# Onchain day 6 ## Kurtosis challenge To run Kurtosis, you will need Docker. Check out the installation docs for [Docker](https://docs.docker.com/desktop/). Then see how to install [Kurtosis](https://docs.kurtosis.com/install). This is the configuration we will be using for our private network. It will include 3 nodes. 2 Geth<->Lighthouse pairs and one Geth<->Teku pair. It will additionally run dora the blockchain explorer. Save the following to a file `basic.yaml`. ```yaml= participants: - el_type: geth cl_type: lighthouse count: 2 - el_type: geth cl_type: teku additional_services: - dora ``` Run kurtosis: ```shell= kurtosis run github.com/ethpandaops/ethereum-package --args-file basic.yaml --image-download always ``` It will do a lot of stuff. At tne end you should see an output like this: ``` INFO[2025-02-13T18:40:20+01:00] ===================================================== INFO[2025-02-13T18:40:20+01:00] || Created enclave: lush-estuary || INFO[2025-02-13T18:40:20+01:00] ===================================================== Name: lush-estuary UUID: 786adf9383ea Status: RUNNING Creation Time: Thu, 13 Feb 2025 18:38:48 CET Flags: ========================================= Files Artifacts ========================================= UUID Name 97eecf350d7e 1-lighthouse-geth-0-63 9e0741a9d62a 2-lighthouse-geth-64-127 c0feee76c3e9 3-teku-geth-128-191 e707448e8835 dora-config 1cb0fccb492b el_cl_genesis_data 9c12fc572440 final-genesis-timestamp e1d83c1dd678 genesis-el-cl-env-file ed1affb0fd25 genesis_validators_root c7be02411dff jwt_file 2ff7925931d6 keymanager_file a8f07cea1a5b prysm-password 975b3dc490be validator-ranges ========================================== User Services ========================================== UUID Name Ports Status 7499762c5d14 cl-1-lighthouse-geth http: 4000/tcp -> http://127.0.0.1:64742 RUNNING metrics: 5054/tcp -> http://127.0.0.1:64743 tcp-discovery: 9000/tcp -> 127.0.0.1:64744 udp-discovery: 9000/udp -> 127.0.0.1:61644 5e23e9bb6800 cl-2-lighthouse-geth http: 4000/tcp -> http://127.0.0.1:64919 RUNNING metrics: 5054/tcp -> http://127.0.0.1:64920 tcp-discovery: 9000/tcp -> 127.0.0.1:64921 udp-discovery: 9000/udp -> 127.0.0.1:58432 9bca3e11bb0d cl-3-teku-geth http: 4000/tcp -> http://127.0.0.1:64994 RUNNING metrics: 8008/tcp -> http://127.0.0.1:64995 tcp-discovery: 9000/tcp -> 127.0.0.1:64996 udp-discovery: 9000/udp -> 127.0.0.1:52415 b7285e1df65c dora http: 8080/tcp -> http://127.0.0.1:65256 RUNNING 8808b66683df el-1-geth-lighthouse engine-rpc: 8551/tcp -> 127.0.0.1:64596 RUNNING metrics: 9001/tcp -> http://127.0.0.1:64597 rpc: 8545/tcp -> 127.0.0.1:64594 tcp-discovery: 30303/tcp -> 127.0.0.1:64593 udp-discovery: 30303/udp -> 127.0.0.1:52262 ws: 8546/tcp -> 127.0.0.1:64595 b8ffb8f05d75 el-2-geth-lighthouse engine-rpc: 8551/tcp -> 127.0.0.1:64659 RUNNING metrics: 9001/tcp -> http://127.0.0.1:64660 rpc: 8545/tcp -> 127.0.0.1:64662 tcp-discovery: 30303/tcp -> 127.0.0.1:64661 udp-discovery: 30303/udp -> 127.0.0.1:54969 ws: 8546/tcp -> 127.0.0.1:64658 1da6c1e77a5d el-3-geth-teku engine-rpc: 8551/tcp -> 127.0.0.1:64733 RUNNING metrics: 9001/tcp -> http://127.0.0.1:64734 rpc: 8545/tcp -> 127.0.0.1:64731 tcp-discovery: 30303/tcp -> 127.0.0.1:64730 udp-discovery: 30303/udp -> 127.0.0.1:53625 ws: 8546/tcp -> 127.0.0.1:64732 9bdf01558373 validator-key-generation-cl-validator-keystore <none> RUNNING b87057b39296 vc-1-geth-lighthouse metrics: 8080/tcp -> http://127.0.0.1:65195 RUNNING 5874675f180c vc-2-geth-lighthouse metrics: 8080/tcp -> http://127.0.0.1:65224 RUNNING ``` Now you should be able to open Dora. Notice the line containing Dora: ``` b7285e1df65c dora http: 8080/tcp -> http://127.0.0.1:65256 RUNNING ``` That means I can open `http://127.0.0.1:65256` in the browser. ### Bonus challenge If you'd like to to the bonus challenge we need to send a RPC request to one of the EL nodes's RPC endpoint. Find the port of `el-1-geth-lighthouse`. It has multiple lines. Select the one which reads `rpc: 8545...` ``` 8808b66683df el-1-geth-lighthouse rpc: 8545/tcp -> 127.0.0.1:64594 ``` And then send the request, make sure to put the right port at the end: ``` ❯ curl -X POST -H "Content-Type: application/json" --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' http://127.0.0.1:PORT-GOES-HERE {"jsonrpc":"2.0","id":1,"result":"0x25"} ``` ## Run your own node challenge Download Geth: https://gethstore.blob.core.windows.net/builds/geth-linux-amd64-1.15.1-b027a90a.tar.gz Or if you are on mac: https://gethstore.blob.core.windows.net/builds/geth-darwin-amd64-1.15.1-b027a90a.tar.gz ``` tar xzf geth-linux-amd64-1.15.1-b027a90a.tar.gz // cd into geth cd geth-linux-amd64-1.15.1-b027a90a ./geth --datadir datadir-blsync-test --beacon.api https://www.lightclientdata.org --beacon.checkpoint 0x42f506d895f34e35d034643e3481026c7a8844ab5872f7d1524d479206e0b2ed❯ ./geth --datadir datadir-blsync-test --beacon.api https://www.lightclientdata.org --beacon.checkpoint 0x42f506d895f34e35d034643e3481026c7a8844ab5872f7d1524d479206e0b2ed ``` After a lot of logs you should start to see lines like this: ``` INFO [02-13|18:28:38.434] Syncing beacon headers downloaded=512 left=21,838,531 eta=2h10m22.710s ``` You're syncing! :)
Last changed by  
 
