Skip to main content

150 posts tagged with "Web3"

Decentralized web technologies and applications

View all tags

Sentio Hits Kraken as $ST Goes Live: Can a TypeScript-First Indexer Crack The Graph's Data Throne?

· 10 min read
Dora Noda
Software Engineer

On April 15, 2026, Kraken quietly did something more consequential than another mid-cap token listing.

It opened ST/USD and ST/EUR order books at 10:30 AM UTC for Sentio, a self-described "decentralized data and compute network" pitching itself as an AI-powered Bloomberg Terminal for Web3. Binance Alpha and Gate.io followed the same day. In a week where headlines were dominated by quantum-safe Bitcoin, trillion-dollar DeFi lending milestones, and Tempo's Stripe-backed L1 testnet, the $ST listing slipped through as the most technically interesting infrastructure bet of the cycle — because Sentio is not trying to replace a DEX or a stablecoin. It is trying to replace the invisible plumbing that every dApp, analytics dashboard, and AI agent already depends on: the indexer.

The question is whether a TypeScript SDK, a claim of 100x faster indexing, and a fresh compute-credit token can dislodge incumbents that have spent five years embedding themselves into every serious Web3 stack.

The End of the Monolithic AI Agent: Why Coinbase's Agentic Wallet Is Rewriting Web3's Orchestration Stack

· 9 min read
Dora Noda
Software Engineer

For two years, the crypto-AI narrative promised a single godlike agent: one model holding your keys, reading the mempool, executing your strategy, and managing your memory. That agent is already obsolete. In February 2026, Coinbase quietly buried it — and most of the industry has not yet noticed.

When Coinbase launched Agentic Wallets on February 11, 2026, the headlines focused on the obvious: a wallet infrastructure purpose-built for autonomous AI. The deeper signal was architectural. Coinbase did not ship a smarter agent. It shipped a wallet that agents call as an external service — and in doing so, it formalized the shift from monolithic AI to specialist agent networks as Web3's critical infrastructure problem for the next decade.

The Monolithic Agent Was Always a Fantasy

The first wave of crypto agents — Virtuals, ai16z forks, the early Eliza clones — bundled everything inside one runtime. Reasoning, memory, key management, execution, and risk scoring lived in a single process, often a single LLM call. It was a beautiful demo and a terrible production system.

The failures were predictable. A monolithic agent holding keys is a single breach away from total loss. A monolithic agent serving multiple tasks drifts across domains, hallucinates across contexts, and cannot be independently audited. And the scaling math is brutal: Anthropic's own research found that a single agent matched or beat multi-agent configurations on 64% of benchmarked tasks when given equivalent tools — but the 36% where multi-agent wins are exactly the high-value, high-complexity workloads Web3 cares about, where Anthropic's parallel sub-agent architecture outperformed single-agent Opus by 90.2%.

Translation: if your agent is doing anything interesting, one process cannot carry the weight. And if your agent is doing anything valuable, one process cannot be trusted with it.

Coinbase's Architectural Pivot: Wallet as Callable Service

Coinbase's Agentic Wallet reframes the wallet as a discrete service that agents invoke rather than contain. The components tell the story:

  • Agent Skills — pre-built primitives for Authenticate, Fund, Send, Trade, and Earn, exposed as callable interfaces rather than embedded logic
  • x402 payment rails — the HTTP 402 status code revived as a machine-to-machine payment protocol, with over 75 million transactions processed, 94,000 unique buyers, and 22,000 sellers across the network
  • TEE-secured CDP Wallets — non-custodial keys held in Trusted Execution Environments, never exposed to the reasoning agent
  • Programmable guardrails — compliance screening, spending limits, and usage monitoring enforced outside the agent's context window
  • EVM and Solana support from day one, with gasless transactions on Base

The key insight: the reasoning agent never sees the private key. It requests an action; the wallet service enforces policy and executes. This is the same decoupling that let the cloud industry scale from monoliths to microservices — independent scaling, isolated failure domains, and security compartmentalization.

The Emerging Specialist Agent Taxonomy

Once you accept that wallets are a service, the rest of the stack decomposes naturally. A mature agentic workflow in 2026 looks less like a single model and more like an orchestra:

  • Coordinator agents decompose tasks, verify results, and settle payments between sub-agents
  • Execution agents specialize in DeFi strategy execution, cross-chain routing, and MEV-aware transaction construction
  • Data agents handle oracle queries, on-chain analytics, and sentiment signals
  • Compliance agents apply KYC, travel-rule, and jurisdictional checks before signatures are requested
  • Interface agents translate natural-language intent into structured tool calls

