You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current way a Transaction object is constructed, the new getFeeForMessage RPC call has confused some devs because it isn't obvious how to get the message from a constructed Transaction.
Proposed Solution
Add getEstimatedFee(connection: Connection) function on Transaction object that returns the fees from getFeeForMessage
Add Transaction constructor that takes in Message and Signatures[] like the rust implementation
Add methods to build Message like you would a transaction, using addSIgnature and addInstruction to match the Rust implemtnation more.
Steps 2 and 3 are to help make it easier to understand what goes into building a transaction in web3.js, and step 1 is to make it simpler to get estimated fees for transactions.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any activity in past 7 days after it was closed. Please open a new issue for related bugs.
Problem
With the current way a
Transaction
object is constructed, the newgetFeeForMessage
RPC call has confused some devs because it isn't obvious how to get the message from a constructed Transaction.Proposed Solution
getEstimatedFee(connection: Connection)
function onTransaction
object that returns the fees fromgetFeeForMessage
Transaction
constructor that takes inMessage
andSignatures[]
like the rust implementationMessage
like you would a transaction, usingaddSIgnature
andaddInstruction
to match the Rust implemtnation more.Steps 2 and 3 are to help make it easier to understand what goes into building a transaction in web3.js, and step 1 is to make it simpler to get estimated fees for transactions.
The text was updated successfully, but these errors were encountered: