A Bitcoin Cash project
Remove the trusted third party
wherever the chain can enforce the rule itself.
Most on-chain finance still rests on something you have to trust: an exchange that holds the book, an operator who can pause it, an oracle that decides the price, a company that promises the backing is real. Deviant removes those where consensus can do the job instead — and is honest about the places it cannot.
The design principle
What the chain can enforce, the chain should enforce.
This is the whole argument, and it has a corollary that governs every screen we build: a user interface is a reporter of consensus facts, never an authority. If a number on screen isn't something the chain is enforcing, we say so rather than dressing it up as a guarantee.
No operator
Swaps are single atomic transactions validated by consensus. There is no matching engine to trust, pause, or front-run — and nobody to ask permission from.
No counterparty
A backed asset carries its Bitcoin Cash inside the coin itself. Redeeming is an ordinary spend of your own funds. No issuer has to still exist, or agree.
No custody
The wallet core runs client-side, in your browser or on your device. Keys never leave it. We could not move your funds if we wanted to.
The two genuine differences
Everything else here follows from these.
Plenty of chains run financial primitives on-chain. Bitcoin Cash is the substrate that makes these two things both consensus-enforced and cheap enough to use at scale — but the substrate isn't the contribution. These are.
MBA — a backed asset that owes you nothing
Every unit carries an intrinsic, consensus-enforced amount of BCH, redeemable unilaterally by whoever holds it. Not a claim on a reserve someone reports on quarterly — the backing is present in the coin, and getting it out is a plain transaction you sign alone.
The distinction we keep insisting on: secured is not backed. In a CDP-style stablecoin, collateral backs the debt, not the token you hold. An MBA promises nothing it cannot keep.
ASM — exchange with nothing in the middle
Swaps happen in one transaction with two inputs: your asset releases the BCH it was carrying, and the target mints at whatever rate its own contract computes. No decentralized exchange, no automated market maker, no liquidity pool, no oracle, no operator.
Because it is rate-function-agnostic, the mechanism doesn't care how an asset prices itself. The protocol-as-liquidity layer is named Poseidon — always available, never asked.
The one invariant that carries the weight
A backed coin costs about 1019 bits to drain. Remove one line, and it costs about 7.
The rate peg — the contract requiring that an output's BCH value equal units × rate (in bits) — is the single load-bearing security check in the protocol. With it, draining the contract is arithmetically impossible. Without it, it is free. Eighteen orders of magnitude sit on one require statement, which is why it is the thing we test hardest and will never optimise away.
Where it actually stands
Validated on chipnet. Not on mainnet, and we won't pretend otherwise.
The protocol works end to end on Bitcoin Cash's test network — real transactions, real covenants, real adversarial tests. What it has not had is mainnet validation, per-jurisdiction availability gating, or regulatory review, all of which block any real-money use. The wallet ships with mainnet structurally absent rather than merely hidden.
L1
No rollup, no sidechain, no bridge. Every rule described here is enforced by Bitcoin Cash consensus directly.
0
Exploits, across every atomic swap executed on chipnet since the first end-to-end proof. 100% peg integrity — the load-bearing invariant above has never broken in testing.
445+
Tests passing, most of them exercising backed assets against adversarial and vulnerability scenarios rather than happy paths.
Known-open problems we don't paper over: covenants can verify that an oracle key signed but not when, so no price-freshness bound is enforced yet — that blocks every price-triggered instrument. Governance hardening is still on paper. The full list lives in the project's open-questions record, not in a footnote here.
Twenty-odd sites, one chain
The wallet, the exchange, the markets, the explorer.
Each product runs on its own name. Some are live, most are working prototypes, and the directory marks which is which — including whether a site is static or needs a server, because that determines who can host it.