Governance is one admin wallet with a small set of powers, among them the pass fee. The Network page shows its state to everyone and its controls to the admin.
Set up a deployment#
-
Initialize governance. The program's upgrade authority signs Sign and initialize and becomes the first admin. The program checks the upgrade authority through its ProgramData account, so nobody else can initialize it.
-
Upload the verifying key. Choose the reviewed version 1 key file, 2,816 bytes. The app shows its SHA-256 and uploads it in 512-byte pieces, one transaction each, then finalizes it. A finalized key never changes; rule sets and proofs need it.
-
Register verifiers. Enter each provider's signing key and Sign and register.
-
Set the pass fee. Enter what each recorded rule pass costs its rule set's issuer and Sign and set. The first setting opens the protocol account the fees are paid into; passes are recorded once it exists.
Day to day#
| Action | Effect |
|---|---|
| Pause Writ | New credentials, rule sets, mint bindings, passes, issuance and every hooked transfer stop. Revocation still works. Existing rule sets and passes stay as they are. |
| Resume Writ | Everything runs again. |
| Deactivate a verifier | Its generation moves on; its credentials and their passes stop counting. |
| Reactivate a verifier | It may issue again; credentials from before stay stale until reissued. |
| Revoke a credential | Moves that credential's epoch; its passes stop counting. |
| Change the pass fee | Applies to every pass recorded afterwards. Zero is allowed. |
Handing over administration#
Administration moves in two steps so it cannot land on a wallet that cannot sign:
-
The admin enters the new wallet and signs Sign and propose.
-
The new wallet connects to the Network page and signs Sign and accept.
Until the new wallet accepts, the current admin keeps every power and can propose another wallet instead.