Sina Mahmoodi
49

Read more

7002 withdrawal schedule

Adding a withdrawal requests to the queue costs 74160 gas per call, which means you can add ~480 withdrawals per block. Within two blocks, the fee to add more withdrawals to the queue will take roughly 2.6 million ETH in the next block. The amount of ETH needed to add another withdrawal will go down over the next blocks, but the curve of the increase is extremely steep. You can kinda think of it as if the 12.5% increase per block of 1559 is only applied every 480 blocks. So whenever this increase applied, the fee not only goes up by 12.5% but by (12.5%)^480, thus the fee increases quite suddenly. The fee will slowly go down on every block, but it will take 126 blocks until the fee is below 1 ETH to add a withdrawal to the queue. This means that an attacker can grief staking pools quite easily. NUMBERS

3/4/2025
Writing a testcase for graphql

I'm adding a testcase for EIP-4844 which will be shipped in the Cancun hardfork. The graphql schema will change to include the additional fields in the block and transaction data structures. Refer to https://github.com/ethereum/execution-apis/pull/468 for the schema changes. The graphql simulator https://github.com/ethereum/hive/tree/master/simulators/ethereum/graphql comes with a chain. However this chain does not include 4844 blocks. So we need to update the chain and add new blocks + txes. For that we use https://github.com/s1na/graphqltestgen. graphqltestgen This tool is used to extend an existing chain which at first consisted of only frontier blocks and later extended with post-merge blocks. The benefit here is we can test the response at fork boundaries too. It takes in a genesis configuration assumed to be at ./genesis.json and the RLP-serialized list of blocks at ./chain.rlp. Note: you need to modify the code to implement the kind of block you want to add. The new chain will be written to ./newchain.rlp. Note since the merge forks happen after a given timestamp. Since the new block should be Cancun, the genesis file must be modified with a value for "cancunTime". To calculate the value, we need to know the timestamp of the last block. This is because the chain generator will automatically assign parentBlock + 10 as the timestamp of any new block. So I print the current header with go run main.go head to find out the latest timestamp.

10/3/2023
state

tracer hooks OnBalanceChange(addr common.Address, prev, new *big.Int, reason BalanceChangeReason) OnNonceChange(addr common.Address, prev, new uint64) OnCodeChange(addr common.Address, prevCodeHash common.Hash, prevCode []byte, codeHash common.Hash, code []byte) OnStorageChange(addr common.Address, slot common.Hash, prev, new common.Hash) OnLog(log *types.Log) OnNewAccount(addr common.Address) blockchain

8/8/2023
eth_multicall test suite tutorial

This is a guide on how to write test cases for eth_multicall and execute them. There are several pieces to this puzzle: Tests are implemented in rpctestgen which outputs IO (Json-rpc request response sequence) artefacts. .io files are copied over to Hive simulation rpc-compat Then we can execute the tests against a client using Hive CLI Now let's go over them one by one. Rpctestgen This is a tool written in Go. It creates a chain from code and starts a Geth node with that. The test cases describe the request to be made which is then sent to geth to fill in the response. The test case can do validation of the response and optionally fail to generate the artefact.

6/19/2023
Read more from Sina Mahmoodi
Published on HackMD