Keyholder guide: run a node and kadia-verify
You sign on your own Ergo node. kadia-verify checks each proposal against that node and asks it to sign. Your key never leaves the node: kadia-verify holds no key, signs nothing itself and sends nothing to the network.
1. Run your own Ergo node
Section titled “1. Run your own Ergo node”- Use the Ergo reference node (the Scala node from github.com/ergoplatform/ergo). The signing rounds were proven on real Scala nodes, release 6.0.8, on testnet on 31 October 2026: a 2-of-5 pause and a 3-of-5 upgrade announcement, each signed by three separate nodes and mined.
- Let it sync fully before your first round. kadia-verify reads every box from it, and checks the network and genesis block against your pins.
- Keep your key in the node’s wallet. Create or restore it there, and unlock it when you sign. Never type your seed phrase or key anywhere else. No Kadia page, tool or keyholder will ever ask for it.
- Keep the node’s API on your own machine. kadia-verify talks to it only over plain HTTP on a loopback address (for example
http://127.0.0.1:9053), and refuses anything else. Set an API key on the node and keep it in a file only you can read. - Keep the wallet for governance only. kadia-verify refuses a proposal that spends a box at one of your wallet’s own addresses, so a round can never quietly spend your coins.
2. Build kadia-verify and check its hash
Section titled “2. Build kadia-verify and check its hash”kadia-verify builds reproducibly: the same commit gives the same bytes on every machine.
packages/kadia-verify/scripts/build-reproducible.sh ./dist # prints the sha256 of ./dist/kadia-verifysha256sum ./dist/kadia-verifyCompare the hash with the one Kadia publishes for that commit before you use it, and with another keyholder’s. If they differ, don’t use it.
3. Write your pins
Section titled “3. Write your pins”Your pins are the facts a proposal is checked against. You write them yourself, and never copy them from a proposal: a proposal that brought its own pins could prove anything.
pins.json (the last three fields are optional):
{ "network": "testnet", "genesisId": "<id of the block at height 1>", "governanceNft": "<the governance NFT id>", "governanceTreeHash": "<blake2b-256 of the governance script>", "reviewedHashes": ["<hex>"], "treasuryTree": "<hex>", "controlNft": "<hex>"}- genesisId: read it from your own node.
- governanceNft and governanceTreeHash: take them from the deployment’s launch manifest, and check them against the governance box on chain and with another keyholder, by a channel you trust.
- reviewedHashes: pin the market-contract hashes you’ve reviewed. kadia-verify then refuses any upgrade to a contract that isn’t on your list.
- treasuryTree and controlNft: needed for the treasury actions.
4. Check it works
Section titled “4. Check it works”Run show on any proposal, even an old one:
kadia-verify show proposal.json --pins pins.json --node http://127.0.0.1:9053 --api-key-file keyIt ends with OK TO SIGN or REFUSED: <reason>. A refusal about your network or genesis block means your pins or your node are wrong; fix that before any real round.
Next: verify and sign a proposal.
Technical details
Sources: kadia-dex packages/kadia-verify/README.md at commit 7ce1595 (7ce159587dc8c0bd78d6a5fbe0f7f8e7dde3920e); the multisig round trip (DEX definition of done, item 13, 31 October 2026).