Botanix: Running EVM Smart Contracts on Bitcoin with 5-Second Blocks

On July 1, 2025, Botanix launched its mainnet: a fully EVM-equivalent sidechain secured by Bitcoin, producing blocks every five seconds with average fees around $0.02. GMX and Dolomite went live on day one. Chainlink Data Feeds were integrated. The founding federation included Galaxy Digital, Fireblocks, Alchemy, and Antpool. On paper, it was the most ambitious attempt yet to bring Ethereum-style programmability to Bitcoin without wrapping BTC on another chain.

Eleven months later, on June 10, 2026, the team announced it was winding down the network. The infrastructure had maintained 100% uptime and zero security incidents. The technology worked. The demand did not. This is the story of what Botanix built, how it worked, and what its shutdown reveals about the market for EVM smart contracts on Bitcoin.

How the Spiderchain Works

Most Bitcoin sidechains rely on a single multisig wallet to custody bridged BTC. This creates a honeypot: one vault holds all deposited funds, and compromising a threshold of signers compromises everything. Botanix's Spiderchain addressed this by distributing custody across a series of connected multisig wallets, each managed by a different subset of Orchestrator nodes.

The core mechanism: each Bitcoin block triggers the creation of a new multisig vault. Signers for each vault are randomly selected from the broader validator pool using Verifiable Random Functions (VRFs) seeded by Bitcoin block hashes. This means the signer set is unpredictable and rotates continuously. An attacker would need to compromise different sets of signers across different vaults to steal all deposited BTC, rather than targeting a single static group.

Cryptographically, the Spiderchain uses FROST (Flexible Round-Optimized Schnorr Threshold Signatures) with distributed key generation (DKG). No complete private key ever exists in one place. Instead, key shares are generated directly by participating Orchestrator nodes through a cryptographic ceremony, ensuring that no single node can unilaterally sign for a vault.

Key design choice: The Spiderchain creates a web of overlapping multisig wallets rather than a single bridge contract. Each vault holds only a fraction of total deposits, and each has a different signer set. This isolates custody risk at the protocol level.

Orchestrator Nodes and Staking

Botanix used a Proof of Stake consensus model where Orchestrator nodes must stake BTC to participate. This stake served dual purposes: it qualified nodes for block production and acted as security collateral ensuring honest behavior. If an Orchestrator attempted to steal bridged funds or act maliciously, its staked BTC could be slashed.

At mainnet launch, the network operated with a 16-node founding federation. Members included Galaxy Digital, Fireblocks, Alchemy, Antpool, XBTO, Kiln, and Chorus One. The plan was to expand to a permissionless set of over 100 nodes, transitioning from a curated federation to an open validator network. That transition never completed before the shutdown.

The Execution Layer

The execution environment was fully EVM-equivalent, not merely EVM-compatible. This distinction matters for developers: EVM-equivalent means existing Solidity smart contracts can be deployed without modification. The same tooling (Hardhat, Foundry, ethers.js) works out of the box. Contracts that run on Ethereum, Arbitrum, or Base run identically on Botanix.

This made porting established DeFi protocols straightforward. GMX, one of the largest decentralized perpetual exchanges, and Dolomite, a lending and margin trading protocol, both deployed on Botanix at mainnet launch. The integration of Chainlink Data Feeds and CCIP (Cross-Chain Interoperability Protocol) gave these applications access to reliable price oracles and cross-chain messaging from day one.

What Shipped on Mainnet

Over its 11 months of operation, the Botanix mainnet processed approximately 25 million transactions across roughly 200,000 unique wallet addresses. The Spiderchain infrastructure maintained 100% uptime with zero security incidents. The network moved tens of millions of dollars in assets through its bridge.

The DeFi applications available at launch included spot and perpetual trading via GMX, lending and borrowing via Dolomite, and various token swaps. This was a functional EVM ecosystem with real liquidity and real users, built on Bitcoin settlement rather than Ethereum.

How Botanix Compared to Other EVM-on-Bitcoin Approaches

