Skip to main content

201 posts tagged with "Infrastructure"

Blockchain infrastructure and node services

View all tags

Glamsterdam Slips: Ethereum's MEV Reform Hits Engineering Reality as ePBS Runs Late

· 11 min read
Dora Noda
Software Engineer

For the first time in Ethereum's accelerated 2026-2027 fork cadence, the roadmap has blinked. In mid-April 2026, core developers publicly acknowledged what client teams have whispered for weeks: Enshrined Proposer-Builder Separation — the single most ambitious piece of the Glamsterdam hard fork — is "trickier than anticipated," and the original May-June mainnet window is almost certainly out of reach. The slip pushes Glamsterdam toward Q3 or Q4 2026, narrowing the gap with the already-scheduled Hegota fork and reopening a question Ethereum thought it had settled: can a five-client base layer still upgrade at the pace a post-Pectra L2 economy demands?

MCP + A2A + x402: The Three-Layer Agent Commerce Stack Web3 Developers Can't Ignore

· 12 min read
Dora Noda
Software Engineer

An AI agent wakes up at 3:17 AM, queries a DeFi analytics API, delegates a risk scoring subtask to a specialized partner agent, pays both providers in USDC, and settles the whole workflow on-chain before the coffee finishes brewing. No human clicked anything. No subscription got charged. No API key got emailed around.

That scenario stopped being theoretical in April 2026.

Three standards — Google's Agent-to-Agent (A2A) protocol, Anthropic's Model Context Protocol (MCP), and the x402 payment protocol — converged into production at the same time, forming what developers are now calling the three-layer agent commerce stack. For Web3 engineers, the window to support all three shut quietly last month: agents that don't speak A2A, MCP, and x402 simultaneously are already being routed around by their more interoperable peers.

This is not another "standard wars" drama where one protocol crushes the others. It's the opposite problem. Three complementary standards each solve a different layer of the same blockchain interaction, and none of them is going away. Here's what that actually means for developers building on Web3 in 2026.

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

Kraken's $550M Bitnomial Bet: Buying the Only CFTC-Regulated Crypto Derivatives Stack Money Can Build

· 10 min read
Dora Noda
Software Engineer

When Kraken's parent company Payward agreed on April 17, 2026 to acquire derivatives exchange Bitnomial for up to $550 million in cash and stock, most headlines framed it as another exchange consolidation story. They missed the actual point. Co-CEO Arjun Sethi gave the game away in the press release: "The shape of a market is determined by its clearing infrastructure, not its front end."

That single sentence reframes the deal. Kraken did not buy a competitor. It bought the only crypto-native company in the United States that holds all three CFTC licenses required to operate a complete derivatives stack — Designated Contract Market (DCM), Derivatives Clearing Organization (DCO), and Futures Commission Merchant (FCM) — and it did so months before its anticipated public listing. In a market where Coinbase clears its futures through a third party, CME dominates institutional notional volume, and the CFTC is actively onshoring perpetual contracts, Kraken just bought the regulatory differentiator that nobody else can replicate without years of approval timelines.

Mint Blockchain Shuts Down: The L2 Graveyard Is Now a Discipline

· 9 min read
Dora Noda
Software Engineer

On April 17, 2026, Mint Blockchain — the NFT-focused Ethereum Layer 2 launched in 2024 by NFTScan Labs and MintCore — announced it was turning off the lights. Users have until October 20, 2026 to withdraw ETH, WBTC, USDC, and USDT through the official gateway at mintchain.io/withdraw. After that date, any assets left on-chain are gone. No extensions. No exceptions.

It is tempting to read this as just another crypto project fading out. It is not. Mint's closure is the latest entry in a 2026 trend that has quietly become one of the most important structural stories in Ethereum: the "Build Every L2" era is colliding with revenue reality, and the rollup ecosystem is learning a new discipline — how to die gracefully.

Monad vs MegaETH: The High-Performance EVM Showdown Reshaping Q2 2026

· 12 min read
Dora Noda
Software Engineer

