evm: write status=0 receipt for state-transition errors (CON-256)

[wen-coding]

Both V2 (x/evm/keeper/msg_server.go) and Giga (app/app.go executeEVMTxWithGigaExecutor) had an err != nil branch — for state-transition errors that aren't VM errors — that logged the failure and returned without writing a receipt. The receipt store stays empty for that tx hash, so eth_getTransactionByHash and eth_getTransactionReceipt return null forever for an included tx. Clients that poll for the receipt (e.g. ethers, hardhat-ethers) hang.

This patch writes a status=0 receipt with gasUsed=gasLimit in both branches before returning.

Why this branch existed

Original V2 msg_server (#1083, Oct 2023) treated this branch as defensively unreachable: the antehandler validated everything that could fail before execution (signature, nonce, balance, intrinsic gas), so by the time msg_server ran Execute() could only return VM errors (which WriteReceipt already handles via vmError). Dropping the receipt in this branch was harmless then because nothing reached it.

Pectra/EIP-7623 added a floor-data-gas check inside go-ethereum's Execute(). The Sei antehandler doesn't replicate it (and shouldn't — the chain follows go-ethereum semantics). So a tx with intrinsic ≤ gasLimit < floor now passes the antehandler and fails inside Execute(), surfacing this previously-unreachable branch in normal operation.

The Giga path (#2654, Jan 2026; #2889, Feb 2026) was deliberately ported to match V2's behavior here and inherited the same gap.

Why this surfaced first under Autobahn

Under V2+CometBFT the Cosmos tx indexer records every tx in the block by hash, and evmrpc falls back to it when the EVM receipt store has no entry. eth_getTransactionByHash resolves quickly via the fallback even with no EVM receipt, so the missing-receipt bug stayed latent. Autobahn intentionally has no Cosmos tx indexer (it's a deliberate design choice — Cosmos-specific indexing isn't being pulled forward), so the fallback isn't there. Same bug, different visibility.

The general principle

Beyond the specific EIP-7623 case: any tx included in a block should produce a receipt. Silently dropping receipts for "this shouldn't happen" cases is a fragile contract — the next protocol upgrade or antehandler change can move a check across that boundary and make the case observable. Always producing a receipt (with status=0 + a meaningful vmError) gives clients deterministic feedback and removes a class of "tx vanished" bugs by construction.

Things done

• V2 path (x/evm/keeper/msg_server.go): write receipt in err != nil branch
• Giga path (app/app.go): write receipt in execErr != nil branch, using effectiveGasPrice for EIP-1559 correctness
• Unit test in x/evm/keeper/msg_server_test.go — uses a dynamic-fee tx where tip < cap so the EffectiveGasPrice assertion discriminates between effective price and maxFee
• gofmt -s clean

🤖 Generated with Claude Code

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	May 5, 2026, 1:35 PM

[codecov]

Codecov Report

❌ Patch coverage is 58.82353% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.08%. Comparing base (7004ef1) to head (e038c7a).

Files with missing lines	Patch %	Lines
app/app.go	66.66%	4 Missing and 1 partial ⚠️
x/evm/keeper/msg_server.go	0.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3383   +/-   ##
=======================================
  Coverage   59.08%   59.08%           
=======================================
  Files        2100     2099    -1     
  Lines      173007   172989   -18     
=======================================
- Hits       102218   102209    -9     
+ Misses      61926    61915   -11     
- Partials     8863     8865    +2     

Flag	Coverage Δ
sei-chain-pr	64.09% <58.82%> (?)
sei-db	70.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
x/evm/keeper/msg_server.go	77.77% <0.00%> (-0.65%)	⬇️
app/app.go	70.46% <66.66%> (+0.62%)	⬆️

... and 28 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.