From 4616729f9501e0f7bc2b0ff58f69af969b16d32b Mon Sep 17 00:00:00 2001 From: monty-sei Date: Wed, 12 Aug 2026 14:23:15 +1000 Subject: [PATCH] docs: restore effectiveGasPrice example consistency MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The receipt example reported "effectiveGasPrice": "0x77359400" (2 gwei) while the transaction example in the same flow caps maxFeePerGas at "0x1234" (4,660 wei) — so the receipt showed 429,000x its own fee cap, contradicting min(baseFee + maxPriorityFeePerGas, maxFeePerGas), the formula documented in evm/evm-parity/gas-and-fees.mdx. Caught by the AI reviewer on #59 and merged before that review was addressed. My error: I classified the change as cosmetic, which it is in isolation and is not in context. Reverted rather than corrected. Making the example realistic means restating all three fee values coherently across two separate JSON blocks, which is editorial work unrelated to v6.6.0 and should not ride along in a release catch-up. --- evm/transactions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/evm/transactions.mdx b/evm/transactions.mdx index d9eacbe..6b9861b 100644 --- a/evm/transactions.mdx +++ b/evm/transactions.mdx @@ -258,7 +258,7 @@ EVM transactions in Sei follow the Ethereum transaction format with standard pro "logs": [], "status": "0x1", "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", - "effectiveGasPrice": "0x77359400", + "effectiveGasPrice": "0x1234", "type": "0x2" } }