Botanix was not the first attempt to bring smart contract execution to Bitcoin. Two other projects have pursued this goal with fundamentally different architectures: RSK (Rootstock), which has been running since January 2018, and Stacks, which uses its own programming language rather than the EVM.

RSK: Merge-Mining and the Powpeg

RSK takes a fundamentally different approach to security. Rather than staking BTC, RSK is merge-mined with Bitcoin, meaning Bitcoin miners simultaneously validate RSK blocks at near-zero marginal cost. As of Q1 2026, RSK commands roughly 84% of Bitcoin's total hashrate (approximately 834 EH/s), making it one of the most computationally secured smart contract platforms in existence.

RSK's bridge, the Powpeg, uses a 5-of-9 multisig federation secured by Ledger HSMs. Peg-in takes around 17 hours (100 Bitcoin blocks) and peg-out around 33 hours (200 blocks). These latencies are a deliberate security tradeoff: slower bridging reduces attack surface. RSK produces blocks approximately every 30 seconds with full EVM compatibility via its Rootstock Virtual Machine.

Stacks: Proof of Transfer and Clarity

Stacks takes yet another approach. Its Proof of Transfer (PoX) consensus mechanism requires miners to spend BTC to earn STX token rewards, anchoring Stacks activity to Bitcoin's chain. Since the Nakamoto upgrade in October 2024, Stacks produces blocks approximately every 5 seconds and achieves 100% Bitcoin finality for its transactions.

Critically, Stacks is not EVM-compatible. It uses Clarity, a decidable, non-Turing-complete language designed to make smart contract behavior fully predictable. This means Ethereum DeFi protocols cannot be ported directly: they must be rewritten from scratch. sBTC, Stacks' BTC-pegged asset, reached $437 million in TVL with over 7,400 holders by Q1 2026.

EVM Compatibility on Bitcoin: Feature or Compromise?

The case for EVM compatibility on Bitcoin is straightforward: Ethereum has the largest smart contract developer ecosystem, the most battle-tested DeFi protocols, and the most mature tooling. If you can run the EVM on Bitcoin, you inherit all of that without building from scratch. GMX did not need to be rewritten for Botanix. It deployed the same contracts it runs on Arbitrum.

