Arkade

• Name: Arkade
• URL: https://arkadeos.com/
• Category: Bitcoin programmable execution layer / VTXO-based offchain settlement infrastructure / Bitcoin-native assets and contract platform
• Tags: bitcoin-ecosystem
• Summary: Arkade is a Bitcoin execution layer built around operator-run virtual-mempool state, VTXO balances, and batched settlement back to Bitcoin. The useful part is not the Bitcoin L2 slogan; it is the explicit operator control plane for admission, settlement, asset support, and SDK-mediated app behavior. Keep this note on that protocol-and-product surface. The named organization that builds, operates, and packages the easiest live path around Arkade now lives separately in ark-labs.
• What it does:
  • Exposes an SDK-driven application environment where clients connect to an Arkade operator and execute transactions instantly in an offchain Virtual Mempool before later settling to Bitcoin L1 in batches
  • Uses VTXOs nested inside shared taproot batch outputs so users retain independently spendable balances plus unilateral exit paths back to Bitcoin even without operator cooperation
  • Supports Bitcoin-native smart-contract patterns including escrows, payment channels, Lightning channels, Lightning swaps, hash-time-locked contracts, and other programmable spending conditions documented in the contract guides
  • Positions itself as infrastructure for payments, lending, trading, smart wallets, delegation, recovery flows, and stablecoin or other asset issuance on Bitcoin
  • Extends the stack with Arkade Assets, a framework for native multi-asset issuance and transfer that uses OP_RETURN/TLV data, control assets, and teleport-style commit-reveal transfers across batch swaps
  • Ships supporting software through Ark Labs repositories including Fulmine, a wallet daemon for Arkade services, and a BTCPay Server plugin for accepting self-custodial Bitcoin payments via Arkade
• Key claims:
  • The official site calls Arkade “An operating system for money” and says it brings “financial applications directly to Bitcoin” with “no wrappers, no bridges, no compromises”
  • The docs homepage and primer say Arkade is a programmable execution layer for Bitcoin that enables payments, assets, swaps, and smart contracts with instant settlement while users retain full custody and no Bitcoin consensus changes are required
  • The primer says applications connect to the Arkade operator through the SDK, transact in the Virtual Mempool, settle through batch settlement, and can always exit unilaterally to Bitcoin L1
  • The primer explicitly says the operator processes and coordinates settlement but “cannot steal funds or prevent withdrawals,” which is one of the clearest trust-model claims in the primary materials
  • The docs index and contract pages show first-party support for chain swaps, Lightning swaps, Lightning channels, escrows, Spilman and Dryja-Poon channels, and an arkd server stack, indicating the project is being built as an application platform rather than only a wallet UX
  • The Ark Labs blog says Arkade processed mainnet payments at Baltic Honeybadger 2025 using existing Lightning wallets such as Phoenix, Wallet of Satoshi, and AQUA, with merchants receiving VTXOs through Arkade’s Boltz integration and BTCPay plugin-backed merchant flow
  • The Arkade Assets blog says the framework is designed to bring stablecoins and other digital assets to Bitcoin natively within Arkade and describes control assets plus a teleport commit-reveal mechanism for moving assets across batch swaps
  • The Ark Labs GitHub organization describes Ark as a fast, low-cost Bitcoin layer-two protocol and publicly exposes repositories for Fulmine, a BTCPay Server plugin, demos, explorers, and other Arkade infrastructure, reinforcing that there is a real operator/developer stack behind the docs narrative
• Whitepaper: No current canonical standalone Arkade whitepaper or litepaper surfaced in this pass. The current docs explicitly tell readers to prefer the docs and glossary over older whitepapers or third-party specs, so the clearest source of truth was the official site, docs corpus, blog posts, and GitHub repositories; see ../whitepapers/arkade-primary-sources-2026-05-03.md. For the named-operator split added in this pass, see ../whitepapers/ark-labs-company-primary-sources-2026-08-09.md.
• Sources:
  • https://arkadeos.com/
  • https://docs.arkadeos.com/
  • https://docs.arkadeos.com/primer
  • https://docs.arkadeos.com/llms.txt
  • https://blog.arklabs.xyz/closing-the-lightning-loop-bitcoins-missing-layer-secretly-goes-live/
  • https://blog.arklabs.xyz/native-assets-on-bitcoin-introducing-arkade-assets/
  • https://github.com/ArkLabsHQ
  • https://github.com/ArkLabsHQ/fulmine

Internal linkages

• VTXO lineage and custody baseline: ark and bark.
• Closest Bitcoin offchain-state comparison: spark.
• Company / operator boundary above the official service, docs, and rollout shell: ark-labs.

Protocol / company boundary

• Keep this note focused on Arkade itself: the Virtual Mempool, VTXO ownership model, unilateral exits, batch settlement, Arkade Assets, and the application-facing execution path.
• Use ark-labs for the named organization that the docs say builds, maintains, and operates Arkade, publishes the canonical docs and repos, and packages Fulmine, merchant integrations, and partnership-led rollout.
• That split matters because how does Arkade work? and which company currently shapes the easiest service and integration path into Arkade? are related but not identical questions.

Control surface

• Arkade’s protocol note should still keep the operator role visible, because the live system is explicitly operator-mediated even while the docs try to bound that power with unilateral exits and signing separation.

• But the thicker entity boundary around official documentation, default service expectations, liquidity/delegate tooling, and merchant rollouts now points upward to ark-labs because those are named-organization questions rather than pure protocol mechanics.

• Last reviewed: 2026-08-09 UTC