For three years, the high-performance EVM was a deck of pitch slides. By April 2026, it is two live mainnets, roughly half a billion dollars in early TVL, and an open question that will define the next two years of Ethereum-aligned scaling: does the future belong to a parallel L1 that ditches Ethereum's settlement layer, or to a real-time L2 that doubles down on it?

Monad went live on November 24, 2025 with a 10,000 TPS parallel EVM, sub-second finality, and one of the largest token airdrops of the cycle — $105 million distributed to roughly 76,000 wallets. Eleven weeks later, on February 9, 2026, MegaETH cut its public mainnet over with a different bet entirely: a single-sequencer L2 streaming transactions at 10ms blocks, sub-millisecond latency, and a stated ceiling of 100,000 TPS. Both are EVM-compatible. Both are backed by tier-one capital. Both ship today. They could not be more philosophically opposed.

This is not the parallel-EVM-vs-monolithic-L1 debate of 2024. It is the rare case where two mainnets ship within a quarter of each other, target the same Ethereum developer base, and force a choice that cannot be hedged: do you optimize for Solana-class throughput on your own settlement, or for Web2-class latency anchored to Ethereum?

Two Mainnets, Two Theses

Monad's pitch is structural. It is an L1 — its own consensus, its own data availability, its own validator set — engineered around four coupled optimizations: MonadBFT (a HotStuff derivative with single-round speculative finality), deferred execution, optimistic parallel execution, and MonadDb. The result is 400ms blocks and 800ms time-to-finality, with the chain's economic security entirely independent of Ethereum.

MegaETH's pitch is architectural. It is an L2 — settling to Ethereum, posting data to EigenDA — but it abandons the multi-sequencer convention that defines Optimistic and ZK rollups. A single sequencer node, provisioned with 100-core CPUs and 1–4 TB of RAM, orders and executes transactions through what the team calls Streaming EVM: an asynchronous pipeline that emits transaction results continuously rather than batched into blocks. The user-perceived latency is sub-millisecond. The throughput ceiling, claimed at 100,000 TPS, sat at roughly 50,000 TPS at launch with stress tests previously hitting 35,000 sustained TPS.

Both architectures break with EVM tradition. Monad keeps the trust model familiar — a validator set, BFT consensus, on-chain state — but rebuilds the execution and storage stack from scratch. MegaETH keeps Ethereum as the trust anchor but centralizes the hot path into a single high-spec node and reintroduces the latency profile of a Web2 backend.

The question is not which is technically more impressive. It is which set of trade-offs developers will pay for.

The Architecture That Drives Each Bet

Monad: Decoupled Pipelines on a New L1

The headline number for Monad is 10,000 TPS, but the more interesting figure is 400ms — the block time. That number is not a consequence of faster hardware; it is a consequence of separating consensus from execution.

In a traditional EVM chain, validators must reach agreement on a block and execute every transaction in it before producing the next block. A slow contract call can stall the entire pipeline. Monad decouples these stages: MonadBFT validators agree on transaction ordering first, and the execution engine processes the previous block asynchronously while the next round of consensus is already underway.

The execution engine itself is optimistic. Monad assumes most transactions in a block touch independent state and runs them in parallel across CPU cores. When a conflict surfaces — two transactions writing to the same account, for instance — the affected transactions are re-executed and merged. The empirical result, reported across Monad's testnet phase and early mainnet operation, is that the parallel speedup is meaningful for typical DeFi workloads where transactions tend to cluster around a few popular contracts but most state is independent.

MonadDb completes the picture. Standard EVM clients use general-purpose key-value stores like LevelDB or RocksDB; Monad ships a custom database tuned for the access patterns of an executing EVM. The combined effect — MonadBFT plus deferred execution plus parallel execution plus MonadDb — is what gets the chain to 10,000 TPS at 400ms blocks without trading away EVM compatibility.

MegaETH: One Sequencer, Many Specialized Nodes

MegaETH starts from a different question: if we accept Ethereum as the settlement layer, how fast can a single L2 execution environment go?

