opentron
opentron copied to clipboard
TODO: follow 4.2.0 upgrade
- TIP 250: merkle tree root of transaction result
- This might be a dangerous decision. since there're only 2 fields in transaction result are used.
- Vote for tron power upgrade?
By reading https://github.com/tronprotocol/tips/blob/master/tip-250.md, it seems currently the Tron protocol lacks tampering protection in the block finalization. How would using only 2 fields of the transaction result represent a risk?
The only 2 fields are ret and contract_ret. They and are checked by block's merkle_tree_root, (hash against all txns in the block).
There once was an account_state_root field in Block, which is abandoned.
See-also: https://github.com/tronprotocol/java-tron/pull/3753