PROTOCOL V2 · DRAFT FOR GOVERNANCE REVIEW

Alliance Protocol v2

Blockchains can't sign contracts — governance votes are the only signature a DAO has. The 2018 protocol understood this. V2 keeps its spine and adds the one thing eight years of hindsight demands: an alliance is a cooperation instrument, never an endorsement, investment, custody arrangement, or promise of returns.

The six rules

Governance is the only handshake

An alliance is official only when a specific alliance proposal passes masternode governance. Blog posts, tweets, and press releases are not ratification.

Declared, itemized, dated

Every alliance declares its purpose, envoys, deliverables, and duration — recorded in the registry before or at ratification, not reconstructed afterwards.

Twelve months, no exceptions

A hard expiry at 12 months. Continuation requires a fresh proposal and a fresh vote. Nothing runs quietly forever.

Vetting before voting

A completed vetting sheet — legal name, jurisdiction, entity registration, litigation history — accompanies every proposal. The 2018 Allnodes template, made mandatory.

Cooperation, never endorsement

An alliance is a cooperation instrument. It is never an endorsement, an investment, a custody arrangement, or a promise of returns — in either direction.

The disavowal banner

If a claimed 'partner' goes rogue or no ratifying record exists, a review notice goes up on the registry immediately — no waiting on a governance cycle. This is the exact mechanism January 2018 lacked.

The mandatory vetting sheet

Filled example survives from 2018: the Allnodes alliance — envoys, scope, risks, and a no-payments-either-way clause. Every v2 proposal carries a completed sheet before the vote.

Field	Requirement
Legal name	Full registered legal name of the entity
Jurisdiction	Country/region of incorporation and governing law
Entity registration	Registration number and public registry link
Litigation history	Material litigation, regulatory actions, sanctions screening
Purpose	Specific, deliverable-scoped purpose of the cooperation
Envoys	Named individuals responsible on both sides
Deliverables	Itemized commitments per party, with dates
Duration	Hard expiry at 12 months maximum; renewal by fresh governance proposal
Financial terms	Declared payments either way; 'no payments' must be explicit if that is the term
Reversibility	How the alliance is wound down; what happens to shared assets

01 · Legal name

Full registered legal name of the entity

02 · Jurisdiction

Country/region of incorporation and governing law

03 · Entity registration

Registration number and public registry link

04 · Litigation history

Material litigation, regulatory actions, sanctions screening

05 · Purpose

Specific, deliverable-scoped purpose of the cooperation

06 · Envoys

Named individuals responsible on both sides

07 · Deliverables

Itemized commitments per party, with dates

08 · Duration

Hard expiry at 12 months maximum; renewal by fresh governance proposal

09 · Financial terms

Declared payments either way; 'no payments' must be explicit if that is the term

10 · Reversibility

How the alliance is wound down; what happens to shared assets

Open questions for governance

Carried from the pre-proposal discussion. Resolving them is part of the proposal's work, not a precondition for it.

Q1Disavowal banner governance

Who flips and clears the banner: a maintenance multisig, or an elected steward re-approved annually?

Q2Own-project alliances

Is an independent envoy plus author abstention sufficient, or must the alliance proposal come from a separate proposer?

Q3Archive policy

Should expired alliances auto-archive, or must even dormant cooperation renew by vote?

Q4Registry scope

Should the registry list unofficial, expired, or dissolved alliances (clearly labelled, disavowal-ready), or track only currently-ratified ones? This build lists all, clearly labelled.

Want to weigh in?

The pre-proposal discussion is live on the PIVX forum. Read it, then bring your answers to the thread.

HOW TO SUBMIT AN ALLIANCE