Description:
While working with Vert, I encountered two unresolved questions regarding EOS transaction handling:
-
Transaction Query API Gap
Currently, I cannot find exposed methods in the Vert SDK to:
• Retrieve transaction details by ID (e.g., getTransactionById)
• Access blockchain transaction history via blockchain structure (e.g., blockchain.transactions)
This makes it impossible to programmatically verify transaction finality or inspect post-execution states.
-
Cross-Action Revert Behavior
From EOS documentation, when a primary action triggers on_notify actions as separate transactions, I want to confirm:
• If an on_notify action reverts, does it cascade to revert the primary action?
• How to trace transaction dependency chains in Vert (e.g., parent-child TX relationships)?
Description:
While working with Vert, I encountered two unresolved questions regarding EOS transaction handling:
Transaction Query API Gap
Currently, I cannot find exposed methods in the Vert SDK to:
• Retrieve transaction details by ID (e.g.,
getTransactionById)• Access blockchain transaction history via
blockchainstructure (e.g.,blockchain.transactions)This makes it impossible to programmatically verify transaction finality or inspect post-execution states.
Cross-Action Revert Behavior
From EOS documentation, when a primary action triggers
on_notifyactions as separate transactions, I want to confirm:• If an
on_notifyaction reverts, does it cascade to revert the primary action?• How to trace transaction dependency chains in Vert (e.g., parent-child TX relationships)?