Community
post.

Sharing this here because r/Bitcoincash is the right audience to read it carefully and tear it apart if something is wrong.

What it is

A non-custodial BCH wallet plus a single CashScript contract — DeviantOpenMintFT.cash — that implements a new instrument class: an open-mint mathematically backed asset with a fixed BCH backing rate, where every unit carries its own backing satoshis inside the UTXO that represents it.

Three properties together make the construction unusual:

• Open mint. Anyone can claim units from the contract at the rate set at genesis. No allowlist, no approval, no waiting.
• Fixed rate. The redemption rate is a constructor parameter. After deployment it is invariant. No oracle, no governance, no upgrade path.
• Self-backed UTXO. Each unit's backing BCH is inside the unit's UTXO. Redemption is a standard P2PKH spend that releases the satoshis. No contract function needs to be called.

We call this construction an MBA — Mathematically Backed Asset — and the specific contract template is called DEA (Deviant Equilibrium Asset). The naming distinguishes it from a token in the conventional sense, because the asset is the locked BCH viewed through a fixed-denomination wrapper, not an accounting entry.

What's been validated

Chipnet snapshots 0001–0021. Public, dated, reproducible. Highlights:

• 450+ validation tests on chipnet to date — including atomic swaps between two open-mint DEAs at different rates that verify the Universal Exchange Rate math (UER = rateA / rateB, deterministic, no oracle, no DEX, no AMM).
• 6+ claims and matched redemptions verifying the backing-rate invariant value == tokenAmount * backingRateSats.
• T-001 attack scenario (non-canonical contract rug) and corresponding defenses D-1 and D-2 validated as PoC.
• Category byte order, reservoir model, and rate-tier dust-limit interaction documented in commit history.

If anyone wants to walk the snapshots and try to break the construction, the contract is DeviantOpenMintFT.cash and the swap test is scripts/chipnet-swap.mjs. PRs and adversarial PoCs welcome.

Why this matters for BCH specifically

CashTokens already gives BCH the substrate. Open mint plus fixed rate plus the BCH base-layer cap produces a structurally novel asset class that does not appear to be possible on chains without UTXOs and without CashTokens-style FT semantics. This is a BCH-native construction, not a port from somewhere else.

There are also some second-order properties that come out of the math:

• Every DEA in circulation increases locked BCH on the network by exactly units × rate. The ecosystem creates structural sat demand as a side effect, not as an engineered feature.
• A swap between two open-mint DEAs is a single atomic transaction. No counterparty, no liquidity provider, no slippage, no front-running window.
• The construction has a natural protocol-fee mechanism (1% on claims, 1% target-side on swaps) that funds the project from real on-chain activity, without selling anything, raising anything, or pre-mining.

How we're funding it

We are not running a fundraise. There is no token sale, no Flipstarter pledge, no equity round, no team allocation, no vesting. The contract earns a small protocol-level fee from claim and swap operations once deployed on mainnet, in the same way a miner earns a transaction fee. If users find the construction useful, the project funds itself. If not, it doesn't, and that is the correct outcome.

This is the Bitcoin model. We are aware of it. We chose it deliberately.

What we're publishing alongside

• A demonstration page that explains the construction in plain language and the categorical distinction between MBA and token.
• A fault-line registry that documents structural exposures in the conventional financial system the MBA construction renders inapplicable. Methodology-first, entries appended as events meet inclusion criteria.
• A brief addressed to readers in regulatory or supervisory roles, explaining what the construction does and does not do under existing frameworks. Plain language, no posturing.

All linked from the main project page.

What we want from this community

Three things, in order of importance:

1. Adversarial review of the contract. If there is a path to mint without backing, mint at the wrong rate, redeem more than was claimed, or break the swap invariant, we want to know before mainnet. The chipnet history is the place to start; the contract source is small enough to audit end-to-end in an evening.
2. Honest reaction to the framing. The MBA-vs-token distinction is doing real work in how we describe the construction. If the framing is off, or the language reads as marketing rather than precise, we want to hear that.
3. No retweets or hype. We are not in the announcement-cycle business. If this project belongs on BCH, it will earn its place by working. The community we want is the one that came for the protocol, not the one that came for the launch.

Tech specs, briefly

• Network: Bitcoin Cash mainnet (planned); chipnet (validated).
• Contract: CashScript, P2SH32, ~80 lines including comments. Single function claim(tokenAmount, recipientLockingBytecode).
• Architecture: A-tier (on-chain enforcement via introspection opcodes), with an optional B-tier soft layer for closed groups that escalates to A without changing identity.
• Rate tiers: powers of ten from 1,000 sats/unit to 1,000,000,000 sats/unit. Non-standard rates are rejected at deployment.
• Wallet: non-custodial, iOS / Android / desktop, single category byte order helper (txidToConsensusBytes) to handle the big-endian/little-endian footgun in CashTokens.

Links

• Demonstration: deviant.app/demonstration
• Fault-line registry: deviant.app/fault-line
• Regulator brief: deviant.app/brief
• Contract source: [repo URL]
• Chipnet snapshots: [docs URL]

Comments and critique welcome. If you are looking for promises about future returns or price targets, this is not the project for that. If you are looking for a contract you can read end-to-end in an evening and either break or trust, this is it.

— The Deviant project