fusaka-devnet-2 specs

Changes include:

• Data column sidecars by root
• validator custody (optional)
• distributed blob building
• shifting cell proof computation to transaction sender

Discussion:

• Who is going to work on EELS/EEST for proof computation to tx sender?

EIP List for fusaka-devnet-2

The list below links the specific commit versions of the EIPs included in devnet-2.
Fusaka mega EIP-7607

EIP-7594: PeerDAS - Peer Data Availability Sampling
EIP-7823: Set upper bounds for MODEXP
EIP-7825: Transaction Gas Limit Cap
EIP-7883: ModExp Gas Cost Increase
EIP-7892: Blob Parameter Only Hardforks
EIP-7907: Meter Contract Code Size And Increase Limit
EIP-7917: Deterministic proposer lookahead
EIP-7918: Blob base fee bounded by execution cost
EIP-7934: RLP Execution Block Size Limit
EIP-7939: Count leading zeros (CLZ) opcode
EIP-7951: Precompile for secp256r1 Curve Support

Test Releases

Consensus Specs: Release v1.6.0-alpha.2

Exection Spec Tests: TODO

Spec versions required & Open PRs

Beacon Metrics
PeerDAS metrics: add data column, kzg, custody metrics Open

Beacon API
Add data_column_sidecar event to eventstream API Merged
Add data column sidecars debug endpoint Merged

Builder Specs

Consensus Specs
Modify fork digest to distinguish BPO forks + add entry to ENR Merged
CGC: Update before Fulu Merged
PeerDAS validator custody: Introduce Status RPC lowest_slot Merged

Execution APIs

Execution Spec PRs
Update EIP-7892: harden the spec with p2p details. Merged
Update EIP-7594: Add blob count per tx limit via blobSchedule Merged
Update EIP-7883: Assume minimal base/mod length of 32 Merged

Execution Spec Tests PRs
feat(tests): peerdas tracking issue Open

Validator custody

Kurtosis Interop Conifg (Pre-devnet testing)

todo

Testing:

EIP-7594: PeerDAS - Peer Data Availability Sampling

• Validator custody testing - kurtosis - add validators and verify cgc value changes
  • This can be easy by setting validators to 0x02 credential and make manual deposits
• MEV workflow testing - pending of flashbots/mock builder
• Minimal spec testing
• Minimal spec testing with mev workflow
• Validator custody testing with assertoor. Have a new assertoor test where 0x02 credentials are toped up 32eth at a time and monitoring the node’s cgc value to ensure that its going up as expected.
• Sync testing script found here
• Figure out proper cgc behaviour, do we want the cgc value to change before fulu? Otherwise we might be without supernodes during fork transition. This would really stress the actual fork
• Finalized root bug - what should the genesis root hash be? @potuz @hangleang
• Prysm <> Grandine peering bug
• What steps can we do to have resource optimization? We see significantly more ram usage with fulu active.
• We see very stable 9 blob spamming with pre fulu.
• Once fulu active, with the same constant load, we see significantly less blobs included.
• We might need some assertoor test for checking the content of blob pool and see if a proposer have included all the blobs that is has seen locally. And then we can investigate if there are any client pairs that are struggling with local blob building with peerdas.
• Test blob reconstruction. Have node propose only 50% of the columns, and see if all clients are able to complete reconstruction.

EIP-7825: Transaction gas limit cap

• Spamoor - create a new scenario with aiming to have 30M+ in a single transaction - @pk910
• Assertoor - verify that all ELs reject such tx
• Malicous test - get a node that accepts 30M tx+ and see if we can propagate it in the network.
  Spamoor config:

# wallet settings
seed: gasburnertx-5 # seed for the wallet
refill_amount: 5000000000000000000 # refill 5 ETH when
refill_balance: 1000000000000000000 # balance drops below 1 ETH
refill_interval: 600 # check every 10 minutes

# scenario: gasburnertx
total_count: 0
throughput: 1
max_pending: 2
max_wallets: 40
rebroadcast: 120
base_fee: 20
tip_fee: 2
gas_units_to_burn: 31000000
client_group: ""

Besu

04 Jun 12:06:51 | Rejected invalid block 65 (0xcc465caeaca9e0a764bc1229350a61890ae76668a4ee83b19b3f1a15b6bde261),  ExtraData: Nethermind v1.33.0a, reason: TxGasLimitCapExceeded: Gas limit 32050000 exceeed cap of 30000000.

Nethermind:

EIP-7823, EIP-7883, EIP-7918

• Hive tests

EIP-7892: Blob Parameter Only Hardforks

• Kurtosis tests, going up, down with max blobs
• Figure out final form of BPO format
• Figure out future forks in blob schedule planning
• Figure out if we want hard fork names in the blob schedule fields.
• Test future compatibility, see if we can start with fulu genesis and higher BPO at genesis.
• out of order fork execution issues, glamsterdam becoming active without triggering bpos

EIP-7917: Deterministic proposer lookahead

• Kurtosis local test to determine that interop works among all clients

Client Interop Readiness

Manu’s test scenarios:
https://hackmd.io/@manunalepa/BJzNsCnvyx

Prysm

Scenario	Grandine	Lighthouse	Lodestar	Nimbus	Prysm	Teku
1a
1b
2a
2b
3a
3b
4

Reference spec for previous devnet:

https://notes.ethereum.org/@ethpandaops/fusaka-devnet-0

Open future Questions:

• Alternately, should a pre-determined blob increase schedule triggered by a BPO mechanism (as proposed here) be included in fusaka-devnet-0?