Redistribution commit/reveal fall back to a 500,000 gas floor that no longer fits under Glamsterdam (EIP-8038)
I maintainer di solito rispondono entro 2 giorni
@sbackend123 ci sta già lavorando.
Dal 8/10/2026.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 85/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- go
- Ambito
- blockchain
Direzione di ricerca
Inizia da pkg/storageincentives/redistribution/redistribution.go alle righe 114, 137 e 160, dove MinEstimatedGasLimit è impostato su 500,000. Controlla anche pkg/transaction/transaction.go, dove prepareTransaction usa questo limite minimo. Aumenta il limite per Commit e Reveal ad almeno 1,000,000 per coprire i costi di gas di Glamsterdam, quindi esegui i test per verificare.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Context
Bee master at ba1238d913d75d5a1709e990d712e90087130115 (code reviewed, not run as a node). Network: Sepolia testnet, where Glamsterdam has been active since 2026-10-06 13:53:36 UTC. Measured from recorded Sepolia transactions and a public Sepolia RPC (geth). Related: #5650 (chequebook deployment, same gas repricing, different code path).
Swarm mainnet runs on Gnosis Chain, not Ethereum mainnet. So mainnet impact depends on Gnosis Chain adopting EIP-8037/8038; until then this affects testnet nodes only.
Summary
pkg/storageincentives/redistribution/redistribution.go sets MinEstimatedGasLimit: 500_000 for Claim (line 114), Commit (line 137) and Reveal (line 160). In pkg/transaction/transaction.go, prepareTransaction uses that value as the fallback when eth_estimateGas fails, and as the floor when the estimate plus 33% is lower. Before Glamsterdam the costliest reveal used 260,121 gas, so the floor always covered it. Under Glamsterdam the same calls can need about 740,000 (reveal) and 525,000 (commit), so a node that ends up on the 500,000 floor runs out of gas.
Expected behavior
Commit and reveal transactions get a gas limit that covers the call at execution.
Actual behavior
On the Sepolia Redistribution contract 0x5b718e36f5ce2f2f7e25a397040436ce6af3e89e, some nodes send commit and reveal at exactly 500,000 and run out of gas, while the same calls from other nodes succeed with higher estimated limits:
| call | before the fork (~72 h) | after the fork (~30 h) |
|---|---|---|
reveal at 500,000 |
949 sent, 7 failed, max gas used 260,121 | 74 sent, 38 failed |
reveal, estimated limits (~985,000) |
succeed, using 733,814 to 738,786 | |
commit at 500,000 |
958 sent, 1 failed, max gas used 231,884 | 68 sent, 35 failed |
commit, estimated limits (~684,000) |
succeed, using 509,183 to 523,461 |
Example: reveal 0x26294e6d7a7afe4088b37cb774198b81300b9ae883f46375b9a481d589170b6e (block 11864703) used all 500,000 and failed out of gas. eth_estimateGas for the same call at the parent block returns 243,665; plus 33% that is below 500,000, so the node used the floor. At execution the call took the more expensive path.
Why the call got more expensive: the costliest pre-fork reveal (0x072c5d03d68ef5ca8a01cdb8ba2af73011301f69b8e329e3ae0b3a9ce9c6ff8e, 260,121 gas) makes 57 SSTOREs, all to existing slots. EIP-8038 raises an existing-slot update from 2,900 to 10,100 gas (5,000 to 12,100 cold), about 7,100 more per write.
Steps to reproduce
- On a Sepolia node,
debug_traceTransaction 0x26294e6d7a7afe4088b37cb774198b81300b9ae883f46375b9a481d589170b6e '{"tracer":"callTracer"}': the top call to the Redistribution contract ends inout of gasat 500,000. eth_estimateGaswith the samefrom,toand input at block 11864702: 243,665.- Compare with any successful post-fork reveal from a node that sent a higher estimated limit (gas used 733,814 to 738,786).
debug_traceTransaction 0x072c5d03d68ef5ca8a01cdb8ba2af73011301f69b8e329e3ae0b3a9ce9c6ff8ewith the default struct logger plusprestateTracer: 57 SSTOREs, none to a new slot.
Possible solution
Raise MinEstimatedGasLimit for Commit and Reveal to at least 1,000,000, above the observed 738,786, or make it configurable. The 33% buffer on successful estimates can stay; the floor is what fails when the estimate comes back from a cheaper path or fails.
Claim uses the same floor, but I did not measure it here. #5473 notes a claim costs roughly 1.5 times a commit or reveal, so its floor should come from a measurement under Glamsterdam rather than this number.
Related: open PR #5473 lowers MinEstimatedGasLimit from 500,000 to 250,000. Under Glamsterdam that floor would cover even fewer commits and reveals (reveal needs about 740,000, commit about 525,000), so the two changes should be considered together.
AI Disclosure
- This issue contains suggestions and text generated by an LLM.
- I have reviewed the AI generated content thoroughly.
- I possess the technical expertise to responsibly review the AI generated content mentioned in this issue.
- Lingua principale
- Go
- Stelle
- 1.5k
- Fork
- 390
- Merge medio
- 4g 15h
- PR unite (30g)
- 21
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ethersphere/bee
-
Chequebook deployment uses a fixed 175,000 gas limit; it needs about 630,000 under Glamsterdam (live on Sepolia since 2026-10-06)Forse già presa @sbackend123 l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
ethersphere/bee#5650 · 1 assegnatario ·
I maintainer di solito rispondono entro 2 giorni
-
seen
Difficoltà 4/5 3-5 giorni Idoneità per principianti 40/100
ethersphere/bee#5648 ·
I maintainer di solito rispondono entro 2 giorni
-
pusher: chunksWorker deadlocks on a deferred chunk that fails IdentityAddress (send on nil op.Err), halting all push-syncForse già presa @sbackend123 l’ha presa 3 giorni fa. Apertaseen
Difficoltà 3/5 1-2 giorni Idoneità per principianti 75/100
ethersphere/bee#5641 · 1 assegnatario ·
I maintainer di solito rispondono entro 2 giorni
-
GET /bzz/<ref>/ can 404 off-node, and the 404 is indistinguishable from a missing index documentApertaseen
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
ethersphere/bee#5625 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
GET /chunks returns 500 "read chunk failed" where /bytes and /feeds return 404Forse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Apertaaccepted seen
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
ethersphere/bee#5624 ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di ethersphere/bee
Issue simili
-
Discriminator mapping keys are listed in a random orderForse già presa @reuvenharrison l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Idle compaction monitors LIST the replica every tick when the newest destination file spans more than one TXIDForse già presa @pishuv l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
benbjohnson/litestream#1563 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
agent-research agent-review-finding chore
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
jordansmall/spindrift#4922 ·
I maintainer di solito rispondono entro 1 giorno
-
gcsartifact: deleting a missing version returns an errorForse già presa @ktsoator l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni