Milos Stankovic

Welcoming @MorphNetrunner as a speaker at ETHCluj for the second year in a row. Milos is a core protocol developer, working for @ethereumfndn since 2024. He's currently part of the Protocol Prototyping team working on Ethereum's upcoming upgrades. We're excited to hear from him.

Fusaka is live on Ethereum mainnet! - PeerDAS now unlocks 8x data throughput for rollups - UX improvements via the R1 curve & pre-confirmatons - Prep for scaling the L1 with gas limit increase & more Community members will continue to monitor for issues over the next 24 hrs.

@potuz_eth @ben_a_adams @nero_eth @ChodoKamil @jih2nn That's what I think as well x.com/MorphNetrunner…

@ben_a_adams @nero_eth @ChodoKamil @jih2nn @MorphNetrunner Still it's inherently more fragile and unnecessarily more complicated than just let the CL drive this

6-second slots are fully spec’d, prototyped in Geth and Prysm, and ready to ship next year. Easily one of the most impactful upgrades we can deliver in the Heka/Bogotá fork. h/t @jih2nn and @MorphNetrunner for getting a first local devnet running.

@ben_a_adams @potuz_eth @nero_eth @ChodoKamil @jih2nn Now that I think about it, I think it makes more sense for CL to tell EL, like it does with other params

@potuz_eth @nero_eth @ChodoKamil @jih2nn @MorphNetrunner Missing my point, was saying the CL should ask the EL what setting to use Similar to blob params where we need to coordinate the same value in both client types; when should really just be one and the other type should query for it (if needed)

@nero_eth @potuz_eth @ChodoKamil @jih2nn If we add SLOTNUM, EL can figure out seconds per slot, so that wouldn't be an issue. I would still leave voting on the block gas limit (instead of per second), but flag can be set per second

thinking about it more, I'm not so sure anymore. My feeling is we should keep the voting on the block gas limit instead of gas limit per second. Even if we abstract the per seconds part away (multiplying by seconds in the slot), it's not super clean. Also, the EL doesn't need to know the seconds per slot.

@benjaminion_xyz @Teku_Consensys The complicated part is not 6s on its own. It's transition from 12s to 6s (while preserving all other properties), upgrading all tooling to support the transition, and benchmarking

Any client that supports the Gnosis chain (@Teku_Consensys was among the first) has supported 5s slots for years now. We don't need to make this too complicated.

@potuz_eth @ChodoKamil @nero_eth @jih2nn Are you referring to client flags? Or something that is more part of the protocol?

@ChodoKamil @nero_eth @jih2nn @MorphNetrunner The EIP should (if it doesn't already) include a change to move to target gas per second instead of per block

@gballet @nero_eth @jih2nn It wasn't heavily tested/benchmarked. And definitely not with BALs as current prototype is based on Fusaka. But as @nero_eth said, block size should half so I also don't see big risk coming from BAL

@nero_eth @jih2nn @MorphNetrunner Was it tested with BALs on a heavy load network/ shadow fork? Seems to me the two things are contradictory, as you increase the amount of data that needs to be transferred, and reduce the time to do so.

@CPerezz19 @ben_a_adams @nero_eth @jih2nn I agree with you, but only partially. Going to 6 sec is not going to unlock any new use cases. But it's significantly going to improve existing ones! Faster inclusion significantly improves capital efficiency. And faster finality impacts everything.

@ben_a_adams @nero_eth @jih2nn @MorphNetrunner This is why we scaled to 100M gas. To support mass L2 exits and massive tokenizations as is a core use case. Not to have L1 at 1TGas/s with 500ns slot times. Again, happy to be convinced otherwise!

Something is coming. Saturday 5:00pm. Music Stage.

Check out our new team page at: prototyping.ethereum.foundation And follow to stay in sync with progess: - @CarlBeek - @JochemBrouwer96 - @BharathVedarth1 - @MorphNetrunner - @raxhvl - @jih2nn

Signing @winprivacy Oath

1/ Protocol Guild’s new brand, logo, and website are live! Our mission remains the same: To secure Ethereum’s future by funding core developers. We will safely scale Ethereum to be long-term infrastructure for the world.

@web3privacy #memathon

Applications for the sixth cohort of the Ethereum Protocol Fellowship are open. If you are an experienced software engineer curious about Ethereum core development, this is for you.

One educational meme: ethereum-magicians.org/t/a-maximally-… @web3privacy #memathon

3rd entry @web3privacy #memathon

I’ve been organizing @ethereum hackathons for 3 years. I was able to do that largely due to being an @EF_ESP grantee for Ecosystem Support. Last year I caught myself wishing I could clone myself to help more events, - because unless you’re a serial organizer like me, you might be missing tools and the network to put together a great event. 🕯️thus I’m launching @hacker_archives - uniting kits, hacker projects, and different initiatives like Safe Events to serve hackers, organizers and sponsors alike. It is a work in progress but DM to contribute or support us❣️ You can find the wireframe of the website below - before you say it - I am aware of the glaring spelling errors and I just want to let you know that I made this at 4am in canva.

Day2 @web3privacy #memathon

@web3privacy #memathon