In order to get the module ID of a module-executed transaction, it is necessary to query using the transaction hash. However, the Gateway did not support this and the Transaction Service was therefore being used directly. We have since implemented a transaction_hash query on the module-transactions endpoint of the Gateway to support this.
Fetching of the module ID from the Transaction Service should now be ported to the Gateway. The ID can be retrieved from the txId.
What is the feature about
In order to get the module ID of a module-executed transaction, it is necessary to query using the transaction hash. However, the Gateway did not support this and the Transaction Service was therefore being used directly. We have since implemented a
transaction_hash
query on themodule-transactions
endpoint of the Gateway to support this.Fetching of the module ID from the Transaction Service should now be ported to the Gateway. The ID can be retrieved from the
txId
.Note: we will eventually return the module ID in the response meaning that it need not be destructure from the
txId
.The list of requirements
txId
(The SDK will need first be updated for type safety)