Kyda Development
Block 647 · 0 connected peers · runtime v102
Open explorerPermissionless infrastructure
Validator path Help make Kyda independent.
Anyone can run a node, audit the open-source runtime, and register to become a validator. Activation is controlled until a reviewed, Sybil-resistant public governance design replaces the launch bridge.
Aura + GRANDPA
Aura schedules block authors. GRANDPA finalizes blocks. Session keys let approved operators join and leave without changing the node binary.
Open candidacy
A signed extrinsic registers any properly keyed account as a candidate. Governance cannot silently add an operator who never opted in.
From node to authority
The validator path
This is deliberately a two-sided process: operators opt in publicly, and the network applies the current anti-Sybil admission policy transparently.
Build the node
Compile the pinned stable2606 source or use the published, signed Kyda container image.
Sync as a full node
Run on the public chain spec, expose only the P2P port, and verify your node reaches the finalized head.
Register session keys
Generate Aura and GRANDPA session keys in your validator keystore. Never copy production keys into source control.
Declare candidacy
Submit kydaValidators.registerCandidate from the funded controller account. Candidacy is open to anyone.
Pass activation checks
Launch governance verifies operational readiness and anti-Sybil requirements before approval at a session boundary.