# Dencun Devnet Issue Tracker ## devnet-7 Spec: https://notes.ethereum.org/@parithosh/devnet-7-specs #### Proposal tracker: | EL | CL | Synced to head? | Attesting? | Proposing? | |--------| -------- | --------------- | ---------- |----------- | |Geth |Lighthouse| ✅ | ✅ | ✅ | | |Teku | ✅ | ✅ | ✅ | | |Nimbus | ✅ | ✅ | ? | | |Lodestar | ✅ | ✅ | ✅ | | |Prysm | ✅ | ✅ | ✅ | |Nethermind |Lighthouse| ✅ | ✅ | ✅ | | |Teku | ✅ | ✅ | ✅ | | |Nimbus | ✅ | ✅ | ? | | |Lodestar | ✅ | ✅ | ✅ | | |Prysm | ✅ | ? | ? | |Besu |Lighthouse| ✅ | ✅ | ✅ | | |Teku | ✅ | ✅ | ✅ | | |Nimbus | ? | ? | ? | | |Lodestar | ✅ | ✅ | ✅ | | |Prysm | ? | ? | ? | |Erigon |Lighthouse| ❌ | ❌ | ❌ | | |Teku | ❌ | ❌ | ❌ | | |Nimbus | ❌ | ❌ | ❌ | | |Lodestar | ❌ | ❌ | ❌ | | |Prysm | ❌ | ❌ | ❌ | |EthJS |Lighthouse| ✅ | ✅ | ✅ | | |Teku | ✅ | ✅ | ✅ | | |Nimbus | ? | ? | ? | | |Lodestar | ✅ | ✅ | ✅ | | |Prysm | ? | ? | ? | #### Issues: - Geth was requesting transactions without a limit, Nethermind provided said transactions as requested and geth subsequently failed at a downstream validation step with `err="message too long`, nethermind announced the wrong sizes for transactions, fixed - Geth announced the wrong sizes for transactions, fixed - Geth transaction RLP was broken, fixed - **UNANSWERED**: We're seeing the following message on 2 nimbus nodes and no other nodes, doesn't seem to be CL related though: nimbus-geth: ``` DEBUG[07-03|09:49:24.586] Message handling failed in `eth` id=0d9de040a6560389 conn=dyndial err="invalid message: message msg #10 (787397 bytes): invalid message: (code a) (size 787397) rlp: expected input string or byte for *uint256.Int, decoding into (eth.PooledTransactionsPacket66).PooledTransactionsPacket[0](types.Transaction)(types.BlobTx).ChainID" ``` - Latest geth. This was due to un-patched geth nodes out in the wild network: ``` invalid message: (code a) (size 131356) rlp: expected input string or byte for *big.Int, decoding into (eth.PooledTransactionsPacket66).PooledTransactionsPacket[0](types.LegacyTx).GasPrice ``` - Deposit processing issue on teku-geth. This was due to improper forkID being used. - Besu p2p blob propagation issue: ``` java.lang.IllegalArgumentException: Value -1 cannot be represented as an unsigned int (it is negative or too big) ``` - Besu proposal issue: ``` 2023-07-11 14:17:12.065+00:00 | vert.x-worker-thread-0 | WARN | AbstractEngineNewPayload | Invalid new payload: number: 78166, hash: 0x200bbf7cd706bb14447d5a91ad67f8cb4eef61293328085a62567f258a0300f6, parentHash: 0xbacd6a1076dffbe712cf2b2f3cafa426d2c441cfe32ad3fe0c0ab1f2edf7b37e, latestValidHash: null, status: INVALID, validationError: Versioned hashes from blob transactions do not match expected values ``` - Privatekey was reused for blobs and transactions. In geth if a blob exists in the mempool, then a tx may not enter the mempool from the same sender account. Confirming if nethermind has the same behaviour.