The case against is more subtle. Bitcoin and Ethereum have different philosophies. Bitcoin's UTXO model is designed for verifiability and censorship resistance. The account-based EVM is designed for expressiveness and composability. Bolting an EVM execution layer onto Bitcoin means the smart contract environment does not benefit from Bitcoin's native security model. The EVM layer runs on its own consensus (in Botanix's case, a staked federation), and the connection to Bitcoin is through a bridge, not through Bitcoin's own validation rules.

This is the fundamental tension: bridges are the weakest link in any cross-chain architecture. Every EVM-on-Bitcoin solution requires users to trust a bridge operator to custody their BTC while they use the sidechain. That trust assumption exists whether the bridge uses a federation, a multisig, an HSM, or a set of staked validators.

The bridge dilemma: Users who want Bitcoin's security properties must give up those properties to use any sidechain. The BTC on a sidechain is an IOU, not native Bitcoin. This is true for Botanix, RSK, and any federated sidechain. The only approaches that avoid this are rollups with validity proofs verified on Bitcoin L1, which remain largely theoretical for Bitcoin.

Why Botanix Shut Down

The Botanix team's post-mortem was unusually candid. They did not blame security failures, regulatory pressure, or technical limitations. The Spiderchain worked as designed. Instead, they identified structural market problems that no amount of engineering could overcome.

The Demand Problem

Bitcoin holders overwhelmingly treat BTC as a reserve asset, not as capital to deploy in DeFi. The behavior pattern the team observed: users would bridge small amounts of BTC, try a few transactions, and leave. They did not bring meaningful liquidity. The 200,000 wallets and 25 million transactions were real, but the TVL told the true story: it peaked at roughly $13.8 million and collapsed to $119,500 by the time of the shutdown announcement.

Wrapped BTC Won

Users who wanted to use BTC in DeFi were already doing so on Ethereum via Wrapped Bitcoin (WBTC) and similar products. These users had access to deeper liquidity, more protocols, and more composability on Ethereum and its Layer 2s than any Bitcoin-native sidechain could offer. Botanix's pitch of "the same DeFi, but on Bitcoin" ran into the reality that users did not value the "on Bitcoin" part enough to accept thinner liquidity.

No Token, No Incentives

Botanix deliberately chose not to launch a native token. Fees were paid in BTC. This was philosophically aligned with Bitcoin culture but eliminated the primary mechanism other Layer 2s use to bootstrap liquidity: token incentives and yield farming rewards. Without token emissions to subsidize early liquidity providers, the network could not compete with the yields available on Ethereum-based DeFi or even on centralized platforms.

Concentration of Activity Elsewhere

The team noted a growing concentration of trading activity on centralized exchanges and platforms like Hyperliquid, where convenience and institutional access outweighed decentralization. The users Botanix needed, active DeFi participants willing to bridge BTC and trade on-chain, were either staying on Ethereum or not using on-chain DeFi at all.

What This Means for Bitcoin Layer 2s

Botanix's shutdown is not an isolated event. The broader BTCFi landscape contracted sharply from a peak TVL of approximately $9.1 billion in October 2025 to around $650 million by Q1 2026: a 93% decline. The projects that survived this contraction share specific characteristics.

What Survived

• Protocols offering native BTC yield without requiring users to learn new interfaces (Babylon, Lombard)
• Chains with established ecosystems and their own token economies (Stacks with sBTC, Core DAO)
• RSK, the oldest Bitcoin sidechain, which survived through eight years of low usage by keeping infrastructure costs minimal through merge-mining

What Didn't

• EVM clones on Bitcoin that offered the same DeFi available elsewhere with thinner liquidity
• Projects without token incentives to bootstrap initial liquidity
• Chains targeting high-frequency DeFi traders who were already served by Ethereum L2s

The lesson is not that Bitcoin Layer 2s are impossible. It is that importing Ethereum's DeFi model onto Bitcoin may not address what Bitcoin users actually want. The successful Bitcoin Layer 2s are not the ones that replicate Ethereum: they are the ones that solve problems specific to Bitcoin.

Different Problems, Different Solutions

Botanix targeted DeFi developers who wanted EVM tooling on Bitcoin: perpetual exchanges, lending protocols, and composable smart contracts. This is a legitimate use case, but it competes with Ethereum's established ecosystem on Ethereum's own terms.

A different category of Bitcoin Layer 2 targets problems that Ethereum cannot solve: instant, self-custodial BTC transfers without smart contract complexity. Spark, for example, is built around statechains and FROST threshold signatures, focused on payments rather than programmable DeFi. There are no smart contracts to port, no EVM to run, and no bridge in the traditional sense: users hold real BTC in a 2-of-2 multisig with the operator set and can exit to L1 unilaterally.

This architectural difference reflects a philosophical one. Rather than asking "how do we make Bitcoin work like Ethereum?" it asks "what can we build that only makes sense on Bitcoin?" For developers interested in building on this model, the Spark SDK provides a direct integration path for wallets and payment applications.

Lessons from Botanix

Botanix deserves credit for what it accomplished technically. The Spiderchain's rotating multisig architecture was a genuine innovation over static federation models. FROST-based distributed key generation eliminated single points of key compromise. The 100% uptime and zero-incident track record over nearly a year of mainnet operation demonstrated that the engineering was sound.

But technology alone does not guarantee adoption. The Bitcoin Layer 2 space is learning that the hardest problem is not building the infrastructure: it is convincing Bitcoin holders to use it. The projects that thrive will be those that align with how people actually use Bitcoin, whether that is as a reserve asset earning yield, a payment rail for instant transfers, or a settlement layer for purpose-built Layer 2 protocols.

Botanix proved that EVM-on-Bitcoin is technically feasible. It also proved that technical feasibility is not enough.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.