ePBS has an EIP number! from now on I'll be referring to EIP-7732. Here is a short thread of some things that this EIP brings to Ethereum. The PR to make it to draft is here

@arixoneth I'm not making any deep nor smart claim. Just pointing that the technology to actually stake native BTC (not wrapped) and in a trustless manner exists and while this may not be an Ethereum killer, it's something that shouldn't be minimized

@IAmNickDodson

@donnoh_eth @DistributedMarz @tyneslol Exactly, this is the key point. The one difference in based preconfs vs centralized sequencer preconfs is that the sequencer can guarantee same ordering regardless of what happens in the parent chain. On based preconfs this is not the case unless you centralize it as well.

@4rgon4ut_ This is not the case, the AI can read and listen to other languages flawlessly, this is an UX issue, not an infra one

@MicahZoltu No they simply need to determine the language of a message before choosing the voice

@MicahZoltu No that's not the case the words are not mispronounced are just simply read in a different language and when it does detect from the start it pronounces well

@MicahZoltu This is cloud, and there's no translation involved at all. Just that listening to a language as someone would read it thinking it's a different one is impossible

@MicahZoltu No, I mean it pronounces Spanish as a gringo who's never ever tried. And if you dictate in Spanish (while set as English) it still tries to guess what you tried to say in English

@2ngg_aprl @fede_intern You get the same sequencer as blast with a centralized preconf gateway. All based rollups even in design still are not based sequencers, they are based batch posters, the sequencer is centralized. Moreover, the L1 sequencer is also centralized. Once FOCIL is in place, well

@fede_intern Liveness is vaporware until someone gives me a design without a centralized preconfer. Interop doesn't really have a fundamental difference than a shared sequencer.

@fede_intern Don't get me wrong I'm an L1 core dev and maxi. I believe if we had designed L2s from the start as L1 coprocessors we would be better off. Based rollups are closer to that design. But I agree with the calls that this seems to be the only fundamental benefit

@gakonst @Data_Always Precisely, I'm not sure where @Data_Always is going with this but it's not clear what a solution is. You can insert more inertia into the pricing mechanism and that leads to worse gas price auctions on spikes. Rollups can't delay batch posting much, there's solid research on this

@donnoh_eth @DennisonBertram @l2beat I had not, this is much better indeed

@donnoh_eth @DennisonBertram @l2beat That's fine, still should be a different list of "not rollups". It could even be opinionated, the stages classification already is and it's somewhat gameable. But we'd all agree that Arbitrum and Blast on the same list is a bit of a stretch

@Rjected I had C++ specifically in mind, but yeah, the "new" libraries like ranges and concepts are particularly tough to read as a reference.