The answer, as the team has built it, requires breaking the symmetry of Ethereum nodes. MegaETH separates roles into specialized node types — sequencer nodes, prover nodes, full nodes — and gives the sequencer extreme hardware: 100-core CPUs, 1–4 TB RAM. This single sequencer orders transactions, executes them through a "hyper-optimized" EVM, and emits results in a streaming fashion rather than waiting for full block completion.

The 10ms block time and sub-millisecond user latency are downstream of this design. So is the centralization risk. MegaETH is explicit that the sequencer is a single point — the MEGA token's primary security role is staking by sequencer operators, with rotation and slashing intended to keep behavior honest. EigenDA handles data availability, so users can reconstruct state independently if the sequencer fails or censors. But during normal operation, one machine sees every transaction first.

This design has a clean theoretical advantage: latency dominates throughput in Web2-style applications. A real-time order book, a multiplayer game tick, an AI agent loop — all of these care more about the round-trip time of a single transaction than about the chain's peak throughput. MegaETH is betting that a category of applications exists which has been waiting for blockchains to feel like servers, and that those applications will accept a more centralized hot path in exchange for that latency.

TVL, Token Performance, and the Early Ecosystem Battle

The dollars do not yet vindicate either side. As of mid-April 2026:

  • MegaETH has accumulated approximately $110.8 million in TVL since its February 9 launch — about ten weeks of compounding from a launch-day base of $66 million.
  • Monad has crossed $355 million in TVL, with daily transactions running between 1.7 million and 2.1 million through March 2026 — a five-month head start showing.

On a TVL-per-week basis, the two are running closer than the absolute numbers suggest, and MegaETH's L2 status means a portion of its TVL is bridged Ethereum collateral that can re-deploy quickly as new venues open.

The token markets are less kind to Monad in the short term. MON trades at $0.03623 against an all-time high of $0.04883 set during the airdrop euphoria — roughly 28% off ATH but still 114% above its low. The next major MON unlock is scheduled for April 24, 2026, which traders are watching as a potential supply-side test. MegaETH's MEGA token mechanics are more constrained at this stage: the token's primary in-protocol use is sequencer staking and rotation, which limits how much float reaches secondary markets in early months.

On the dApp side, both ecosystems have aggressively courted Ethereum-native protocols. Aave proposed deploying v3.6 or v3.7 to Monad with a mid-to-late March 2026 schedule. Balancer V3 went live on Monad in March. Allora's prediction inference layer integrated on January 13. PancakeSwap brought roughly $250 million of TVL when it launched on Monad in December.

MegaETH's cleanest early win was joining Chainlink SCALE on February 7, 2026 — two days before mainnet — which immediately put dApps like Aave and GMX in reach of an oracle pipeline tied to nearly $14 billion of cross-chain DeFi assets. The bet there is leverage: rather than wait for protocols to deploy organically, plug into the connective tissue that already routes liquidity across chains.

The Developer Decision That Actually Matters

For most Ethereum developers, both chains are EVM-equivalent enough that "porting" means redeploying contracts and updating an RPC URL. The deeper choice is about which performance profile your application needs and which trust assumption your users will accept.

Choose Monad if your application is throughput-bound and value-bearing. A perp DEX matching at thousands of orders per second, an on-chain CLOB, a high-frequency lending market — these benefit from 10,000 TPS at 800ms finality and from Monad's L1 trust model where the chain's security is not delegated to a single sequencer. The cost is bridging: assets and users must move from Ethereum to Monad explicitly, and Monad's economic security is its own validator set rather than Ethereum's.

Choose MegaETH if your application is latency-bound and Ethereum-aligned. Real-time games, AI agent loops with tight feedback, order books that need 10ms ticks, microtransaction-heavy consumer apps — these benefit more from sub-millisecond latency than from raw TPS. Settlement to Ethereum means assets stay denominated in the L1's security model and bridging is cheaper. The cost is the single-sequencer trust assumption during normal operation.

