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
Document which types of Transaction Operations the Chainweb Rosetta implementation returns, as well as the scenario that trigger these different types.
The Rosetta organization documents the endpoint expectations, but there are still some open-ended aspects that are implementation specific.
The text was updated successfully, but these errors were encountered:
Blocks are made of Transactions and Transactions are made of "Operations".
Each block has 1 Transaction with an Operation labeled CoinbaseReward.
Let's say that this block then has 2 other block transactions: Tx A (a transfer) and Tx B (just a + 1 1 tx).
Then Tx A will have the following operations:
FundTx Operation (this is when we charge the gas payer all of the gas they allocated)
TransferOrCreateAcct Operation that takes the amount from the sender account
TransferOrCreateAcct Operation that deposits the amount to the receiver account
GasPayment to the Miner for the gas amount that the transaction consumed.
Gas Payment to the Gas Payer refunding any unused gas amount. If there's no amount to refund, then this extra operation might not be there, but I'm not sure.
NOTE: gas payment to miner + refund to gas payer = total amount of gas allocated in the FundTx Operation
Tx B will have the same types of Operations as Tx A but without the TransferOrCreateAcct since no KDA was moved around by users.
Document which types of Transaction Operations the Chainweb Rosetta implementation returns, as well as the scenario that trigger these different types.
The Rosetta organization documents the endpoint expectations, but there are still some open-ended aspects that are implementation specific.
The text was updated successfully, but these errors were encountered: