# Proto-Danksharding (EIP-4844) Devnet v3 User Guide [toc] ## Getting Devnet-3 ETH You can request devnet ETH from the deployed Multifaucet: https://eip4844-faucet.vercel.app/ ## Uploading Blobs Blobs can be uploaded by sending blob transactions to geth. [blob-utils](https://github.com/Inphi/blob-utils) is a handy script that makes it easy to send blob transactions: ``` blob-utils tx\ -rpc-url <your_geth_rpc_url>\ -blob-file <blob_file>\ -to <to_address>\ -value <value>\ -chain-id 1331\ -private-key <account_private_key> ``` ## Downloading Blobs Blobs can be retrieved from the beacon chain network. [blob-utils](https://github.com/Inphi/blob-utils) lets you do this easily: ``` blob-utils download\ --beacon-p2p-addr <beacon_node_p2p_address>\ --slot <beacon block slot> ``` ## Public Endpoints Here are a couple endpoints you may use to interact with the devnet. Execution RPC: https://eip-4844-alpha.optimism.io Beacon nodes: - `/ip4/34.121.33.53/tcp/13000/p2p/16Uiu2HAkwy4MJBLsCvmuPwrfVX9GqNiGeppshnsbn2BgKskCtRDE` - `/ip4/34.122.190.151/tcp/13000/p2p/16Uiu2HAmHd6WSHUEB7SrxdDR8dPVLTJqkzgPGbriej15udyQZugY` - `/ip4/34.123.117.254/tcp/13000/p2p/16Uiu2HAmSLVoxaR1ztHqBjezWFSvFa3HeTWPZNswfS4aMWob59L6` ## Configuration If you're client dev, you'll need the following configs to peer with the devnet. - Geth genesis configuration: https://github.com/Inphi/eip4844-testnet/blob/devnet-3/genesis.json - Beacon State Genesis: https://github.com/Inphi/eip4844-testnet/blob/devnet-3/genesis.ssz - Beacon chain configuration: https://github.com/Inphi/eip4844-testnet/blob/devnet-3/config.yml There isn't a bootnode for the devnet. But you can peer directly with the following nodes to join the network: #### Execution bootstrap nodes ``` enode://fdefa8b36717bd246ce338e952a3b949e608158d06c74c8b9e207439f70bfc63da27b7a4c4161a14722f7d4a256fda9c93a6dd5c26624b6a523dca2cd852ad97@34.121.33.53:30303?discport=0 ``` Network ID is 1331. #### Beacon boostrap nodes ``` enr:-MK4QNbUbou2Vr7FsG_Mm9luJuY-6L8nT6-Zl8tSBpmAEtVEBKGZxlazo-xGsmUCppD8X1JRoPekMP3Ysr39H54_iN6GAYU61xS5h2F0dG5ldHOIAAAAAAAAAACEZXRoMpA3FbaXIAAAk_gmlkgnY0gmlwhCJ5ITWJc2VjcDI1NmsxoQIlwaxycUgJ_Ht4lYdDlInbIuRxu0HcHcFbu0D7As2SLYhzeW5jbmV0cwCDdGNwgjLIg3VkcIIu4A enr:-MK4QBqN5McD5YYgfEnfQjWUvrSaCITjBvQevlP5q0nCVbKuZRoa2XvGWOBwTDQyLNYiqgeettVwXs0PrSc1rOY2rjKGAYU2M7A8h2F0dG5ldHOIAAAAAAAAAgCEZXRoMpA3FbaXIAAAk_gmlkgnY0gmlwhCJ6vpeJc2VjcDI1NmsxoQNJzjxNKr7-a-iEDs0KvaL_vo1UH91kefEiWzgAdwSntYhzeW5jbmV0cw-DdGNwgjLIg3VkcIIu4A enr:-MK4QEzb6r0hpSyiko9u-mbEX1TzdTD9RcSiU4jhey5jJbTAHLdXNFR32CfjingVa6QMyCPtZRUfzSGbJ0ur3-Pdxe-GAYU2OwM5h2F0dG5ldHOIAAAAAAAAAACEZXRoMpA3FbaXIAAAk_gmlkgnY0gmlwhCPi7faJc2VjcDI1NmsxoQIKBTGU_riCSYrscdRCLuocbNzhF9RTNItPfD4_PmYngIhzeW5jbmV0cwCDdGNwgjLIg3VkcIIu4A ``` Try not to get your node banned :pray: ## Troubleshooting/assistance If you have issues running the devnet, please reach out in the `#4844-testing` channel of the [Eth R&D discord](https://discord.gg/wNT8ghMbkw).**
Last changed by  
 
inphi
881

Read more

Prysm x Geth EIP4844 Interop (h/t @terencechain)

Prysm setup Clone the eip4844 branch in the Prysm repo and build the binaries $ git clone https://github.com/prysmaticlabs/prysm.git $ cd prysm $ git checkout eip4844 $ bazel build //cmd/prysmctl $ bazel build //cmd/beacon-chain $ bazel build //cmd/validator $ cd ../

12/19/2022
Proto-Danksharding (EIP-4844) Devnet **v2** User Guide

[toc] What's Changed? Please read through this document carefully as there have been some changes since the first Devnet. Here's a summary: The geth and beacon clients have been updated New geth and beacon genesis Some beacon chain and execution networking parameters have changed New geth/prysm bootstrap node addresses Blob-utils has been updated to support Devnet v2

10/12/2022
Optimistic Syncing for EIP-4844

We need to tweak the way optimistic sync works. Right now, a VALID block means all of its ancestors will also become VALID blocks. This breaks with EIP-4844 when blob sidecars are introduced as an optimistcally imported block lacking its sidecar will be incorrectly promoted to VALID. This makes It then becomes easy for an attacker to trick peers into treating actual invalid blocks with missing data as valid. To fix this all we have to do is change the block used as a basis for the block status transition. When a block transitions from NOT_VALIDATED to VALID, identify the latest ancestor whereby all of its own ancestors satisfy data availability: (using the same type definitions in the optimistic sync spec) def latest_valid_candidate_block(opt_store: OptimisticStore, block: BeaconBlock) -> BeaconBlock: # Assuming the input `block` is VALID chain = [] while True:

6/30/2022
Read more from inphi
Published on HackMD