Mutual by design
Every state change requires the current pair. Neither participant acts alone.
Shared creation, anchored to Bitcoin
Tandem gives a pair one Bitcoin-native object they can shape together. Add a chapter, rotate either key, close cooperatively, or use a recovery path prepared before it is needed.
Protocol finalized. Mainnet is not active.
A Tandem is not a token, an account, or a promise from a platform. It is one evolving object controlled by a pair. Its history follows exact rules that any independent implementation can verify.
Every state change requires the current pair. Neither participant acts alone.
Each chapter becomes part of one continuous object instead of a scattered trail.
Recovery transactions are prepared and checked before the shared state moves.
Explore the defined actions. This demonstration explains the state model and never creates, signs, or broadcasts a transaction.
CREATE
Two clean inputs bind the pair to one exact shared carrier. The object begins active, with both keys required for every cooperative move.
01 / Shared record
02 / Stewardship
03 / Milestones
Read the authoritative protocol bytes, validate chapter and close manifests, and test against the published golden vectors. Independent implementations can conform to the same public contract without sharing a codebase.
The protocol is finalized, but mainnet is not active. Public activation requires independent verification, recovery drills, security review, signer support, and an explicit launch decision. No repository, website, or funded address activates Tandem.
Read the public readiness pathFor people building something worth sharing