Skip to content

Keyholder guide: what a keyholder does

Kadia is controlled by six keyholders. They’re never named anywhere in Kadia: the console shows them as Keyholder 1 to Keyholder 6, each with a short fingerprint of their public key. The same keys are used for DEX governance, the treasury, lending (since lending’s relaunch 2 on testnet) and the oracle’s governance box.

Lending has its own governance boxes: a status box (which pools are open, paused or wound down) and a release box (upgrades and the upgrader keys). On testnet the lending LP market has a separate status and release pair, with the same keys, shown in the console as “LP market governance (testnet)”. On mainnet, lending and the LP market share one pair.

A keyholder’s job is to read, check and sign proposals, using their own Ergo node and Kadia’s command-line checker, kadia-verify. Nothing a keyholder signs takes effect until enough of the six have checked and signed it too.

DEX governance lives in one box on Ergo, the governance box. Every market finds it by its NFT and reads it before each swap or deposit. The box gives the six keys two roles:

Role Signatures needed What it can do What it can’t do
Guardian 2 of 6 Pause trading, or resume it. Nothing else. Change contracts or keys, wind the DEX down, or stop anyone withdrawing, cancelling or taking a refund.
Upgrader 4 of 6 Announce or cancel an upgrade, change the guardians, change the upgraders, give up upgrades for good, and wind the DEX down. Make an upgrade take effect before its 14-day notice ends, trap funds in an old market, or announce an upgrade that takes effect after the upgrade path closes.

Two keyholders can stop trading quickly in an emergency, but changing what the markets run needs four of the six.

The console groups them in plain words. Each card says who signs and whether it can be undone.

Action Signed by Can be undone? What it does
Pause trading Guardians Yes Stops new swaps and deposits for up to 30 days per signature (renewable). Withdrawing, cancelling and refunding keep working.
Resume trading Guardians Yes Ends a pause early.
Upgrade the market contracts Upgraders Yes, until it takes effect Announces new market contracts. After a 14-day notice, each market can move to them.
Cancel an announced upgrade Upgraders Yes Withdraws an announcement before any market moves.
Change the guardians Upgraders Yes Replaces the keys that can pause and resume, or removes them.
Change the upgraders Upgraders Yes, until it’s applied Announces a new set of upgrader keys; after the notice, the current upgraders apply it.
Apply the new upgraders The outgoing upgraders No Hands the upgrader role to the announced keys.
Give up upgrades for good Upgraders No Locks the market contracts as they are, forever. Pause, resume and wind-down still work.
Wind down the DEX for good Upgraders No Closes new swaps and deposits on every market, forever. Withdrawing, cancelling and refunding keep working.
Treasury actions (gather, pay, top up the oracle deposit, refresh, move to new keys) The treasury’s holder Moving to new keys: no Spend from or look after the treasury. A payout can’t be recalled.

Some upkeep needs no keyholder: anyone may refresh the governance box when it gets old, clear an announcement left over after upgrades have ended, or collect a market’s fee into the treasury.

Whatever the keyholders sign, a user can always get their funds out:

  • A pause never stops withdrawing liquidity, cancelling an order, a refund after expiry, market upkeep, or the treasury’s fee claim.
  • An upgrade never traps funds. Orders made for the old market can’t be filled by the new one, but their cancel and refund paths never read the market, so they can always be cancelled or refunded and placed again.
  • Upgrades end on their own. The upgrade path closes for good at block height 2,550,000 (about two years after launch); after that, no announcement can take effect.

The console is a convenience, not the check

Section titled “The console is a convenience, not the check”

The governance console shows every proposal, who has signed, and the clocks. Its keyholder view appears when your wallet holds one of the keyholders’ keys, but that’s only a convenience: everything it shows is public on the chain. You don’t trust the console, or anyone’s summary, when you sign. You check each proposal with kadia-verify on your own node. The next pages show how:

  1. Run a node and kadia-verify
  2. Verify and sign a proposal
  3. Waiting periods and pauses

The founder chose on-chain proposals for treasury spending. They will run through a new council holder contract, which doesn’t touch the DEX contracts. Its six-keyholder contracts have passed a re-check by independent AI reviewers, not an outside audit firm. They aren’t locked or deployed yet, and one threshold below is still to be confirmed.

How a proposal works:

  • a keyholder creates a proposal box naming the exact asset, amount and recipient;
  • each keyholder approves with an ordinary single-signature transaction, so a browser wallet works and no node round is needed;
  • once enough have approved and the notice has run, anyone can carry it out, and it pays exactly what the proposal says;
  • during the notice, keyholders can cancel it.
Proposal Approvals needed Notice before it can be carried out Cancels that stop it
A payout 4 of 6 2,160 blocks (about 3 days) Pending confirmation
Moving the treasury to new keys (a migration) 4 of 6 10,080 blocks (about 14 days) 3 of 6

The notice counts from when the proposal is created, not from its last approval.

What each group of keyholders can and can’t do

Section titled “What each group of keyholders can and can’t do”
  • Fewer than four can’t move funds. No payout and no migration passes with three approvals or fewer.
  • Four together can pass anything, a payout or a migration. If four keyholders acted against the other two, the two couldn’t stop a migration: the notice (3 days for a payout, 14 for a migration) is the only warning, for them and for the public. Whatever the final payout rule, four could still move everything by a migration once its 14 days have run.
  • Three can stop any migration by cancelling it during the notice. If the six split three against three, neither side has the four approvals to pass anything, so the council is frozen until they agree.
  • If two keys are lost, the four left must all agree to pass anything. They can still move the treasury to new keys, which is how lost keys are replaced.
  • If three keys are lost, nothing can pass again: no payout, no migration, not even the emergency rescue, which also needs four keyholders. The treasury would be stuck for good, so lost keys must be replaced while four remain.

Until the council is finished, the treasury actions above use the same verify-and-sign rounds as DEX governance.

Technical details

Sources: kadia-dex docs/specs/r12-governance.md at commit 3cb6869 (3cb68693db1c03d2ab150a3844dcbe194a6a326b); kadia-web apps/governance (the console).

Six keyholders, guardians 2 of 6 and upgraders 4 of 6: the founder’s decision (kadia-labs, 1 November 2026). Testnet’s figures are its governance box at revision r12.

The council treasury: kadia-dex branch feat/council-n6 at commit 8c19479 (packages/kadia-council/contracts/params/council_{factory,holder,proposal}.json, vendored in apps/docs/vendor/kadia-council/). There, APPROVE is 4, NOTICE is 2,160 blocks, MIGRATE_NOTICE is 10,080 blocks and MIGRATE_CANCEL is 3. CANCEL, the cancels that stop a payout, is 3 there, but the founder hasn’t confirmed it yet: a variant with CANCEL 2 was also checked (branch feat/council-n6-cancel2). What each group can and can’t do follows kadia-ops research/final-audit/council-v6-recheck.md (1 November 2026, commit 547344e), “Delta re-check” §4, which checks kadia-council’s REVIEW.md §6 entries C1–C4:

  • fewer than four can’t move funds: §2 and “In plain words”;
  • four pass anything, two honest keyholders can’t stop a migration, and a minority veto on payouts only buys time: C3 and its clarification;
  • three stop any migration, and a 3–3 split freezes the council: C4;
  • two keys lost: C1;
  • three keys lost: C2;
  • the notice counts from creation: REVIEW.md C12.