arixon.eth (@arixoneth) 's Twitter Profile
arixon.eth

@arixoneth

researcher // based rollup maxi // intern @taikoxyz

ID: 1364317541989036032

calendar_today23-02-2021 20:53:52

6,6K Tweet

4,4K Followers

474 Following

arixon.eth (@arixoneth) 's Twitter Profile Photo

being the only rollup with decentralized sequencing it makes sense to also have a strong security council we’ll be introducing a 6/8 council made up of external parties alongside the launch of our DAO proud to have so many teams helping us decentralize and push ethereum forward

arixon.eth (@arixoneth) 's Twitter Profile Photo

people still underappreciate the L1s role in the rollup centric roadmap it won’t just be for settlement/DA but also a global sequencing layer and liquidity hub for L2s on that point: gwyneth won’t have a canonical bridge, assets will live on the L1 and be accessed atomically

arixon.eth (@arixoneth) 's Twitter Profile Photo

seeing a lot of posts saying “L2s are the reason for ETH’s underperformance” while there’s some truth to that, it’s way more nuanced than just L2 = bad the real issue was moving away from the L1 as a shared state machine and spinning up a bunch of general purpose L2 walled

arixon.eth (@arixoneth) 's Twitter Profile Photo

i kinda agree with justin but the way he said it was off imo we all know not everything can or should live on the L1, that’s just not realistic but the L1 absolutely needs to support mid/high value financial activity with max security and decentralization shoving regular users

arixon.eth (@arixoneth) 's Twitter Profile Photo

zora didn’t launch trading on their own chain because it doesn’t have enough users or capital you need a lot of willing buyers ready to ape new coins and that’s missing on zora so users would need to bridge which adds a lot of friction this is why i don’t think appchains make

arixon.eth (@arixoneth) 's Twitter Profile Photo

funny seeing people compare preconfs from a single server to chains with consensus just reaffirms my take that normies don’t care if confirmation comes before or after consensus they just want good UX this is why i say focus on good preconf infra not just shorter blocktimes

arixon.eth (@arixoneth) 's Twitter Profile Photo

excited to see the first "neutral" stage 2 rollup live on testnet - trustless multiprover - no instant upgrade multisig - gigagas throughput - uses L1 sequencing all built on the taiko based rollup stack

arixon.eth (@arixoneth) 's Twitter Profile Photo

fairly common misconception about based rollups, let's clear it up early on, the idea was that L1 validators (delegating to builders in practice) would decide ordering and capture the execution income from based rollups this was brought up as an argument against based

arixon.eth (@arixoneth) 's Twitter Profile Photo

love seeing the recent push for L1 scaling might even say it’s not ambitious enough here’s how EIP-9689 roughly translates to TPS scaling over the next few years based on average L1 tx gas usage

love seeing the recent push for L1 scaling

might even say it’s not ambitious enough

here’s how EIP-9689 roughly translates to TPS scaling over the next few years based on average L1 tx gas usage
arixon.eth (@arixoneth) 's Twitter Profile Photo

we now have two neutral rollups in development, surge & R1 both contribute to the burn and are sequenced by the L1 thanks to the taiko based stack expecting more projects to join the based movement as UX and cost improve with preconfs

arixon.eth (@arixoneth) 's Twitter Profile Photo

as much as i love R1 & surge i gotta agree with alex on this one there’s a reason most big L2s today aren’t stage 2 yet, and it’s not because they don’t want to be (it actually makes for great marketing) the real issue is the code just isn’t battle tested enough to safely

arixon.eth (@arixoneth) 's Twitter Profile Photo

looks like beaverbuild is retiring their centralized builder to focus on buildernet good to see the MEV supply chain healing

arixon.eth (@arixoneth) 's Twitter Profile Photo

probably the biggest taiko upgrade yet - preconfs + batching for whitelisted providers (permissionless soon) - forced inclusion - multiproving w/ multiple clients via SGX & ZK - solver support for bridging tl;dr big UX, security and efficiency boost

arixon.eth (@arixoneth) 's Twitter Profile Photo

imo a very underappreciated part of pectra is the increased maxEB for validators not only is it great for UX but it lets large players consolidate validators which drastically reduces network overhead that in turn allows for more execution and blob scaling

arixon.eth (@arixoneth) 's Twitter Profile Photo

will do the same for my boxes tonight pectra generally reduces networking overhead and storage load blob count is already increased, it’s time to scale execution too