Description
In genlayer_py/types/transactions.py:437, the _from_v06 class method hardcodes tx_execution_result=0 instead of reading it from the transaction data.
Impact
- Any code using
from_transaction_data() will always show NOT_VOTED as execution result on Bradbury and Asimov testnets.
- Users cannot distinguish between successful and failed contract executions via this field.
- While
get_transaction() overrides this via getTransactionAllData, the from_transaction_data() path remains broken.
Suggested Fix
Map tx_execution_result from the appropriate field in the decoded tuple. For V06, tx_data[9] is txExecutionHash and may contain the execution result.
Notes
tx_execution_result maps to: 0 = NOT_VOTED, 1 = SUCCESS, 2 = FAILURE- Affects all users of Bradbury/Asimov testnets using
from_transaction_data()
Description
In
genlayer_py/types/transactions.py:437, the_from_v06class method hardcodestx_execution_result=0instead of reading it from the transaction data.Impact
from_transaction_data()will always showNOT_VOTEDas execution result on Bradbury and Asimov testnets.get_transaction()overrides this viagetTransactionAllData, thefrom_transaction_data()path remains broken.Suggested Fix
Map
tx_execution_resultfrom the appropriate field in the decoded tuple. For V06,tx_data[9]istxExecutionHashand may contain the execution result.Notes
tx_execution_resultmaps to:0 = NOT_VOTED,1 = SUCCESS,2 = FAILUREfrom_transaction_data()