Defining hardware requirements for Ethereum entities is important because it parametrizes what we mean by decentralization, enables informed decision making about protocol upgrades and allows for meaningful benchmark comparisons.
We have been gathering feedback on the current
Kev
312 posts
Applied Research. Ethereum.
prev: Aztec. Creator/Lead of the Noir programming language
Joined May 2023
- Replying to @mteamisloadingI think there is a stronger argument here: Existing home stakers that use mev-boost will still be able to run ethereum validators since most of the work is done by the relayer/sophisticated block builder. They fall under the "attesters" row in the EIP. With an increase in
- Replying to @_weidaiTo clarify, Noir doesn’t compile down to plonkish or r1cs. It compiles to an intermediate representation(IR) that aims to be more high level than what you would get from r1cs/plonkish — the idea being that a proving system will take this IR and convert it to whichever np
- Replying to @nico_mnbl and @savio_souI don't think theres a direct equivalent in terms of R1CS or turbo/ultraplonk rows. To elaborate, when Noir was being made, the design decision was made to not compile down to R1CS/plonk csat directly due to it not being clear that these were the best representations for
- Replying to @pumatheumaI think unless sp{n} imposes zero to no “vm overhead” then the endgame will be a mixture of both zkVMs and circuit compilers; where circuit compilers refers to taking a function written in some high level language and compiling it to a circuit. The reason being that some use
- Replying to @OisinKyneOne thing, the document does not include bandwidth because it’s been very controversial. There’s a second document for that that hasn’t passed the sniff test so far. The issue with bandwidth is that many folks cannot pay for better bandwidth in some areas and you may need more
- Replying to @mteamisloadingTo make the question harder :) if I had to choose three over the next 4-6 months, I would say: - PeerDAS - History Expiry - Latency reduction of EL validity proofs PeerDAS - so that rollups can scale. I think knowing what the maximum number we could scale to is important for
- Replying to @5dayoldburrito and @lightclientsYou can think of EOF as “evm improvements”. I think the majority from both sides would probably agree that: - if we were to start from scratch, we would have something that looks more like EOF - if there was a way to implement EOF like changes and it would magically apply to
- Replying to @drjasper_eth and @malik672_Agree that a raspberry pi 5 for validators is too low, though I think they are okay for full nodes because full nodes have ~12 seconds to download and verify the block. There is a tradeoff between strength of hardware and the amount of download bandwidth needed here, so it might
- Replying to @terencechainI think there is also the added dimension that EIP-1 may not play well with EIP-3, but EIP-2 does. Also the consideration as to whether it makes sense to do EIP-1 and then EIP-2, or should we go straight to EIP-2 with respects to urgency and enshrined protocol complexity (since
- Replying to @tyneslol and @m_ratsimI didn't hear much pushback on the following suggestion in the call: "Given we have inclusion lists. We recommend 25 Mbps download and upload, if you are using MeV-boost. If you want to build blocks locally then we recommend 50 Mbps download and upload" @potuz_eth had valid
- Replying to @mteamisloadingWhy? Just shipping a product does not make it valuable and just because a product has received funding in the past, does not justify future/perpetual funding. If the foundation found no value in this product, but a large proportion of the community did, and it was not possible

