Skip to content

return TxReverted from SubmitTransaction when receipt status is 0#21220

Open
poopoothegorilla wants to merge 2 commits intodevelopfrom
fix/PLEX-2535
Open

return TxReverted from SubmitTransaction when receipt status is 0#21220
poopoothegorilla wants to merge 2 commits intodevelopfrom
fix/PLEX-2535

Conversation

@poopoothegorilla
Copy link
Contributor

EVMService.SubmitTransaction always returned TxSuccess after fetching the transaction receipt, without checking receipt.GetStatus(). When a transaction reverts on-chain (status 0), this caused chain capability DON nodes to return inconsistent results, preventing OCR consensus and producing quorum timeouts.
Check the receipt status after fetching it and return TxReverted when status is 0. Update NewChainReceipt test helper to mock GetStatus() and add a test case verifying reverted receipts produce TxReverted.
Fixes PLEX-2535 https://smartcontract-it.atlassian.net/browse/PLEX-2535

@github-actions
Copy link
Contributor

👋 poopoothegorilla, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@trunk-io
Copy link

trunk-io bot commented Feb 18, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
Test_CRE_V2_EVM_WriteReport_Failing_On_Receiver The test 'Test_CRE_V2_EVM_WriteReport_Failing_On_Receiver' failed during execution. Logs ↗︎
Test_CRE_V2_EVM_WriteReport_Failing_On_Receiver/[v2]_EVM.WriteReport_-_failing_on_receiver_fails_with_tx_status_set_to_revert_o... The test failed during an EVM write regression due to a failure in the receiver contract, likely caused by a revert or transaction error. Logs ↗︎

View Full Report ↗︎Docs

@cl-sonarqube-production
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments