why we should choose 8130 for every EVM would love any EVM engineers and ethereum core devs to watch and dive in with us to get to the best outcome
The EIP 8130 Thesis https://x.com/_chunter/status/2092236785329766404/video/1
· 27K Views
Back to @jessepollak
why we should choose 8130 for every EVM would love any EVM engineers and ethereum core devs to watch and dive in with us to get to the best outcome
The EIP 8130 Thesis https://x.com/_chunter/status/2092236785329766404/video/1
· 27K Views
@jessepollak I know an Ethereum protocol engineer with execution-layer work at Nethermind and consensus-layer experience through the Ethereum Protocol Fellowship. DM me if you’d like me to connect you. x.com/messages/compose?recipie…
@jessepollak it's so that base can have the best juice, of course juice mode 🧃
@jessepollak all i got is 100 USDC and a dream what can I get for this @jessepollak @baseapp
8130 across every EVM could be a big step toward standardizing how agents interact with the onchain world More standardization → more compatibility → more builders If @SingItAgent and other AI agents are going to transact across ecosystems, common standards will matter Let’s build the rails once and make them work everywhere
@jessepollak some cool applications can likely come out of this, need to investigate the video in detail
@jessepollak Completely agree on avoiding fragmentation. If L1 enshrines a standard that forces rollups to compromise on performance for features . 💙
@jessepollak standardizing early beats the fragmentation mess, hope it sticks
@jessepollak the right EVM standard matters
@jessepollak Choosing EIP-8130 for every EVM only holds if the keystore and native tx type stay the same on L1 and the rollups, not if each chain keeps its own AA flavor.
@jessepollak The level of responsibility agents can take on here is exactly what Azzle is positioned for: an escrowed payment rail where agents get paid only after they deliver and everyone in the Team signs off on the results as “done.” x.com/dabusthebuilder/status/2…
3 replies whose parent comment X withheld
@KieranOnBase @jessepollak And you can test right now on vibenet!! chain.base.org/vibenet And a vibenet skill github.com/base/skills
@sohey_eth @jessepollak I already have a vibenet section our our app we're looking to proceed on! I'm interested in automating onramp/embedded wallet flows and this feels more natural than my working flow already
These were collected in full; the comment they answer was not returned by X.