-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Enhance cleos get transaction_id
for exploded data
#6830
Comments
Due to some problems, (guessing that a single nodeos pushed too many transactions) caused the transaction push to return timeout, but in fact the transaction has been pushed successfully. The solution I think of temporarily is that I hope to calculate the ID of the transaction in advance before the transaction is submitted, so that when the transaction is repeated, it is first determined whether the transaction ID already exists. After searching, I found that 'cleos get transaction_id ' (#6830) seems to be the function I want, but testing different data, always returning the same id. I use the method problem? Or is this feature not used like this?
1e24d670f7c504c63184cc4be449f19685a2215f95d03aba7d61f4aac3c77eb8.zip |
The
The problem is your json includes more than a transaction object. Only give it the transaction object. See attached files.
|
I am bothering again, I want to use java to calculate the offline transaction id, but the actual calculation is inconsistent with the return of the chain, can you help me see it? |
You might find this helpful: https://github.com/EOSIO/eosio-java |
actions.hex_data
asactions.data
ifactions.hex_data
provided. That only works, of course, ifhex_data
is available. Ifhex_data
is not available then the abi of the action would need to be retrieve or provided.The text was updated successfully, but these errors were encountered: