Skip to content
ADR-0076Architecture decisionAcceptedversion 1.0.012 November 2026

In short ​

The network's joint decisions (admitting a member, upgrades, network schemas) need the votes of at least two members. If the network has two members and one of them leaves of its own accord, a single member remains, and a single member cannot take any decision alone. Since no new member can be admitted either, the network cannot leave this state. This decision prevents reaching that point: unilateral exit is refused in a two-member network; a member that wants to leave first waits for a third member to be admitted, then withdraws without a vote.

Context ​

  • ADR-0002 #5: a state can leave unilaterally with withdraw(); no vote is needed and the guarantee is in the code.
  • SPEC-BC-0001 §1 (independent review finding R6): because the 2/3 rule loses its meaning below three members, requiredVotes never goes below 2. The same section says that removal is impossible in a two-member network and that both sides "can only withdraw voluntarily".
  • Contract audit (2026-11-11), confirmed by a test (behaviour before this decision): with 2 active members, withdraw brought the count to 1. After that
    • every proposal of the remaining member fails with ThresholdNotMet(1, 2) (admission of a new member included);
    • the remaining member cannot withdraw (LastValidator);
    • contracts cannot be upgraded, network schemas cannot be written, and list anchor writers and the migration window cannot be managed. National records are not affected (the remaining state keeps writing its own records); what locks is network-level governance, and there is no way back.
  • The same state can arise at initialisation: initialize accepts a single founder, and with one member no proposal can be executed. Today this is used only in local development set-ups. There is no production chain, and it opens with at least two independent operators (ADR-0009 K4).
  • Because two closed rules conflict, the code was not changed before the decision; the rule was set by this document.

Options ​

OptionWhatForAgainst
(a) Exit waits at two memberswithdraw is refused while the network has 2 active members. A member that wants to leave first waits for a third member to be admitted, then withdrawsGovernance never locks; a small, local code change; R6 is keptThe right to exit is deferred in a two-member network: if the other member does not vote to admit a new member, the exit does not take place on chain (the member can stop its validator and stop writing records, but still counts as a member)
(b) Threshold 1 with a single memberwithdraw stays free. With 1 active member requiredVotes returns 1; the remaining member can admit new membersThe right to exit is fully kept; no lock; single-founder initialisation works tooThe single remaining member takes every network-level decision alone: after the 7-day delay it can upgrade the contracts and affect the records of the states that left. R6's guarantee that "one state cannot decide alone" is lifted in a one-member network
(c) BothExit is refused at two members; threshold 1 for a single-member initialisationThe lock is closed on both pathsTwo separate rules; a one-member network is not wanted in production anyway (ADR-0009 K4)
Do nothingThe rule stays in the operations documents: "in a two-member network, admit a third member before withdrawing"No code changeA single transaction locks the network irreversibly; no protection against a mistake or a dispute

Recommendation ​

(a). Reason: a two-member network behaves, in the specification's own words, like a partnership; the purpose of the right to exit is not to let one partner stop the network's joint governance for good with a single transaction. (b) opens the lock but leaves all network-level authority with one state; the on-chain records of the states that left stay exposed to that state's upgrade decision. Under (a) the right to exit is not removed, it is tied to an order. Proposed rules (moved to the binding table if accepted):

  1. withdraw is refused while the network has 2 or fewer active members (today only the last member is refused).
  2. ADR-0002 #5 is read with this note: unilateral exit needs no vote while the network has at least three active members; in a two-member network it is used after a third member has been admitted.
  3. Single-founder initialisation is for local development only. Whether initialisation should require at least two founders is decided separately: local development and test network set-ups can run with one founder today, so this draft does not change it.
  4. The error name and the specification text are approved at acceptance.

Decision (2026-11-12) ​

(a) accepted as recommended. The binding rules are GC1–GC3 below; the name follows the table. Whether initialisation should require at least two founders was left to a separate decision that day; it was closed the same day by the additional decision below (GC4).

Additional decision (2026-11-12): at least two founders ​

The network is founded by at least two founders. The approved direction: mandatory in the real network; a single-founder set-up at most for local development and tests, behind an explicit flag. Two ways of implementing it were considered:

WayWhatResult
(i) Mandatory in the contractGovernance.initialize refuses fewer than two founders; tests and local scripts set up with two founderschosen
(ii) In the set-up scriptsThe contract keeps accepting a single founder; the set-up scripts accept a single founder only on local chain ids or with an explicit flagnot chosen

Reason: (ii) binds only this repository's scripts; someone who deploys the contract with another tool can found it with one founder, and the rule stays in habit, not in code. Under (i) the rule is in the contract itself, like GC1. A single-founder flag turned out to be unnecessary as well: the local development chain, the test network and the contract tests were already set up with two or three founders; a single-founder governance cannot execute any proposal, so it has no behaviour to test. No flag was added; if one is needed later it is added by a new decision. No new name was needed: the existing FounderMismatch error is used (the same error as the "fewer than two founders" check on the founder recognition proposal).

Invariants ​

CodeRule
GC1Unilateral exit (Governance.withdraw) passes only while the network has at least three active members; it is refused while the network has 2 or fewer active members (TooFewMembers). Neither exit nor removal can bring the number of active members below the absolute minimum of votes (2): governance always stays able to decide.
GC2In a two-member network the path for a member that wants to leave is ordered: a third member is admitted first (proposeStateAdmission, with the votes of the two members), then the member leaves with withdraw; this second step needs no vote. Until the admission takes place the member can stop its validator and stop writing records; its membership continues.
GC3ADR-0002 #5 is read with this note: the right to exit is not removed, it is tied to an order. In a network with at least three active members it is unilateral, needs no vote and is guaranteed in code. The effect of an exit on credentials does not change: issued credentials and existing records stay valid (ADR-0002 #4).
GC4The network is founded by at least two founders: Governance.initialize refuses fewer than two founders (FounderMismatch). The set-up scripts and the key map check the same rule before deployment; there is no flag or exception for a single-founder set-up.

Name (public ABI; following the existing error naming pattern — TooManyDelegates(count, max)):

WhereName
Governance errorTooFewMembers(uint32 active, uint32 required) — active: the number of active members at the time of the call; required: the minimum number of active members for a unilateral exit (3)

Consequences ​

  • Governance.withdraw: a one-line change of the condition (activeMemberCount ≤ 2 → refused). Storage layout and function signatures do not change; one error is added to the ABI. LastValidator remains only on the removal proposal.
  • GC4: the condition in Governance.initialize (founders.length < 2 → FounderMismatch); the ABI and the storage layout do not change. The set-up code checks the same rule before deployment, with an explicit message (contracts/scripts/lib/deploy.ts, network-setup.ts; key map apps/chain-indexer/src/chain-keys.ts, network/testnet/testnet.mjs). network/testnet/make-network.sh writes no key map for a one-validator network (node-level checks only). The number of QBFT validators and the number of founders are different things: the local one-validator development chain also sets the contracts up with two founders (TR, KZ).
  • Tests (contracts/test/review-2026-11-11-governance.test.ts, contracts/test/governance.test.ts): one of three members withdraws (3 → 2), exit is refused in a two-member network (2 → 1), and once a third member has been admitted the exit passes and the two remaining members keep deciding.
  • SPEC-BC-0001 §1 and §14 item 8 (closed); an implementation note on ADR-0002.
  • Remaining limit (deliberate): in a two-member network, if the other member does not vote to admit a new member, the exit does not take place on chain. The member can stop its validator and stop writing records; the membership record continues. This follows from a two-member network behaving like a partnership (SPEC-BC-0001 §1).
  • Implementation note (2026-11-12; the decision itself is unchanged) — key backup while the network has two members. If a member of a two-member network loses its governance key (today the same key as the validator node key), that member cannot vote. The remaining member cannot pass any proposal alone (minimum absolute vote 2); the member that lost its key cannot be removed (there is no removal in a two-member network, SPEC-BC-0001 §1) and cannot withdraw (GC1; withdrawal also needs the same key). The only way to change a validator address is re-admission, which needs two votes. Governance then falls into the lock that GC1 prevents, with no way back. For this reason, with the approval of project management (2026-11-12), the operating rule is: until a third member joins, every member must keep a backup of its governance key that is stored in a place separate from the key itself and has been tested by restoring it. The rule is an operating rule (the contract cannot check it); its place in the operations document is ARCH-0002 Step 11. In a network of three or more members, a member that loses its key can be removed by the votes of the others and re-admitted with a new address; a backup is recommended there too.

Status ​

Accepted — 2026-11-12. Approved by project management (2026-11-12): option (a), as recommended; the same day the additional decision GC4 (at least two founders). DECISIONS: D-GOV-12. GC1–GC4 are binding. Implementation: Governance.withdraw, Governance.initialize (SPEC-BC-0001 version notes).