perama.eth (@eth_worm) 's Twitter Profile
perama.eth

@eth_worm

Tinkering

🌱 systems, gadgets, mechanisms, designs, protocols

ID: 1357459599771660288

linkhttp://perama-v.github.io calendar_today04-02-2021 22:44:54

678 Tweet

1,1K Followers

0 Following

perama.eth (@eth_worm) 's Twitter Profile Photo

Ok hear me out A magnet link for all data required to trace all blocks that start with some byte. And a little client that can ingest those and serve debug_traceTransaction Entry point via TrueBlocks, LLC 🌱 to know which 🧲. Post next magnet links in a contract every so often

perama.eth (@eth_worm) 's Twitter Profile Photo

Snack sized archive node recipe 🧑‍🍳 Ingredients - 172KB block body - 2.5MB RequiredBlockState.ssz_snappy 🧑‍🍳 Method 1. Verify state proofs 2. Blend with revm 🧑‍🍳 Serves 270MB trace github.com/perama-v/archo…

perama.eth (@eth_worm) 's Twitter Profile Photo

I dream of a local dapp renaissance, as in Dappnet If reth (Georgios Konstantopoulos) ate the UnchainedIndex (TrueBlocks, LLC 🌱 ), and then spawned 1000 portal nodes (pipermerriam) The progeny could just, you know, show you what Ethereum is doing in a sane way github.com/perama-v/eth_g…

perama.eth (@eth_worm) 's Twitter Profile Photo

Soothing matrix rain for live (androolloyd.hl) EVM data debug_traceBlockByNumber -> semantic filter -> drip Danno Ferrin not pure bytecode sorry. I offer function selectors and logs as consolation Should work against any execution node github.com/perama-v/archo…

perama.eth (@eth_worm) 's Twitter Profile Photo

debug_traceBlockByNumber can be hundreds of MB. Tens of GB if memory is enabled. Why not trace it yourself? A proposal for a method that returns the state for re-executing a block. eth_getRequiredBlockState github.com/ethereum/execu…

perama.eth (@eth_worm) 's Twitter Profile Photo

FOCILIS - an extension to FOCIL that uses a semaphore-like construction. This allows IL publishers to be truly honest about what they see in the mempool. I think the ZKPs are probably mature enough. What do you think? ethereum-magicians.org/t/eip-7805-com…

perama.eth (@eth_worm) 's Twitter Profile Photo

For native rollups, BLOCKHASH opcode use is not secured by the state root. It is implicit state, which L1 doesn't know One solution is to have an L1 contract with a 256 long ring buffer for each rollup. After EXECUTE returns valid, the L2 blockhash buffer is updated