Bounded mining
Mining licenses, authenticated presence, deterministic assignments, and memory-hard work put protocol limits around participation. More raw hardware can finish work sooner; it does not create unlimited eligibility.
A device-first monetary protocol
No Masters.
Only the Many.
Mutiny is a decentralized monetary protocol designed to put participation back into ordinary hands.
Mining should not be an endless race for specialized hardware. A monetary network should not require a trusted payment oracle. Ownership should not demand unnecessary identity.
Mutiny is being built around different assumptions.The protocol
Built for participation.
Designed for verification.
Bitcoin-verifiable economics
Applicable license purchases can be verified from Bitcoin evidence inside the protocol—without depending on an exchange API or a Mutiny-controlled payment database.
Security by separation
Owner authority, mining authority, node identity, and spending credentials are deliberately separated. Watch-only operation and offline signing keep ownership from becoming an always-online secret.
Consensus, not administrators
Canonical encoding, authenticated state, deterministic replay, and explicit network rules let independent nodes reach the same result without a master operator deciding what is valid.
How it works
Rules that make participation legible.
Mutiny treats mining eligibility, proof, state, and payment evidence as protocol concerns—not business logic controlled by a website.
Licenses are cryptographic records with identical semantics, not “basic,” “pro,” or industrial mining classes. A license owner may delegate mining authority without giving a device control of the wallet.
- 1Authorize
A cryptographic license defines eligible participation.
- 2Prove presence
Recent authenticated mining presence establishes an active window.
- 3Perform assigned work
Deterministic assignments and bounded proof make work independently checkable.
- 4Verify and commit
Independent nodes validate canonical blocks and authenticated state.
Bitcoin, independently verified
Payment evidence belongs in consensus.
Mutiny maintains Bitcoin header and best-chain state, validates proof-of-work and timing rules, and evaluates bounded confirmation evidence. The goal is simple: a node should be able to prove the relevant Bitcoin event for itself.
Treasury custody is designed for threshold control. It is not a promise that MUT is redeemable for Bitcoin.
Hostile by default
The network has to survive the real world.
Mutiny’s reference node has been exercised across independent peers, replay, reorganization, restart, crash recovery, WAN partitions, malformed handshakes, and connection pressure. Correctness must hold when the Internet breaks—not just when a demo runs perfectly.
The Mutiny ecosystem
One protocol.
Many ways to participate.
The reference node is the consensus foundation. The user-facing participation layer is still being built.
Protocol foundation
Implemented & validated
- Core consensus and UTXO transactions
- Licensed mining and authenticated workers
- Bitcoin SPV-style verification
- Encrypted keystore and offline signing
- Authenticated P2P and multi-node recovery
Participation layer
In development
- Android wallet and miner
- ESP32 production firmware
- LoRa and Bluetooth adapters
- NFC payment experience
- Consumer wallets, explorers, and tools
Internet · Wi-Fi · Bluetooth · NFC · LoRa Transport carries information. Consensus determines validity.
Development status
Protocol first.
Public launch later.
Mutiny Protocol is in development. Mainnet is not yet public. There is no sale, no investment offering, and no promise of future value. The work is being documented in public while the protocol and ecosystem mature.
Join the development record →The many
Build in public.
Follow milestones, discuss the protocol, and help test what is being built.