Since I joined @ArkLabsHQ in March, I've learned a lot about @arkade_os and Bitcoin in general. Here's some of the things I've learned. Keep in mind that the tech is under active development, so some details may change. What is Arkade? Arkade is best described as an open execution engine for Bitcoin, or more broadly a toolkit for building financial applications on Bitcoin. Arkade was originally built around a transaction coordination technique that produces an onchain "batch output" controlled by multiple people. It's since evolved into a broader toolkit for enforcing custom spending conditions on any Bitcoin output. The batch output mode is what most people associate with Arkade today, though, so let's start there. In Arkade, this is made possible via a centralized operator, who constructs an onchain "batch swap" transaction that aggregates inputs from multiple users. This batch swap is similar to an atomic swap in that all participants must sign for it to be valid, and the resulting claims on the output are immutable -- neither the operator nor the users can change its spending conditions. Each claim is known as a "virtual unspent transaction output", or "VTXO" for short. The virtual bit means that it's unbroadcasted. When you own a VTXO, you own a set of transactions drawing from a batch output, that if broadcasted onchain create a UTXO only you can spend. This might sound complicated but it's not -- it's a similar state to a transaction that you've signed offline but haven't yet broadcast. Each Arkade VTXO is a Bitcoin output -- specifically, a Taproot (P2TR) UTXO. Taproot outputs are special for many reasons, but one of the more interesting ones is that they can be locked behind several independent spending paths. By default, an Arkade VTXO has two spending paths -- the first allowing for instant spending via collaboration with the operator, and the second allowing for delayed spending by the user alone. In that first path, the operator can apply additional spending conditions not currently enforced by the Bitcoin network -- for example, refusing to sign transactions that spend inputs used in a previously submitted transaction. The batch output model is Arkade's primary mode today, but it doesn't define the outer limit of the engine. Because VTXOs are just Taproot UTXOs, the same spending condition logic can apply to standard onchain UTXOs. Who is Arkade for? The main users we're targeting are people who want to build financial applications on Bitcoin. Every Arkade transaction is a Bitcoin transaction. Everything you can build on Bitcoin, you can build on Arkade. All funds on Arkade have strong, often mainnet-level finality guarantees. But you're not stuck choosing between full mainnet finality and full reliance on a custodial wrapped token -- with all the power (and vulnerabilities) that implies. When you want functionality you can't get on mainnet, you opt in to specific, limited trust assumptions (e.g. I'll trust this cosigner to enable instant spending, and this cosigner to enable passkey-based signatures). Each product picks the minimum set of trust assumptions it actually needs, rather than inheriting an all-or-nothing tradeoff. Arkade is not perfectly trustless, nor is it private. But you choose which trust assumptions you need, rather than Arkade choosing for you. Why should I use Arkade? The main reason right now is speed. Bitcoin blocks take on average 10 minutes to be mined. That means if you’re receiving funds, or even just sending a transaction with a change output returning to your wallet, you need to wait for ~10 minutes to be sure your money is secure. With Arkade, it’s instant -- the operator gives you a very strong assurance that your money is yours, and you can immediately make a new transaction. But that's just scratching the surface. The main thing we're working on is programmability. Instant spending works because the operator enforces extra spending conditions. Push that further, and you can enable new opcodes that aren't enforced by Bitcoin yet. These opcodes unlock new features like: 👉 Covenants (must send X amount to Y address) 👉 Advanced arithmetic (must deduct 5% interest) 👉 New signature curves (must provide a valid passkey signature) 👉 Zero-knowledge proofs (must prove ownership of >1 BTC without revealing exact balance) One of the quick wins this enables is non-interactive Lightning swaps. Normally, claiming a Lightning swap means coming back online to sign the claim yourself. Soon, new opcodes will let claim conditions be committed in advance, so the provider can complete the claim once funds arrive -- but the rules will still force it to be claimed to your address. That means you'll be able to generate the invoice, go offline, and the payment will still land in your Arkade wallet, ready to spend instantly or exit to mainnet. We also have a native asset protocol, enabling the likes of stablecoins, loan receipts, and membership records. How can I try it out? The best way right now is via our reference wallet: arkade.money You can receive Bitcoin from mainnet, Lightning, or within Arkade, and send out to the same. You can also swap to and from stablecoins via services like @Boltzhq and @satora_io. If you're a developer, you can try out our SDKs for TypeScript, Go, Rust and .NET. See more on our docs: docs.arkadeos.com

As I've mentioned before, @arkade_os is Bitcoin with extra steps You can inspect Arkade transactions using standard Bitcoin software like @SparrowWallet and @mempool But how is that possible when the vast majority of transactions never get published to Bitcoin mainnet?