You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On v2.x.x (with Cosmos sdk <= 0.42.9) no events were emitted for failed transactions at txs_results in block_results.
For example, B50BDC617EBA33412B92AA11B58EE54EE055A8A3666846D735A9381813B06535 in block 3,526,796:
Since v3.x.x (with Cosmos sdk >= 0.43.0) events are emitted even for failed transactions (including balance tracking events).
For example, 4B0DD315C33C45571F730B506891A514D78BD23BF71A54DDCE202107DF769E90 in block 4,142,573:
But there are still failed transactions for which no events are emitted.
For example, D75ADA55BF9BBFFE17BCEBA34CB69E659DE2B5DC9F7EA1E85634F424F1756199 in block 4,423,509:
Cosmos SDK does not generate any events when transaction fails in one of the auth middlewares (for example, signature verification, nonce matching, etc.). If you want more details on this, you can create an issue with Cosmos SDK.
On v2.x.x (with Cosmos sdk <= 0.42.9) no events were emitted for failed transactions at
txs_results
inblock_results
.For example,
B50BDC617EBA33412B92AA11B58EE54EE055A8A3666846D735A9381813B06535
in block3,526,796
:Since v3.x.x (with Cosmos sdk >= 0.43.0) events are emitted even for failed transactions (including balance tracking events).
For example,
4B0DD315C33C45571F730B506891A514D78BD23BF71A54DDCE202107DF769E90
in block4,142,573
:But there are still failed transactions for which no events are emitted.
For example,
D75ADA55BF9BBFFE17BCEBA34CB69E659DE2B5DC9F7EA1E85634F424F1756199
in block4,423,509
:All failed transactions due to
account sequence mismatch
do not have events.Related to: (x/bank) #8656 balance and supply are now correctly tracked via
coin_spent
,coin_received
,coinbase
andburn
events.The text was updated successfully, but these errors were encountered: