Skip to main content

157 posts tagged with "Web3"

Decentralized web technologies and applications

View all tags

Bonk.fun Domain Hijack: Front-End Attacks Are Crypto's Fastest-Growing Threat Vector

· 9 min read
Dora Noda
Software Engineer

On March 12, 2026, a community-driven Solana launchpad processing hundreds of thousands of dollars in daily fees briefly turned into a wallet-draining trap — and the smart contracts powering it were never touched. Bonk.fun, the letsBONK-branded meme coin platform backed by Raydium and the BONK DAO, had its domain hijacked, a fake "Terms of Service" signature prompt injected into its front-end, and roughly 35 wallets emptied before the team flagged the compromise. The attackers didn't need a zero-day. They needed a hostname.

That single hour of chaos captures what security teams across DeFi have been whispering since 2023 and shouting since the $1.4 billion Bybit heist: the Solidity code is no longer the soft target. The front-end is. And the industry's collective blind spot is costing users more than any smart contract exploit in history.

Intent-Based Wallets: The Endgame of Account Abstraction

· 12 min read
Dora Noda
Software Engineer

For fifteen years, using crypto has meant one deeply strange ritual: opening a wallet, scrutinizing a hex-encoded transaction, manually funding an account with the right gas token, and signing with a key you are personally responsible for never losing. By 2026, that ritual is on the way out — and the wallets leading the charge are not asking users to sign transactions at all. They are asking users what outcome they want.

That shift, from transaction-based wallets to intent-based wallets, is the long-promised endgame of account abstraction. It is being assembled right now out of three apparently unrelated pieces: ERC-4337 smart accounts, EIP-7702 EOA programmability, and a $10B+ wallet-as-a-service market in which Coinbase, Privy (now part of Stripe), Dynamic (acquired by Fireblocks), Safe, and Biconomy are racing to build the default consumer surface for Web3. Put them together and you get a wallet that finally behaves like Apple Pay: you express a desire, someone else figures out the plumbing, and the blockchain disappears.

The Final Form: Users Specify Outcomes, Not Transactions

The mental model for a 2020-era crypto wallet was a transaction factory. You selected a chain, chose a gas token, set slippage, reviewed calldata, and signed. Every UX paper cut — wrong network, insufficient ETH for gas, a signature for an approval plus a second signature for the swap — came from the fact that the user was the one operating the low-level machine.

Intent-based architectures invert that model. As Anoma's research on intent-centric topologies frames it, an intent is a partial state change expressing a preference, signed by the user, that a solver network competes to fulfill. CoW Protocol has run this playbook for years as a batch-auction DEX where users sign "sell X for at least Y" and solvers do the routing. Flashbots' SUAVE takes the same idea down into block building. Cross-chain intent protocols are actively replacing bridges, turning "bridge from Arbitrum to Base" into "have these tokens on Base in under a minute."

The critical point for wallets is this: once an account is programmable enough to accept conditional, multi-step instructions and hand them off to a solver, the UI no longer has to look like Etherscan. It can look like a chat box, a Shopify checkout, or a one-tap "Buy PENGU" button inside a consumer app. The wallet becomes the place where intents get authenticated; something else does the executing.

ERC-4337 Built the Execution Pipes

The first enabling piece is ERC-4337, which went live on Ethereum mainnet on March 1, 2023, and quietly became the execution substrate for most of today's smart wallets. Instead of sending a transaction from an externally owned account, a user signs a UserOperation — a richer object that specifies validation rules, an optional paymaster, and the calls to execute. Bundlers package these into real transactions and send them to a canonical EntryPoint contract. Alchemy's overview of account abstraction walks through this pipeline in detail.

Three capabilities fall out of this design, and together they make intent-based UX actually shippable:

  • Gas abstraction via paymasters. A paymaster contract can agree to pay gas on the user's behalf, sponsored by the application or swapped from any ERC-20 the user holds. The experience is a user with zero ETH transacting immediately after account creation — the pattern that Nadcab's 2026 gas abstraction guide projects will become an invisible default by 2027.
  • Session keys. Rather than reauthorizing every action, a user can grant a scoped, time-limited key — "this dApp may spend up to 100 USDC on trades on Base for the next hour." This is the primitive that makes on-chain games, AI agents, and high-frequency DeFi usable without a signature popup every 30 seconds.
  • Modular validation. Because validation is expressed in contract code, not hard-coded by the protocol, wallets can swap in passkeys, multisig logic, social recovery, or fraud checks without changing the underlying account.

ERC-4337 by itself, however, had a structural problem: smart accounts are separate contracts from the ordinary EOAs most users already had. Migrating 200M+ existing addresses into brand-new accounts was never going to happen cleanly. That is the gap EIP-7702 closed.

EIP-7702 Upgraded Everyone's Wallet Overnight

Ethereum's Pectra upgrade launched on May 7, 2025, and introduced EIP-7702 — a deceptively simple change that lets an ordinary EOA temporarily delegate its code to a smart contract. The private key still controls the account, but while the delegation is active, the EOA behaves like a smart wallet: it can batch calls, use paymasters, whitelist session keys, and plug into ERC-4337 infrastructure. Turnkey's deep dive on the 4337-to-7702 journey captures the key insight: the two standards are complementary, not competing.

The effect on adoption is dramatic. MetaMask, Ledger, Ambire, and Trust Wallet have shipped EIP-7702 support, and Ledger has rolled it out across Flex, Stax, Nano Gen5, Nano X, and Nano S Plus hardware. BuildBear's ERC-4337 vs EIP-7702 comparison notes that most major wallet providers are expected to follow through 2025 and into 2026, which is exactly what the on-chain data is now showing.

In practical terms, 7702 means users do not have to know they are getting a smart wallet. Their existing address keeps working; it just starts doing more. That is the quiet precondition for a mass-market intent-based UX: you cannot ask hundreds of millions of users to migrate, so you upgrade the account they already have.

The $10B+ Wallet-as-a-Service Battle

If ERC-4337 and EIP-7702 are the protocol layer, the battle for the product layer is being fought in wallet-as-a-service. This is where consumer-grade onboarding, passkeys, embedded UIs, and intent routing get packaged into an SDK that any app can drop in.

The leaders each come from a different angle:

  • Coinbase Smart Wallet is the reference consumer implementation. Coinbase's announcement and Base's rollout plan describe a wallet with passkey-based authentication, gasless transactions by default, and cross-chain deployment — 8 networks at launch and the same contract address across 248 chains via the Safe Singleton Factory. It is effectively trying to become the "Sign in with Apple" of Web3.
  • Privy, acquired by Stripe in June 2025, is now fused with Bridge to unify crypto and fiat payments, pushing embedded wallets deep into mainstream fintech flows. Openfort's Privy alternatives guide tracks how this acquisition reshaped the consumer-crypto landscape.
  • Dynamic, acquired by Fireblocks, is focusing on developer experience and multi-chain adapters, positioning embedded wallets as an enterprise building block.
  • Safe and Biconomy are competing on the modular-account side, particularly around ERC-7579 — a minimal standard for modular smart accounts co-developed by Rhinestone, Biconomy, ZeroDev, and OKX that lets validators, executors, hooks, and fallback handlers plug into any compliant account.
  • Aggregators such as WAGMI, Web3Modal, RainbowKit, and Reown have already integrated smart wallets at the connector layer, meaning most new dApps are intent-capable by default.

The strategic prize is the identity and intent layer for Web3. Whoever owns the wallet owns the funnel for every transaction, payment, and agent action a user initiates. Openfort's top 10 embedded wallets report and the wave of Stripe/Fireblocks M&A make it clear that incumbents now treat this as strategically important — and finite.

The Four Primitives That Make the Intent Wallet Real

Strip away the marketing and there are four concrete primitives behind "wallets that hide the blockchain."

  1. Native passkeys (EIP-7212). A precompile for secp256r1 signature verification lets wallets authenticate with the same WebAuthn passkeys iPhones, Android devices, and YubiKeys already use. That removes seed phrases as the default recovery model and replaces them with device-secure, phishing-resistant credentials users already trust.
  2. Session keys (commonly structured as ERC-7579 validator modules). Scoped, revocable permissions underwrite one-tap gameplay, recurring payments, and agent autonomy without turning the signature popup into spam.
  3. Gas abstraction (ERC-4337 paymasters). Apps sponsor gas, users pay fees in the stablecoin they already hold, and "I need to buy ETH first" stops being a gating step.
  4. Batched execution (ERC-7821). A single user action can contain an approve + swap + bridge + stake sequence that either all happens or none of it does, eliminating the half-completed multi-step disasters that define crypto UX today.

Combine these four with a solver network and you have the ingredients for an actual intent-based wallet: the user says "swap $500 of USDC for ETH on whatever chain is cheapest," and the wallet handles bridging, gas, approval, and execution under one authorization.

Why This Is Also a Security Story

Intent architectures are not just a UX upgrade. They are also a security pattern, which matters more than usual given the $25M Resolv hack reporting from March 2026 that put intent-layer safety on investors' radar.

Two shifts stand out. First, because intents are expressive declarations of desired end states, wallets and solvers can simulate and reason about them before execution — rejecting anything whose outcome would violate a policy, rather than relying on users to spot malicious calldata. Second, smart accounts let wallets layer defense-in-depth: spending limits, address allow-lists, transfer delays on large outflows, and automatic pauses on anomalous activity can all be modules on the account itself, not optional settings buried in a UI.

The flip side is new risk surface. Solver networks can collude, paymasters can front-run, and a mis-scoped session key can drain an account silently. Intent wallets do not eliminate risk; they move it from "did the user read the calldata?" to "did the wallet's modules and solvers behave correctly?" That is a far better question to be auditing in 2026.

What Builders Should Watch in the Next 12 Months

Three inflection points are worth tracking:

  • EIP-7702 saturation. As more wallets turn on delegation and more dApps start assuming smart-wallet capabilities, the design space for EOA-only UX collapses. Apps that still require users to manually fund gas, approve separately, and sign bridges will feel obsolete.
  • ERC-7579 module ecosystems. Expect a real marketplace of audited validators, session-key modules, recovery policies, and compliance hooks that wallets can compose the way mobile apps compose SDKs. Thirdweb, OpenZeppelin, and Rhinestone are already building toward this.
  • Intent settlement standards. Cross-chain intents are the next battleground, and whoever standardizes settlement (ERC-7683 and its successors) will influence how liquidity and MEV get captured across L2s.

The underlying infrastructure — low-latency RPCs, bundlers, paymasters, indexers — has to keep pace. Every intent that a wallet accepts becomes several chain operations behind the scenes, which means the providers that serve these wallets see traffic scale non-linearly with user counts.

BlockEden.xyz operates high-availability RPC and indexing infrastructure across Ethereum, Base, Arbitrum, Sui, Aptos, and other networks that intent-based wallets settle on. If you are building a smart-wallet SDK, paymaster, solver, or embedded-wallet experience, explore our API marketplace to run on infrastructure designed for the multi-chain, intent-driven future.

Sources

Pi Network's 18M KYC Army: How the Sleeper Identity Layer Just Redefined Web3's Most Important Metric

· 14 min read
Dora Noda
Software Engineer

The crypto industry has spent a decade celebrating wallet counts as if they were users. In April 2026, a network most serious analysts wrote off three years ago quietly rewrote the scoreboard: Pi Network confirmed 18 million KYC-verified human beings and 526 million peer validation tasks completed — numbers that, depending on how you squint, either expose Web3's biggest measurement lie or describe the most undervalued identity layer on the planet. The same week, a single clustered group of 5,800 wallets farmed roughly 80% of an airdrop on BNB Chain. The juxtaposition was not a coincidence.

Sybil-resistance, long treated as a niche concern of airdrop farmers and DAO governance nerds, has suddenly become the single most consequential design problem in crypto. The cause is simple: autonomous AI agents can now open wallets, pass behavioral heuristics, and transact on-chain at machine speed. Against that attacker, "one wallet one vote" is worse than useless — it is an engraved invitation. And the networks that can prove their users are actual humans, at scale, with emerging-market coverage, are about to matter a lot more than the networks that can prove their users have a MetaMask extension.

The Numbers That Reframe the Debate

Pi Network's April 2026 milestone announcement reads like a boring operations update until you line it up against the rest of the industry:

  • 18 million KYC-verified Pioneers. Each application passes roughly 30 distinct checks, combining AI pre-screening with human review from a pool of more than 1 million trained validators.
  • 526 million peer validation tasks completed across the platform, with each identity split into small sub-tasks (liveness video, document check, photo match, name verification) and requiring at least two independent validators to agree before approval.
  • 100 million-plus app downloads, outpacing Coinbase and OKX on global install counts, and roughly 60 million active monthly miners.
  • First validator rewards distribution on April 3, 2026, paying out at 22x the current base mining rate — instantly making KYC validation the most lucrative activity on the network.
  • 16.57 million Pioneers already migrated to mainnet at the March 5, 2026 snapshot, topped up by a 10 million Pi foundation contribution to the first-round rewards pool.

Now compare to the other identity layers the industry usually treats as serious:

  • World (formerly Worldcoin) reports around 26 million signed-up users with roughly 12.5 million full Orb iris-scan verifications. Orb Mini deployment is the lever the team is pulling to push past 100 million — a target, not a number on the books.
  • Human Passport (formerly Gitcoin Passport) crosses 2 million verified users across its credential stack. Strong in grant-funding circles, tiny next to the mobile audience Pi has accumulated.
  • Civic Pass and BrightID continue to serve specific protocol use cases well but have never been designed to scale to the hundreds of millions.

The honest way to read these numbers is that Pi has quietly built the largest KYC-verified human network in Web3 — and it did so in exactly the markets (South and Southeast Asia, Africa, Latin America) that every other proof-of-personhood project either can't reach or explicitly refuses to scan with an Orb.

Why "Verified Humans" Is Suddenly Load-Bearing

For most of crypto's history, the industry's North Star metric was wallet count. More addresses meant more users, which meant more adoption, which meant number go up. The metric worked, if imperfectly, as long as creating a fresh wallet still imposed meaningful friction — downloading an extension, learning about seed phrases, funding for gas.

Three 2026 developments broke that assumption completely.

AI agents now open wallets by themselves. BNB Chain's active AI agent count exploded from roughly 337 at the start of January 2026 to more than 123,000 by mid-March, a 36,000% increase in under three months. Each of those agents has at least one wallet. Many have several. None of them are human. The wallet-count metric did not just get diluted — it stopped measuring the thing it used to measure.

Airdrop Sybil attacks went industrial. In Apriori's token launch on BNB Chain, a single clustered group of 5,800 wallets captured approximately 80% of the supply. Trusta Labs' open-source Sybil-detection framework, OKX's dedicated airdrop protection tooling, and the growing common wisdom that airdrops should be tied to deposits or volume rather than activity signal the same conclusion: activity-based rewards are broken when attackers can spin up 10,000 perfectly-behaved AI agents with unique transaction patterns.

Governance quorum assumptions started to crumble. A DAO vote that passes 70-30 against an "incumbent" position looks legitimate only if the wallets voting represent distinct humans. When a well-resourced attacker can credibly field 50,000 autonomous agents that each cast individually-rational-looking votes, the one-wallet-one-vote model is not secure — it is cosplay as security.

Every one of these failure modes shares a root cause. The industry has been using a cheap, non-unique identifier (the wallet) to do the job of a hard, unique identifier (the human). As long as the gap between those two things was narrow, the approximation worked. AI agents have now yanked those two signals apart by several orders of magnitude, and there is no way back.

What Pi Actually Built (And Why It Works Differently)

Pi Network's identity system was not designed in response to the 2026 AI-agent crisis — it predates it by years. But the design choices that once looked like "mobile-first crypto for the masses" now look like the most pragmatic answer to proof-of-personhood at scale:

Distributed human validation, not biometrics. Where Worldcoin's pitch is "we will ship a hardware device to every country and scan every iris," Pi's pitch is "we will pay Pioneers to validate each other's documents on their existing smartphones." The first model is beautiful in theory and politically catastrophic in practice — multiple governments have banned or suspended Orb operations. The second is boring, incremental, and has already moved 526 million validation tasks through the system.

Split-task review with redundancy. Each KYC application is decomposed into independent sub-tasks: liveness check, document inspection, photo match, name verification. At least two validators must independently agree before approval. This is simultaneously a Sybil-resistance scheme (no single validator can rubber-stamp fakes at scale) and a quality-control system (errors are statistically squeezed out by agreement thresholds).

AI in the inner loop, humans in the outer loop. Pi's Standard KYC process integrates AI pre-screening to halve the queue of applications awaiting human review. Crucially, the AI filters out the obvious cases and hands the ambiguous ones to human validators — inverting the typical Web3 approach of "deploy AI and pray." The humans are the final authority; the AI is a throughput accelerator.

Palm-print biometrics as an optional second layer. Pi is beta-testing palm-print authentication as an additional anti-Sybil layer. Unlike iris scanning, palm prints can be captured by consumer smartphones without dedicated hardware, which matters enormously for the network's emerging-market footprint.

The trade-off most Western commentators miss is that Pi's system is slow by design. A Pioneer might wait weeks or months between starting KYC and full mainnet migration. For a developer who wants to ship an NFT drop next Tuesday, that is infuriating. For a protocol that wants to know whether its 18 million users are 18 million distinct humans and not 200,000 humans running 90 agent-wallets each, it is exactly the right cadence.

The Emerging-Markets Moat Nobody Priced In

Here is the data point that matters most and gets discussed least: Pi Network's user base is concentrated in precisely the regions that the rest of the proof-of-personhood stack cannot reach.

Pi has tens of millions of users across Vietnam, Indonesia, the Philippines, Nigeria, and Latin America — populations that often have limited access to traditional banking, passport documents accepted by Western KYC vendors, or hardware that can run browser-extension wallets smoothly. These same users typically cannot get to an Orb (which requires physical travel to a Worldcoin kiosk) and do not have the crypto literacy to wrangle Gitcoin Passport's stamp ecosystem.

What Pi has done, effectively, is build a KYC network where the onboarding unit of cost is a $50 smartphone and a willingness to spend a few minutes a day opening the app — not a passport, not a $1,200 iPhone, not a visit to a specialized biometric device. For the next billion crypto users, that is the only onboarding model that will actually work at scale.

This matters strategically for any protocol trying to design a genuinely global airdrop, governance vote, or retroactive funding round. A Sybil-resistance layer that accidentally excludes half the world's population is not really Sybil-resistant — it is Western-user-resistant, which is a very different property. Pi's geographic distribution is an asset that competitors will not easily replicate, because the investment required is less technical than operational: years of community building, translated documentation, local validator training, and payment rails that work in countries with 30% mobile-money penetration.

What This Means for Protocol Builders in 2026

If you are a protocol team that plans to run an airdrop, a governance vote, a grant round, or a DeFi access layer in the next 18 months, the Pi milestone has three immediate implications.

Treat proof-of-personhood as a stack, not a vendor choice. No single PoP system covers every use case well. Worldcoin offers strong biometric uniqueness in regions where it operates. Human Passport covers the Western grant-funding circuit with strong integrations. BrightID captures crypto-native social graphs. Pi now owns the emerging-markets KYC-verified-human segment. The right architecture for a serious 2026 airdrop is probably to accept proofs from multiple systems and score accordingly, not to bet the entire anti-Sybil strategy on one source of truth.

Design for "verified human" as a first-class primitive. ERC-8004 on Ethereum mainnet, which went live January 29, 2026, provides an on-chain registry for agent identities with cryptographic attestations. Companion standards for human identity are lagging — not because the demand is missing, but because the politics of a global human-identity registry are complicated. In the meantime, the practical path is to accept portable proofs (Pi, Worldcoin, Human Passport, BrightID) and make "human-only" gating a configurable policy for any access-controlled surface.

Stop treating wallet count as a serious metric. If a protocol reports 500,000 wallets and a competitor reports 50,000 verified humans, the competitor is probably the more valuable network — and certainly the more defensible one against Sybil attacks, governance capture, and regulatory pressure. Investors, founders, and analysts should start explicitly tracking verified-human counts as a parallel KPI to wallet count in every diligence deck.

The Open Questions Pi Still Has to Answer

None of this is a coronation. Pi Network still faces three sharp questions that will determine whether the 18 million KYC number translates into actual infrastructure value.

Can the KYC process scale another 10x? Adding 180 million verified humans requires either an enormous expansion of the validator pool or aggressive AI substitution for human review. Each choice carries risk: more validators dilutes per-validator rewards and invites quality degradation, while more AI review undermines the whole "distributed human verification" pitch. Pi's answer so far — AI in the inner loop, humans in the outer loop — is clever, but it has not been tested at 10x the current throughput.

Does the PI token accrue the value of the identity layer? Most of Pi's cultural mindshare still treats it as a speculative token play. For the identity thesis to matter economically, PI needs to become the unit of payment for identity-gated services: airdrop allocations priced in PI, governance votes collateralized in PI, access to human-only DeFi pools metered in PI. The mainnet infrastructure to do this exists. The protocol partnerships to make it happen have barely started.

Will mainstream Web3 protocols actually integrate? Pi's emerging-market userbase is its greatest asset, but it also makes Pi foreign to most Ethereum-centric builders. The network that integrates Pi-verified-human proofs for airdrops or governance first will get a defensible distribution advantage in exactly the regions where user acquisition costs are lowest. Nobody has taken that shot yet at scale. The team that does is going to look very clever in 18 months.

The New Shape of Web3 Identity

The broader pattern here is that Web3's identity layer is stratifying — not into a single winner but into a portfolio of primitives, each optimized for a different segment. World owns the Western hardware-biometric market. Human Passport owns credentialed grant-funding identity. Civic serves enterprise on-ramps. BrightID serves crypto-native community governance. Pi owns KYC-verified humans in emerging markets at a scale nobody else comes close to.

The protocols that treat identity as a stack, not a switch, are going to build the most resilient systems. The ones that try to standardize on a single vendor are going to discover in 2027 that their "global" airdrop somehow excluded half the world's humans, or that their "Sybil-resistant" governance was, in fact, dominated by a few well-resourced AI agent farms that happened to pass Orb.

The 18 million number is not just a milestone for Pi. It is the first honest signal the industry has that proof-of-personhood is not a research problem anymore — it is a shipping-at-scale problem, and the shipped systems have very different shapes than the research papers predicted.

BlockEden.xyz provides production-grade blockchain RPC infrastructure for teams building identity-aware Web3 products across Sui, Aptos, Ethereum, and BSC. As Sybil-resistance becomes a load-bearing primitive for every serious airdrop, governance system, and AI-agent-gated protocol, explore our API marketplace to build on foundations designed for the verified-human era.

Sources

a16z vs. the SEC's Broker Net: The Safe Harbor That Could Decide DeFi's Fate

· 11 min read
Dora Noda
Software Engineer

Every wallet developer, DEX interface builder, and NFT marketplace creator in the United States currently operates under the same legal ambiguity: their non-custodial software might — under a maximalist reading of the Securities Exchange Act of 1934 — make them an unregistered broker-dealer. The penalty for that classification? Criminal liability, civil enforcement, and the effective death of their product.

That is the legal cliff Andreessen Horowitz (a16z) and the DeFi Education Fund (DEF) are trying to rope off. In August 2025, the two organizations filed a joint proposal with the SEC's Crypto Task Force, asking the Commission to formally declare that non-custodial software interfaces are categorically not broker-dealers. The April 2026 publication of a supporting economic analysis by former SEC Chief Economist Craig Lewis has reignited the debate at exactly the moment the SEC is drafting its most comprehensive crypto rulemaking in a generation.

The question is simple and its stakes enormous: should the software you write to let users control their own assets be regulated the same way as the Morgan Stanley broker managing your grandmother's retirement account?

Google's UCP Is Winning the Protocol Wars — And Web3 Just Became Its Secret Weapon

· 8 min read
Dora Noda
Software Engineer

Three months after Google unveiled its Universal Commerce Protocol at NRF 2026, one thing is clear: the race to own AI-native commerce infrastructure has a front-runner — and the winner may be determined not by which Big Tech platform has the most users, but by which one can settle payments the fastest, cheapest, and most trustlessly.

That answer, increasingly, points to blockchain.

Toss's "Money 3.0" Gamble: How South Korea's Largest Fintech Is Betting Blockchain on 30 Million Users

· 9 min read
Dora Noda
Software Engineer

Imagine an app that handles the banking, investments, insurance, and payments of nearly 60% of an entire country's population. Now imagine that app quietly filing 24 trademark applications for a homegrown digital currency — and hiring engineers to build its own blockchain. That is what South Korea's Toss has been doing since mid-2025, and the implications reach far beyond one company's product roadmap.

Toss, operated by Viva Republica, is not a crypto-native startup chasing venture capital on a Web3 pitch. It is South Korea's dominant financial super-app, with 30 million registered users, nearly $1.8 billion in 2025 revenue (up 38% year-over-year), and a planned US IPO targeting a $10 billion-plus valuation. When a company of this scale turns toward blockchain, it signals something different from the speculative launches that characterized the last cycle — and it also invites comparison to a cautionary tale that every Korean fintech executive knows by heart.

Toss Goes Onchain: Why South Korea's $10B Fintech Super-App Is Building Its Own Blockchain

· 8 min read
Dora Noda
Software Engineer

A fintech app that half of South Korea uses every day just filed 24 stablecoin trademarks, started hiring blockchain engineers, and told a packed conference audience that "Money 3.0" runs on smart contracts. Toss is not experimenting with crypto — it is architecting an entirely new financial layer for 24 million users.

DePAI: When Robots Get a Blockchain Wallet and Start Paying Each Other

· 9 min read
Dora Noda
Software Engineer

When a robot dog named Bits identified it was running low on battery, it didn't bark for help or send an alert to a human operator. It located the nearest charging station, walked over, plugged itself in, and paid for the electricity in USDC — all without a single human instruction. This wasn't a science fiction demo. This was OpenMind's live prototype running on the x402 protocol in early 2026.

Welcome to DePAI: Decentralized Physical AI, the convergence that's turning the physical world into an autonomous machine economy.

The Protocol Wars: Google UCP, x402, ERC-8183, and the Fight to Define How AI Agents Pay

· 9 min read
Dora Noda
Software Engineer

Every decade or so, a new computing paradigm forces the payments industry to rebuild from scratch. The internet gave us PayPal. The smartphone gave us Stripe. Now AI agents are giving us something far stranger: a world where software autonomously buys and sells goods, services, and compute — at machine speed, at machine scale, without a human authorizing each transaction.

The question that will shape the next decade of commerce is not whether AI agents will transact. They already do. The question is: which protocol will they use?

In the first four months of 2026, four major contenders have emerged — Google's Universal Commerce Protocol (UCP), Coinbase's x402, Ethereum's ERC-8183, and Stripe's Machine Payments Protocol (MPP). Each represents a fundamentally different philosophy about who controls the future of autonomous commerce. Understanding their differences is essential for any developer, investor, or business building in the AI-crypto convergence.

Google UCP: The Commerce Layer

On January 11, 2026, Google announced the Universal Commerce Protocol alongside over 20 global partners including Shopify, Walmart, Target, Mastercard, Visa, and Stripe. The pitch was elegant: eliminate the "N × N integration bottleneck" — the hairball of point-to-point integrations that currently prevents AI shopping agents from working across the open web.

UCP works through a simple discovery mechanism. Merchants publish a /.well-known/ucp JSON manifest that AI agents can dynamically read. The manifest lists available capabilities — checkout, product discovery, order management, loyalty — structured as modular functions that agents can compose. Payment itself is handled separately: UCP supports Google Pay, Shop Pay, and major card networks, with payment processors Adyen, Mastercard, and Stripe plugging into a flexible payment handler layer.

The practical entry point is Google AI Mode in Search and the Gemini app. When you ask Gemini to "order a birthday cake from the nearest bakery," UCP is the plumbing enabling that transaction without you ever visiting a website.

What makes UCP formidable is its distribution, not its technology. Google's AI surfaces reach billions of users. Any retailer who wants to appear in AI-mediated search results has strong incentive to implement UCP. That network effect — buyer agent distribution through Google, merchant adoption through e-commerce fear of being left out — is a structural moat that no startup can easily replicate.

The Web3 concern: UCP routes transactions through Google's identity layer and established payment processors. Stablecoins and on-chain settlement are not part of the initial architecture. For now, UCP is the incumbent rails dressed in agentic clothes.

Coinbase x402: The Open Rail

While Google optimized for consumer-facing retail commerce, Coinbase identified a different problem: API economics don't work when you add agents.

Card networks have a minimum fee floor of roughly $0.30 per transaction. That's fine when a human is buying a $50 product. It's completely unworkable when an AI agent is making thousands of micro-requests to different APIs — fetching a weather data point, running a quick LLM inference, querying a blockchain node — at fractions of a penny each. Traditional payment rails are simply the wrong tool.

Coinbase's answer, formalized in early 2026 with the x402 Foundation alongside Cloudflare, repurposes the long-dormant HTTP 402 "Payment Required" status code. Here's how a transaction works:

  1. An agent sends an HTTP request to a paid resource
  2. The server responds with HTTP 402 — a machine-readable payment demand specifying amount and accepted currency
  3. The agent pays in stablecoins (primarily USDC on Base, Polygon, or Solana)
  4. The agent retries the request; the server grants access

The implementation is just a middleware wrapper — a few lines of code. No account setup. No API keys for the payment itself. Settlement is instant and near-free on L2 networks. USDC accounts for 98.6% of x402 transactions on EVM chains. Coinbase offers 1,000 free transactions per month through its Developer Platform.

x402 is particularly compelling for the developer tool and AI infrastructure market. BlockEden.xyz's blockchain node APIs, for example, represent exactly the kind of pay-per-call services that x402 was designed to unlock — where machine-to-machine API access needs to be both granular and economically viable.

The honest challenge: despite a supporting ecosystem valued at roughly $7 billion, on-chain data as of March 2026 shows only around $28,000 in daily x402 volume. The narrative is years ahead of real usage. The protocol is technically sound; product-market fit remains to be demonstrated at scale.

ERC-8183: Trust Between Agents

Neither UCP nor x402 solves a problem that emerges when agents don't just buy things — they hire each other.

Imagine an orchestration agent that needs to complete a complex research task. It subcontracts to a web-scraping agent, a summarization agent, and a fact-checking agent. Each subcontractor needs to be paid — but how does the orchestrator trust that the work was actually done? How does the subcontractor trust it will be paid? What happens when the work is subjective and the parties disagree?

ERC-8183, announced March 10, 2026 by the Ethereum Foundation's dAI team and Virtuals Protocol, addresses this layer. Ethereum Foundation AI Lead Davide Crapis called it "one of the missing components in the open agent economy."

The standard defines three roles:

  • Client: Posts a task on-chain, deposits funds into escrow
  • Provider: The agent performing the work, submits completion proof
  • Evaluator: The party that judges whether work is complete and triggers settlement

The Evaluator is the core innovation. It's modular: it can be another AI agent, a zero-knowledge verifier smart contract (for deterministic tasks), a multi-sig DAO (for high-value work), or any address that can call complete or reject. The protocol itself is neutral — it just watches for the settlement signal.

Job lifecycle flows through four states: Open → Funded → Submitted → Terminal. A hook system lets developers extend the core lifecycle with custom logic: enforce preconditions, manage complex capital flows, integrate external reputation checks.

ERC-8183 isn't competing with x402 or MPP — it operates at a different layer. The emerging stack looks like this:

LayerProtocolWhat it does
Commerce/DiscoveryGoogle UCPWhat to buy, from whom, under what terms
HTTP Payment Primitivesx402Pay-per-request API access
Settlement/BridgeStripe MPPFiat + crypto settlement
Agent Contract/EscrowERC-8183Agent-to-agent subcontracting and dispute resolution
Identity/ReputationERC-8004Is this agent trustworthy?

Stripe MPP: The Bridge

Stripe's Machine Payments Protocol, launched March 18, 2026 alongside the Tempo blockchain (co-incubated with Paradigm), is the most pragmatic of the four. It's designed to be the fiat-to-crypto bridge that lets agents transact in either currency depending on the merchant's preference.

The flow mirrors familiar patterns: an agent requests a resource, the service responds with a payment request, the agent authorizes payment, the resource is delivered. What's notable is what happens next: MPP transactions appear identically to standard Stripe payments in the merchant dashboard — same tax calculation, same fraud protection, same accounting integrations, same refund flows.

Early use cases capture the range of the opportunity. Browserbase uses MPP so agents can pay per headless browser session. Postalform lets agents pay to print and mail physical letters. One food vendor lets agents order sandwiches in New York City.

Stripe also supports x402 ("Stripe taps Base for AI agent x402 payment protocol"), suggesting the company is deliberately positioning as infrastructure for any agent payment protocol rather than betting exclusively on its own standard. This is a classic platform play: control the settlement layer regardless of which protocol wins at the application layer.

The Stakes: Who Captures $3–5 Trillion?

McKinsey projects AI agents could mediate $3–5 trillion in global commerce by 2030. The protocol wars matter because whoever controls the payment layer controls the economics of that market.

The fundamental divide is between two visions:

The incumbent vision (Google UCP, Stripe MPP, Visa's Trusted Agent Protocol): Agent payments are an extension of existing commerce infrastructure. Merchants adopt new protocols because of distribution advantages and compliance guarantees. Stablecoins might participate at the settlement layer, but identity, fraud protection, and merchant relationships remain with existing players.

The open crypto-native vision (x402, ERC-8183): Agents are a fundamentally new actor class that doesn't fit existing identity and payment assumptions. A software agent has no credit history, no social security number, no billing address. The only sensible identity system is a cryptographic wallet. The only sensible payment rail is one that doesn't require a human account holder. Stablecoins aren't just an alternative payment method — they're the correct primitive.

Mastercard's $1.8 billion acquisition of stablecoin infrastructure firm BVNK — the largest stablecoin infrastructure deal on record — suggests the incumbents understand the threat. They're not ceding the stablecoin layer; they're buying their way into it.

Ant Group's blockchain arm joined the race on April 2, 2026, unveiling Anvita, a platform enabling AI agents to hold assets, trade, and transact with minimal human involvement — bringing Chinese fintech into a race that previously seemed US-dominated.

What This Means for Web3 Builders

The protocol wars are not winner-take-all — at least not at every layer simultaneously. More likely, different protocols will dominate different segments:

  • Consumer retail: Google UCP wins through distribution, at least in the near term
  • API/developer tool payments: x402 wins if adoption reaches critical mass among AI infrastructure providers
  • Agent-to-agent subcontracting: ERC-8183 wins by default — no incumbent has a competing standard for this use case
  • Hybrid merchant payments: Stripe MPP wins among Stripe's existing merchant base

The existential question for crypto-native protocols is whether the $28,000 daily x402 volume grows into something real before incumbents integrate stablecoins into their own standards and remove the differentiation.

For developers building today, the practical answer is: implement x402 for API monetization (the integration cost is low), watch ERC-8183 for agent-to-agent commerce, and accept that Google UCP will dominate consumer retail until proven otherwise.

The race to define how AI agents pay is the most important infrastructure competition in technology right now. The winners won't just process payments — they'll set the terms of the autonomous economy.

BlockEden.xyz provides enterprise-grade blockchain APIs and node infrastructure across 20+ networks, built for the scale that AI agent applications demand. As x402 and agent-native payment protocols mature, our API-first architecture positions developers to monetize and access blockchain data with machine-speed granularity. Explore our API marketplace to build infrastructure designed for the autonomous future.