The honest answer for many teams is both. The two chains are not fighting for the same application categories so much as drawing the boundary of what high-performance EVM means. Monad anchors the L1 throughput end. MegaETH anchors the L2 latency end. The middle — and most existing DeFi lives in the middle — will choose by which numbers matter more for the specific workload.

Can the High-Performance EVM Segment Sustain Two Winners?

The instinct after every L1 race of the last cycle is to expect consolidation. The 2021–2024 wave of "Ethereum killers" produced one durable winner outside Ethereum (Solana) and a long tail of chains that never escaped low single-digit billion TVL. The high-performance EVM segment in 2026 looks structurally different.

First, the architectural divergence is real, not cosmetic. Monad and MegaETH are not two attempts at the same idea with different tokenomics. An L1 with parallel execution and an L2 with a centralized streaming sequencer are not substitutes for one another at the workload level. Capital and developers can — and likely will — split.

Second, both chains target the EVM developer pool, which is by an enormous margin the largest in crypto. Roughly 90% of blockchain developers work on at least one EVM chain. Even modest fractional capture supports two viable ecosystems.

Third, the competitive set is wider than just these two. Solana continues to dominate the parallel execution conversation outside the EVM. Sei's Giga upgrade, with 200k TPS on devnet and Autobahn consensus rolling through 2026, is a third high-performance EVM contender. Hyperliquid has demonstrated that a vertically integrated chain optimized for one use case (perpetuals) can dominate without competing on general-purpose throughput. The narrative that "the high-performance EVM" will collapse to one winner mistakes a category for a single market.

The more interesting question is which of these chains becomes the default for net-new Ethereum-aligned development by the end of 2026 — the one builders reach for first when latency or throughput rules out Ethereum mainnet. On current trajectory, Monad has the lead in DeFi capital and developer infrastructure breadth; MegaETH has the lead in the consumer and agent-facing latency narrative. Both can be true simultaneously for at least the next year.

What to Watch Through 2026

Three signals will tell us how this plays out:

  1. TVL composition, not just total. Monad needs to show that capital is sticky rather than airdrop-rotated, and that protocols are deploying production volumes rather than testing. MegaETH needs to show that bridged capital converts to active strategies rather than parking.
  2. First-class native applications. Both ecosystems are still mostly populated by ports of Ethereum incumbents. The chain that produces a category-defining native application — something that could only exist there — will pull ahead in the developer mindshare race that the TVL numbers cannot capture.
  3. Sequencer decentralization on MegaETH; validator economics on Monad. MegaETH's single-sequencer model is honest about its trade-off but will need a credible decentralization roadmap to win institutional and risk-averse capital. Monad's validator set economics, particularly through the April 24 unlock and subsequent vesting tranches through 2029, will determine whether MON's security budget holds up against the chain's growth.

The high-performance EVM was a thesis for years. In Q2 2026, it became a market with two live products and a clarifying question: what kind of speed matters? Whichever side gives the better answer for the workloads of the next cycle — DeFi at scale or consumer-grade real-time apps — will set the template that the rest of the EVM ecosystem chases for the remainder of the decade.

BlockEden.xyz provides enterprise-grade RPC and indexing infrastructure across the EVM ecosystem and major non-EVM chains, supporting builders evaluating where to deploy as high-performance EVM matures. Explore our API marketplace to build on the infrastructure your application's latency and throughput profile actually needs.

Sources

peaq Network After Mainnet: Can a Polkadot Parachain Become the Ethereum of the Machine Economy?

· 9 min read
Dora Noda
Software Engineer

Sixty DePINs. Twenty-two industries. Millions of devices issuing blockchain-native identities to themselves. And a $0.017 token.

Those four numbers, placed next to each other, tell the story of peaq Network in April 2026 better than any press release. Eighteen months after mainnet launch, the Polkadot parachain built for the machine economy has the ecosystem traction of a top-tier L1 and the market cap of a mid-cycle altcoin. HashKey Capital's February 2026 research report calls peaq a foundational layer for the converging Web3-and-robotics sector. The market calls it a $200M micro-cap. One of those assessments is wrong — and figuring out which one is the most interesting question in DePIN right now.

Solana Frontier Hackathon: Can 80,000 Builders Outrun a $286M Hack and a 33% Price Crash?

· 7 min read
Dora Noda
Software Engineer

On April 6, 2026, while Drift Protocol's incident response team was still tracing $286 million in stolen assets across cross-chain bridges, Colosseum quietly opened registration for the Solana Frontier Hackathon. The timing felt almost defiant. Solana had just absorbed its largest DeFi exploit since the 2022 Wormhole bridge hack, SOL was trading near $87 after a 33% Q1 decline, and Sei Network was finalizing its EVM-only migration that same weekend — peeling off another competitor from the Solana Virtual Machine camp.

Into that turbulence, Colosseum is asking developers to spend five weeks building. The question isn't whether the Frontier Hackathon will draw a crowd. The question is whether hackathon participation can still serve as a leading indicator of ecosystem health when the ecosystem's price chart and security narrative are both bleeding.

The Frontier Hackathon by the Numbers

The Solana Frontier Hackathon runs April 6 through May 11, 2026 — five weeks, fully online, open globally. Builders compete across six tracks: DeFi, infrastructure, consumer applications, developer tooling, AI and crypto, and physical world (DePIN) projects. The prize pool sits well into seven figures, but the real draw is downstream: Colosseum's venture fund has committed over $2.5 million toward winning founders, with select teams receiving $250,000 pre-seed checks plus admission to the Colosseum accelerator.

The track record is the pitch. Across twelve Solana Foundation hackathons (four of them now run by Colosseum), more than 80,000 builders have competed. The most recent event, the Solana Cypherpunk Hackathon, drew 9,000+ participants and 1,576 final submissions — the largest crypto hackathon on record. Earlier cohorts seeded what are now flagship Solana protocols: Marinade Finance, Jupiter, and Phantom all trace lineage back to Foundation hackathons.

That history is the bull case. The bear case is everything that has happened in the last six weeks.

The Drift Wound

On April 1, 2026, attackers drained Drift Protocol — the largest perpetuals DEX on Solana — for $286 million. The mechanics matter, because they didn't exploit a smart contract bug. They exploited a feature.

The attackers spent months posing as a quantitative trading firm, building social trust with Drift contributors. They deployed a fake token called CVT (CarbonVote Token) with a 750 million supply, seeded a thin liquidity pool, wash-traded the price to roughly $1, and stood up a controlled price oracle to feed that fiction to Drift. The kill shot used Solana's "durable nonces" — a convenience primitive that lets transactions be signed now and broadcast later — to trick Security Council members into pre-signing dormant transactions that the attackers eventually fired.

Elliptic and TRM Labs both attributed the operation to DPRK-linked threat actors, citing laundering patterns and onchain timestamps consistent with Lazarus Group tradecraft. Drift's TVL collapsed from approximately $550 million to under $250 million within days. The Solana Foundation responded on April 7 with the Solana Incident Response Network (SIRN), a coordinated security backstop for protocols across the ecosystem.

For a hackathon recruiting builders one week later, the question is uncomfortable: do you start a five-week sprint to ship infrastructure on a chain where the largest perp DEX just lost half its TVL to a social engineering attack on a built-in primitive?

The Paradox: Activity Up, Price Down, Builders Steady

Here is what makes the Frontier Hackathon's timing more interesting than the headlines suggest. SOL is down 33% year-to-date, but Solana is processing roughly 41% of all on-chain trading volume — more than Ethereum and every L2 combined. The chain added more than 11,500 new developers in 2025, second only to Ethereum, and crossed 10,000 all-time unique developers in late March 2026. The Solana Developer Platform (SDP) launched in late March, bundling 20+ infrastructure providers behind a single API surface for issuance, payments, and trading.

The pattern looks less like an ecosystem in retreat and more like one in the awkward middle of a re-rating. Price action is responding to the security narrative and broader risk-off conditions. Activity is responding to the fact that Solana still settles trades faster and cheaper than its competitors. Hackathon participation will tell us which of those signals dominates among the people who actually choose where to build.

