
#EIP4844 (Proto-Danksharding): What impact will it have on the L2s transactions cost? Which L2 will win the fee war? ⚔️💰 🧵⬇️ Let's deep dive into an analysis & projections + TLDR attached 1/16

Co-founder & COO @EnsembleCodes | prev: VC @greenfield_cap

#EIP4844 (Proto-Danksharding): What impact will it have on the L2s transactions cost? Which L2 will win the fee war? ⚔️💰 🧵⬇️ Let's deep dive into an analysis & projections + TLDR attached 1/16

With about 1000 AIagents everybody talks about #ERC8004, #x402 and #AIagents but there's a trust problem nobody's solving. How do you know an agent will do what it claims? 8004 fixes this. It's a registry that makes agents discoverable and trustworthy all on chain. Here's why it matters 🧵⬇️ 1/5

More ressources: - x402 whitepaper: x402.org/x402-whitepaper.pdf - x402scan: x402scan.com/ - 8004scan: 8004scan.io/ 5/5

This unlocks agent marketplaces, reputation systems, and trustless discovery without gatekeepers. It's infrastructure for the agent economy. Built by teams from @Consensys , @Google, @ethereumfndn and @coinbase. Big up to @MarcoMetaMask ,Davide Crapis, Erik Reppel & Jordan Ellis 👏 eips.ethereum.org/EIPS/eip-8… 4/5

Real examples: → Trading agent? Check its reputation score before trusting it with funds → Research agent? Verify its zkML validation proof → Data agent? See all past feedback on-chain Every agent is discoverable, rateable, and verifiable. No gatekeepers needed. 3/5

8004 turns every agent into an NFT with three trust models: → Reputation (on-chain reviews like Uber ratings) → Validation (cryptographic proofs via stake/zkML) → TEE Attestation (hardware-verified execution) You can verify agents before delegating tasks. 2/5

Bibliography: Big up to Erik Reppel, Ronnie Caspers, Kevin Leffew, Danny Organ, Dan Kim, Nemil Dalal, the authors of the x402 whitepaper → x402.org/x402-whitepaper.pdf Other relevant links: - x402.org - x402.org/x402-whitepaper.pdf - coinbase.com/developer-platf… - github.com/coinbase/x402 - x402scan.com/ - a16zcrypto.com/posts/article… 7/7

Why it matters: x402 gives the web a native payment layer, something it’s lacked since day one. It enables a whole new way to monetize: from subscriptions or adds to micropayments <0.01$. It makes value as programmable as information: APIs, models, and apps can charge or pay each other directly. From streaming platforms to data providers, entire business models become autonomous and composable built for both humans and AI agents. It unlocks a $30T market by 2030 based on a16z 2025 report 6/7

What it enables: x402 removes the friction of accounts, API keys, and billing cycles. It lets AI agents and apps pay per use, instantly, and autonomously. 1) A trading bot on Uniswap pays $0.02 for real-time price data from an API. 2) An OpenAI powered agent rents GPU compute from a Base hosted provider by the minute. 3) A reader unlocks a Bloomberg or Substack article for $0.10, no subscriptions, no logins. Simple, direct, and machine native. 5/7

How it works: x402 adds a lightweight layer on top of HTTP. When an API request lacks payment, the server replies with a structured 402 Payment Required: including the cost, asset (like USDC), recipient wallet, and network. The client signs the payment (EIP-712), submits it onchain, and retries the request all in one flow. In practice, it makes paying for an API as seamless as a regular API call. 5/8

Solution: Coinbase’s x402 turns the old “402 Payment Required” code into a real payment protocol. When a server needs payment, it replies with an HTTP 402 containing the price and wallet details. The client (or AI agent) sends a signed USDC payment, retries the request and access is granted instantly. No accounts. No subscriptions. Just pay per use. 4/7

Problem: The internet never had a native way to handle payments. Everything we use today (credit cards, billing systems, subscriptions) was built for humans interactions, not machines. AI agents can browse APIs and data, but for paying: they hit a wall --> forms, accounts, invoices. There simply wasn’t an open, programmable payment layer that machines could use on their own until now. 3/7

HTTP had always a response code for payments long before crypto existed: HTTP 402. It was called "402 - Payment Required", but since the 1990s it was never implemented Now Coinbase just revived it as x402, a standard that turns that code into a payment layer for AI agents and apps. 2/7

Everything you need to know about about "#x402: The Payment Protocol" 🧵 Let's deep dive into a breakdown + TLDR attached 1/7

Always great to be back on @web3globalmedia talks 🫡
#GM - Join us for Wednesday's Web3 Global Talks! 🎙️ Our Guests: @FUSDFinance, @VelarBTC, @totofinance, @TDe_Fi, @hashpack, @SALTLending, @EnsembleCodes, @relend_network, @BitRockChain Set your reminders 👇

I've been meaning to share an important update - I’m joining @ensemblecodes as co-founder. After stepping away from @addressableid , I gave myself one rule: Go where your curiosity takes you. This is where it led 👇