Agreements that carry their own proof.

Five moves, and nobody has to be trusted.

A promise is a chain of signed transitions. Each one commits to the one before it, and the ones that matter are committed to Bitcoin by spending a seal that can only ever be spent once.

1. Step one

   Draft the whole agreement

   One party — the minter — writes the parties, the roles, the obligations, the milestones and their acceptance criteria, the documents, and where a dispute would go. Up to 10 parties and 50 roles. The contract is agreed as a whole, not clause by clause.

2. Step two

   Everyone signs it

   Every party signs the genesis with their VERV ID key — unanimous, or there is no promise. Signing is asynchronous by default: each party reviews and signs through the VERV ID ceremony in their own browser, in their own time, and the promise is minted once the last signature lands.

   An agreement that wants everyone present at the same moment sets the optional Ceremony flag — policies.ceremony, off unless you turn it on — and the co-signing happens live instead. Only the minter installs software; everybody else needs a browser and a link.

3. Step three

   Anchor it to Bitcoin

   The minter spends a seal UTXO in a transaction that commits to the transition hash. A seal can be spent once, so a promise can only ever have one history. This is the RGB mechanism — client-side validation, single-use seals, consignments — implemented natively. It is not an RGB asset.

4. Step four

   Verify it anywhere

   The chain travels as a portable .pp file — transitions, signatures, the DID documents used, and the anchor proofs. Anyone holding it recomputes every hash and every signature themselves, offline. No server is trusted for validity.

5. Step five

   Mediate if it goes wrong

   A dispute goes to mediation — VERV DAO by default, 50 USD-equivalent in stablecoin paid by the party filing it — and then, if that fails, to arbitration: Kleros v2, the private court KEBE, or a provider the parties name themselves. Every outcome is a signed attestation the chain verifies for itself.

The primitive, and nothing that is not the primitive.

Stage I ships the agreement, its evidence and its consequences. It never touches your money.

Bitcoin learns 35 bytes. It learns nothing else.

Anchoring publishes a commitment, not a contract. What goes into the block is a three-byte tag and one hash — the same 35 bytes whether the promise is a handshake or a hundred-page facility agreement.

Everything that means anything stays in the consignment, and the consignment goes only to the people entitled to it. Parties get the chain, because a contract is agreed as a whole. A mediator or an arbitrator gets a disclosure bundle that the filing party exports deliberately — the registry stores only its hash.

Prove the promise first. Move the money last.

Custody is the part that is easy to promise and hard to be trusted with, so it comes after the primitive is real and running.

1. Iin development

   Proof of Promise

   The agreement, its evidence and its consequences — with no custody and no escrow.

   • Payment obligations and settlement proofs; money moves outside the protocol
   • Milestones verified by k-of-n signatures over Proof-of-Event evidence
   • Disputes: VERV DAO mediation, then Kleros v2 / KEBE / custom arbitration
   • Full node with Bitcoin anchoring, plus a web light client for everyone else

2. IIplanned

   Rights and handover

   The promise starts carrying transferable things, and stops depending on one node.

   • Rights objects — contribution, payment and consent rights — and permissioned transfer
   • Seal and coordinator handover when the minter disappears
   • Promise composition, oracle and device verifiers
   • Cryptographic binding of legal identity; reputation events

3. IIIplanned

   Money on the chain

   Value moves inside the promise instead of alongside it.

   • USDT escrow on RGB, held and released by the agreement's own rules
   • Further custody rails as they become real
   • A native RGB codex once that toolchain has a released contract compiler and a wallet

A VERV product, not an island.

If this is worth building, it is worth funding.

The protocol is Apache-2.0 and the specification is public. There is no token, no sale, and no investor deck behind this — a protocol that has to sell you something before you can read it is a protocol asking to be trusted first.