DAO-governed protocol

ShardKeep Governance.

Finalized public governance proposals. Every Warden, every Bastion, every protocol change passes through on-chain governance enforced by code — not a single company's discretion.

Proposal v2 Finalized April 2026

The Unbreakable Governance Model

Two Realms DAOs — one on DevNet, one on MainNet — hold the authority to admit new infrastructure operators to the ShardKeep network. Every Warden and every Bastion passes through a 5-gate pipeline alternating between council oversight and peer vote. Each admission produces a soulbound cNFT on DevNet, another on MainNet, cryptographically cross-bound to immovable PDA-owned node wallets. Slashing rules live in the program, not in council votes.

Read proposal → 12 sections · cNFT binding · 5-gate pipeline · Security Council

Earlier foundational proposals (role separation, warden registry, tokenomics, on-chain shard map) live in the operator portal at master.shardkeep.io/shardkeep/proposals/. Links from the v2 proposal will take you directly to each one.

Council Seats — Canonical Metadata

The five-seat governance council is instantiated on Solana as an NFT collection with one seat NFT per council member. Each NFT’s on-chain uri field points at one of the metadata JSONs below. These URLs are referenced permanently in on-chain data and must remain stable.

ShardKeep Council Seal

Council Seal

512×512 PNG shared by all council NFTs across both networks. Canonical URL: /assets/images/shardkeep-council-seal.png

Previous flat paths /council-seats/{file}.json 301-redirect to the DevNet set for backwards compatibility.