The Competition Got Sharper, Not Weaker

The April 6 start date is two days before Sei Network completes its EVM-only migration on April 8. That removes Sei's dual SVM/Cosmos compatibility from the board entirely — one fewer chain offering Solana-adjacent execution semantics. On paper, that consolidates SVM gravity around Solana itself. In practice, it means anyone who wanted SVM now has exactly one mature option, and the bar to convince them is whatever Solana's developer experience looks like in May 2026.

Meanwhile, the Ethereum side of the pipeline is not idle. ETHGlobal's 2026 calendar runs Cannes (April 3-5), New York (June 12-14), Lisbon (July 24-26), Tokyo (September 25-27), and Mumbai in Q4. HackMoney 2026 alone drew 155 teams to a single sponsor's testnet. Base, Arbitrum, Monad, and the rest of the L2 cohort are running near-continuous developer programs. The Frontier Hackathon isn't competing against a vacuum; it's competing against a fully staffed Ethereum recruiting funnel that has rebuilt itself around AI-native and consumer-crypto narratives.

The differentiator Colosseum is leaning on is conversion. ETHGlobal hackathons are talent-discovery events; Colosseum hackathons are founder-formation events. The $250K check, the accelerator slot, and the explicit commitment to fund "select winning founders" turn a five-week sprint into the front door of a venture pipeline. That model is rarer than it sounds, and it's the reason Colosseum events tend to produce companies rather than demos.

What to Watch Between Now and May 11

A few signals will tell us whether the Frontier Hackathon is reviving Solana's developer momentum or just maintaining it:

  • Submission count vs. Cypherpunk's 1,576. A flat or rising number despite the Drift overhang suggests builder conviction is structural, not sentimental.
  • Track distribution. A heavy weighting toward infrastructure and developer tooling would signal that builders are responding to the security narrative by hardening the stack. A consumer/AI tilt would signal they're betting on the next narrative cycle instead.
  • Geographic spread. Previous Colosseum events skewed toward North America and Europe. A larger Asia and LATAM share would suggest the SVM consolidation story (post-Sei) is pulling international SVM-curious teams toward Solana by default.
  • DePIN and AI-agent submissions. Both categories are where Solana's low-latency settlement matters most, and both are where the Frontier Hackathon explicitly invited entries. Strong showings here would validate Solana's pivot toward agentic and physical-world use cases.
  • Post-hackathon TVL of winners six months out. This is the only metric that matters in the long run, and the one Colosseum's accelerator model is built to optimize for.

The Bigger Bet

Hackathons don't fix exploits. They don't reverse price charts. What they do — when they work — is recruit the next cohort of founders who will build the protocols that determine whether the chart and the security narrative recover at all. The Cypherpunk hackathon delivered Unruggable, Yumi, Seer, and a handful of other projects that are now actively shipping. If the Frontier Hackathon delivers a comparable cohort, the Drift exploit will be remembered as a 2026 incident rather than a 2026 inflection point.

The harder bet is whether builders show up at all. By May 11, we'll have an answer.


BlockEden.xyz provides enterprise-grade Solana RPC and indexer infrastructure for teams building on SVM. If you're shipping at the Frontier Hackathon or hardening a protocol post-Drift, explore our Solana API services for production-ready endpoints designed for the workloads that matter.

Stacks Nakamoto + sBTC: Has Bitcoin DeFi Finally Delivered After Three Years of Delays?

· 8 min read
Dora Noda
Software Engineer

For years, "Bitcoin DeFi" has been the industry's most over-promised phrase. Every cycle, someone declares that the $1.9 trillion asset class is about to wake up. Every cycle, the capital stays on Ethereum. Now, with the Nakamoto upgrade live, sBTC past $545 million in TVL, and a decentralized signer set rotating into place, the narrative is finally meeting the infrastructure. The question is no longer whether Bitcoin DeFi is technically possible. It is whether users will show up.

