Shared creation, anchored to Bitcoin

One object.
Two people
in control.

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.

2people
1shared object
0platform keys

Built for the things that only make sense together.

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.

A

Mutual by design

Every state change requires the current pair. Neither participant acts alone.

B

A history that grows

Each chapter becomes part of one continuous object instead of a scattered trail.

C

The exit comes first

Recovery transactions are prepared and checked before the shared state moves.

See how one shared object moves.

Explore the defined actions. This demonstration explains the state model and never creates, signs, or broadcasts a transaction.

CREATE

Begin one object together.

Two clean inputs bind the pair to one exact shared carrier. The object begins active, with both keys required for every cooperative move.

Control
Key A and Key B
Result
One active Tandem
Safety
Recovery kit completed first

A shared object should carry a reason to exist.

Explore use cases

01 / Shared record

A living archive authored by two people.

Partners, collaborators, families

02 / Stewardship

Control that can change hands only by agreement.

Teams, custodians, co-creators

03 / Milestones

One object that grows as the work grows.

Projects, collections, long arcs

What Tandem is.
What it refuses to become.

It is

  • A deterministic Bitcoin protocol
  • One jointly controlled object
  • An exact sequence of shared actions
  • A recovery path prepared in advance

It is not

  • A marketplace or investment product
  • A token, yield program, or ranking system
  • A platform with an administrator key
  • A guarantee against key loss or misuse

The public contract is exact and inspectable.

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.

Network status

Explore now.
Mainnet waits for proof.

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 path

For people building something worth sharing

Some objects belong to one person.
This one begins with two.