Warden Protocol has built exactly this substrate. Its Agent Hub — effectively an "App Store for agents" — has processed over 60 million agentic tasks and serves roughly 20 million users as of February 2026, after a $4 million strategic round at a $200 million valuation from 0G, Messari, and Venice.AI. Warden's Statistical Proof of Execution (SPEx) provides cryptographic evidence that a task's output came from the claimed model, which is the trust primitive a coordinator needs when farming work to untrusted specialists.

The supporting standards are snapping into place. ERC-8004, which went live on Ethereum mainnet on January 29, 2026 and reached BNB Chain six days later, gives agents a verifiable on-chain identity and reputation. x402 handles the micropayment layer so agents can pay each other without API keys. Session keys built on ERC-4337 account abstraction let owners cap autonomy — "this agent can spend $50/day, anything above requires human signature" — without handing out master keys.

Identity, payment, execution proofs, and key boundaries: the four missing primitives that monolithic agents tried to fake internally are now external, composable services.

Microservices Déjà Vu — Including the Pain

Every architect who lived through the 2015-2020 microservices migration is watching this with a familiar unease. The benefits are real. So are the costs.

Multi-agent systems are more resilient, more auditable, and more adaptable than monolithic equivalents. They isolate failures, allow specialist teams to ship independently, and let you swap a reasoning model without rebuilding the wallet layer. But 40% of multi-agent pilots fail within six months of production deployment, usually because teams pick the wrong orchestration pattern or fail to understand how it degrades. Latency compounds across hops. Interfaces ossify. Debugging a distributed trace of model calls is harder than debugging a monolith — and the monolith at least has one log to read.

Web3 inherits all of this, plus a unique twist: the execution layer is adversarial.

The Agent MEV Problem

Here is the uncomfortable truth that most specialist-network evangelists avoid. Deterministic, composable execution agents are more vulnerable to MEV than their monolithic predecessors, not less.

The EVM is deterministic by design: same state plus same transaction sequence yields identical results on every node. That guarantee is the foundation of blockchain consensus, and it is also a front-running bot's dream. When a specialist execution agent follows a predictable pattern — "rebalance at 14:00 UTC, route through Uniswap V4, slippage tolerance 0.3%" — it becomes trivially observable. Sandwich bots scan the mempool for exactly those signatures. The more specialized and deterministic the execution agent, the sharper the attack surface.

A monolithic agent with messy, varied behavior was, paradoxically, partly protected by its own chaos. A disciplined specialist network is not. Which means the MEV-protection stack — solver networks like CoW Protocol, private order flow, intent-based batching, and encrypted mempools — is no longer an optional DeFi nicety. For production specialist networks it is table stakes.

What This Means for Web3 Infrastructure

The shift has a direct consequence for anyone running the pipes. A single monolithic agent generates one RPC session, one wallet signature flow, one coherent transaction stream. A specialist network operating on the same user intent generates orders of magnitude more traffic: data agents polling oracles, coordinator agents hitting reputation registries, execution agents pre-simulating across chains, compliance agents querying sanction lists, all of them settling micropayments to each other via x402.

Every one of those hops needs reliable, multi-chain data access. The API consumer profile changes from "dApp calling eth_call a few times per user session" to "swarm of agents making thousands of low-latency requests across Ethereum, Base, Solana, Sui, and Aptos within a single workflow." Rate limits designed for humans break instantly. Single-chain RPC providers become bottlenecks. Latency variance that a human user would never notice cascades across agent hops into compounded failure.

BlockEden.xyz operates enterprise-grade RPC and indexing infrastructure across 25+ chains, purpose-built for exactly this kind of high-throughput, multi-chain agent workload. If you are building coordinator or execution agents that span ecosystems, explore our API marketplace for infrastructure designed to keep up with agent-scale traffic.

The Next Eighteen Months

The pieces are now on the board: Coinbase's wallet-as-service architecture, Warden's coordination layer, ERC-8004 identity, x402 payments, ERC-4337 session keys, and a growing library of specialist agent frameworks. What comes next is the hard part — not inventing new primitives but composing the existing ones into reliable, auditable, MEV-resistant production systems.

Expect consolidation around a few dominant orchestration patterns, a brutal shakeout among the 40% of multi-agent projects that picked the wrong one, and a quiet transfer of value from "agent apps" to the infrastructure providers that make specialist networks actually work at scale. The monolithic agent was a good demo. The specialist network is the architecture that ships.

The only question left is whether the teams building on Web3 recognize the shift in time — or spend another year shipping godlike agents that cannot survive contact with a mempool.


Sources:

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.