Keyholder guide: waiting periods and pauses
The clocks
Section titled “The clocks”| Clock | Length | Set by | What it means for you |
|---|---|---|---|
| A pause | Up to 21,600 blocks (about 30 days) per signature | The contract | A pause names its end height. It lapses on its own, and can be renewed with another guardian round. |
| The upgrade notice | 10,080 blocks (about 14 days) | The contract | An announced upgrade, or an announced change of upgraders, takes effect no sooner than this after the announcement. Users see the countdown on the console’s public page. |
| The announcement window | 720 blocks (about a day) | The contract | An announcement records a height from the proposer’s tip to 720 blocks past it, and the transaction must be in a block by then. So an announce, cancel or renounce round has about a day to finish. |
| The upgrade sunset | Block height 2,550,000 (about two years) | The contract | After it, no market can be upgraded. A new announcement must take effect before it, and once it’s passed, anyone may clear an announcement left over. |
| The cooling-off | 24 hours after posting | The console | Nobody may sign a one-way action until it’s over. Wind-down, the emergency stop, is exempt. |
| A proposal’s life | 3 days | The mailbox | An unsigned proposal expires with its tokens and contributions. Post it again if needed. |
| The governance box’s age | 919,800 blocks (about 3.5 years) | The contract | Anyone may refresh the box after this, before storage fees could reach it. Before then, nobody can recreate it, so nobody can disrupt trades by recreating it. |
What a pause stops, and what it never stops
Section titled “What a pause stops, and what it never stops”| Market action | While paused, or after a wind-down |
|---|---|
| Swaps | Blocked |
| New liquidity deposits | Blocked |
| Withdrawing liquidity | Never blocked |
| Cancelling an order, or a refund after expiry | Never blocked: they never read the market |
| Market upkeep, the treasury’s fee claim | Never blocked |
A route through several markets fails as a whole if any of its markets is paused, so no trade half-happens. If the governance box can’t be read at all, swaps and deposits fail closed, and the console’s public page says “Treat trading as closed until it can”.
During an upgrade notice
Section titled “During an upgrade notice”- Deposits pause; swaps continue. No new money enters a market whose contract is about to change, but trading carries on until the upgrade takes effect, and liquidity can be withdrawn at any time.
- Orders for the old market stop filling once a market moves. Their cancel and refund paths still work, so users cancel and place them again, or wait for the refund.
- A firm vault can’t be withdrawn early, so its lock is capped at 10,080 blocks, the length of the notice: every firm quote expires within an upgrade’s notice.
Wind-down and renounce
Section titled “Wind-down and renounce”- Wind-down (upgraders, 4 of 6) closes swaps and deposits on every market for good. Everything in the “never blocked” rows above still works. It’s the one one-way action without the 24-hour cooling-off, because it’s the emergency stop.
- Renounce (upgraders, 4 of 6) gives up upgrades for good. The governance box stays, so that pause, resume and wind-down still work; only the upgrade path ends.
Back to what a keyholder does.
Technical details
Sources: kadia-dex docs/specs/r12-governance.md §2, §4 and §9 at commit 3cb6869 (3cb68693db1c03d2ab150a3844dcbe194a6a326b); kadia-web apps/governance/src/lib/safety.ts; kadia-gov-store’s README at 7ce1595.