From 10-Minute Blocks to 5-Second Finality

Stacks shipped the Nakamoto hard fork in late 2024, and it is the largest architectural change the protocol has ever attempted. Two shifts matter most.

First, block times dropped from roughly ten minutes (locked to Bitcoin's cadence) to around five to six seconds using "fast blocks" that still inherit Bitcoin finality. That is the difference between a chain you can use for a DeFi swap and one you can only use for settlement.

Second, Stacks can no longer fork on its own. Before Nakamoto, the chain had a theoretical 51% attack surface because miners could reorganize Stacks history independently of Bitcoin. Post-Nakamoto, reversing a confirmed Stacks transaction is at least as hard as reversing a Bitcoin transaction. You have to attack Bitcoin itself.

This is the architectural guarantee Stacks has promised since 2021. It just took three years and a complete consensus redesign to actually ship it.

sBTC: The First Serious Attempt at Trustless BTC

sBTC is a 1:1 Bitcoin-backed asset that lives on Stacks. Deposits went live on December 17, 2024. Withdrawals followed in early 2025. As of April 2026, sBTC has approximately $545 million in TVL across 7,400+ holders, with institutional minters including SNZ, Jump Crypto, and UTXO Management.

The design that sets sBTC apart from every previous wrapped Bitcoin asset is its signer set. Instead of a custodian or a fixed federation, sBTC deposits are held by a threshold signature wallet controlled by an open, economically incentivized signer network.

Signers lock up STX tokens under Proof of Transfer, run nodes, and process sBTC deposits and withdrawals. In exchange, they earn BTC rewards that PoX generates natively. There is no token-minting subsidy funding the security budget. Real Bitcoin flows to signers who do real work.

Compare this to the alternatives:

  • wBTC is controlled by BitGo. One custodian. If they go offline, the peg breaks. This risk was not theoretical — 2024 governance disputes showed exactly how concentrated that trust model is.
  • tBTC uses a threshold network of randomly selected node operators. It is genuinely decentralized but lives on Ethereum, meaning the "Bitcoin" asset spends its life far from Bitcoin's security.
  • cbBTC is Coinbase custody. It works. It is also fully centralized.
  • Babylon is not a wrapped asset at all. It lets Bitcoin secure PoS chains through BTC staking, but it does not give you a programmable BTC token to plug into DeFi.

sBTC is the first design where the BTC-backed asset lives on Bitcoin-finalized infrastructure with an open signer set that can (eventually) be joined by anyone willing to stake STX.

The Signer Decentralization Question

Here is where the honest assessment gets uncomfortable. sBTC launched with 14 to 15 elected signers — a federation, not an open-membership peg. This was always the plan. Phase 1 hardcodes trusted operators so the protocol can ship without waiting for a fully permissionless signer protocol to be production-ready.

The Q2–Q3 2025 milestone was supposed to rotate this initial cohort into a dynamically changing, permissionless signer set. That rotation is in progress but has moved more slowly than the original roadmap suggested. Stacks core developers are now floating a more ambitious redesign — fully self-custodial sBTC that further reduces trust assumptions — with a litepaper expected in 2026.

In plain language: sBTC today is less decentralized than the whitepaper describes, more decentralized than any competing wrapped BTC, and on a credible path toward genuinely permissionless signing. How quickly that path closes will determine whether sBTC keeps its trust-minimization premium over wBTC and cbBTC.

The DeFi Stack That Actually Works

Infrastructure is useless without applications. What makes the 2026 moment different from prior "Bitcoin DeFi" cycles is that the application layer has finally shipped.

  • ALEX is the anchor DEX with over $20M in TVL and a recent $10M raise led by Spartan Capital. It provides the core swap and LP functionality.
  • Arkadiko runs a CDP stablecoin (USDA) where users will be able to mint against sBTC collateral once the governance vote passes. This is the CDP-on-Bitcoin primitive that was missing for years.
  • Bitflow operates as the DEX aggregator and has launched HODLMM, a concentrated liquidity market maker built for Bitcoin trading that settles on Bitcoin via Stacks.
  • Velar runs an incentivized sBTC DEX with its own VELAR token rewards.
  • Granite delivers sBTC lending and flash loans — the building blocks that Aave and Compound gave Ethereum back in 2020.

Third-phase sBTC deposits pushed the amount of BTC locked from 1,000+ to 5,000+ coins, and sBTC TVL crossed $580 million briefly. The Stacks Asia Foundation has launched a coordinated push toward 21,000 BTC on Stacks — a symbolic target that would represent roughly 0.1% of Bitcoin's circulating supply moving into Bitcoin-native DeFi.

The Hard Truth About Comparative TVL

Stacks' $545M sBTC TVL is real and growing. It is also a rounding error compared to Ethereum's $150B+ DeFi TVL. Bitcoin's market cap sits near $1.9 trillion. The capital that has actually migrated into Bitcoin-native DeFi is a fraction of a percent.

This gap exists for three reasons:

  1. Developer preference: Ethereum's toolchain (Solidity, Foundry, Hardhat) is a decade mature. Clarity (Stacks' language) is safer and more explicit but has a far smaller developer pool. Every builder you pull onto Stacks is one you have to re-educate.

  2. Liquidity fragmentation: DeFi's flywheel requires deep pools. Stacks' $545M TVL is large enough to validate the thesis but small enough that institutional-size trades move markets.

  3. Narrative fatigue: Bitcoin holders have heard "Bitcoin DeFi is here" every cycle since 2019. Even with better infrastructure, convincing HODLers to bridge their coins takes more than technical readiness.

The path forward is not obvious. Stacks is pursuing multichain sBTC expansion via Wormhole (deploying sBTC on Sui and other L1s) and native USDC integration in Q1 2026 to solve the stablecoin-liquidity pair problem. Both are reasonable moves. Neither is a guarantee that capital migration accelerates.

Why 2026 Is the Fork in the Road

The bull case for Stacks is narrow but coherent. If sBTC hits its $1B DeFi TVL target and the signer rotation completes on schedule, Stacks becomes the default answer to the "where do you put productive Bitcoin" question. BlackRock and other institutional BTC holders that currently park coins in spot ETFs without yield gain a credible on-chain yield path. The $21,000 BTC campaign becomes a realistic milestone rather than aspirational.

The bear case is equally coherent. Rootstock, BitVM-based solutions, Babylon, and cbBTC on Base all compete for the same capital. If signer decentralization stalls or sBTC governance hits friction, wrapped BTC on Ethereum remains the default and the Bitcoin DeFi narrative dies for another cycle.

What is different this time is that the technical excuses are gone. Fast finality works. The peg functions. Real DeFi protocols have shipped. The remaining variables are execution, marketing, and whether Bitcoin holders actually want yield on their Bitcoin or whether they prefer their coins to sit quietly in cold storage.

The Builder's Verdict

For developers evaluating where to build Bitcoin-native applications, the math has shifted. Pre-Nakamoto Stacks was a research project. Post-Nakamoto Stacks is a production chain with sub-10-second user-facing latency, Bitcoin-finalized security, and a BTC-backed asset that does not require trusting Coinbase or BitGo.

The application layer still has gaps. Lending is nascent. Derivatives are immature. Cross-chain messaging relies on Wormhole rather than native Bitcoin primitives. Developer tooling needs to match the Ethereum standard.

But the premise — that you can build financial applications on Bitcoin without bridging to a foreign L1 or trusting a custodian — is no longer theoretical. Whether that premise matters enough to rewire how Bitcoin capital flows through DeFi is the question 2026 will answer.

If the answer is yes, Stacks earns a seat at the L1 table. If the answer is no, Bitcoin DeFi joins the metaverse and Web3 gaming as a narrative that sounded inevitable until it wasn't.

BlockEden.xyz provides enterprise-grade RPC infrastructure across 20+ chains, including native Bitcoin L2 support for builders shipping on Stacks and other Bitcoin-aligned networks. Explore our services to build on foundations designed to last.