← Back to Blog

Community & Decentralisation: ShellDAO and the Path to Mainnet

·Shell Chain Team
communitygovernancevalidatorsroadmap

The thesis

A blockchain that is technically post-quantum but operationally centralised is not a post-quantum blockchain — it is a database with a long signature list. The product Shell Chain is building only matters if, by mainnet, it is run by many independent operators with no veto from the founding team.

This post lays out how we get there. It is intentionally a draft for community review, not a published policy. We expect every section to change after public input. Comments and PRs against the proposal are welcome at github.com/ShellDAO/governance.

Where we are today

  • Codebase: ShellDAO/shell-chain, MIT-licensed, 19 crates, 1,200+ tests, public commit history.
  • Consensus: weighted Proof-of-Authority (wPoA) with a small, named validator set during the testnet phase.
  • Governance: an on-chain Governance contract is live; only the validator set itself can call privileged paths.
  • Treasury: none. There is no premined token, no token sale, and no on-chain treasury contract yet.

This is a deliberately small attack surface for the testnet. It is also deliberately not what mainnet should look like.

ShellDAO: the governance design under consideration

ShellDAO is the proposed steward organisation of the Shell Chain protocol post-mainnet. The current draft has three pillars:

1. Protocol upgrades

Protocol-level changes (consensus parameters, EVM upgrades, system contract additions) flow through a four-stage process:

  1. Draft proposal — written as a SIP-XXX (Shell Improvement Proposal) Markdown file in the public governance repo.
  2. Technical review — at least one core contributor and one external reviewer must sign off; all open questions resolved in writing.
  3. On-chain vote — open to all token holders (token TBD; see below) above a participation quorum, with quadratic voting under consideration to dampen whale influence.
  4. Time-locked execution — successful proposals enter a 14-day time-lock before activation. Operators have a hard window to upgrade or to opt out by halting their node.

2. Treasury and grants

The DAO treasury (when seeded — see token economics below) is intended to fund:

  • Public goods: client diversity (a second Shell-Chain client in a different language), audits, formal verification, education.
  • Ecosystem grants: wallets, explorers, bridges, indexers.
  • Validator subsidies for the first two years to cover operating costs while transaction fees are low.

Grant decisions are made by an elected technical committee with quarterly reporting and on-chain veto by token holders.

3. Code stewardship

The ShellDAO entity holds the ShellDAO GitHub organisation, the project domain (shell.org), the testnet infrastructure (testnet.shell.org), and the release-signing keys. All are operated under multi-party control: no single individual can publish a release or change DNS unilaterally.

Validator economics (draft)

Mainnet consensus is planned to transition from wPoA to a delegated proof-of-stake variant. The current draft economics:

  • Minimum self-stake to become a validator: TBD; the goal is "high enough to be skin-in-the-game, low enough to keep the validator set geographically and politically diverse."
  • Delegation: any token holder can delegate to any active validator; delegators share rewards proportionally to stake, minus a validator-set commission.
  • Slashing: enforced from v0.17 onwards (see the v0.17 release deep-dive). Double-sign forfeits the offending validator's stake at a high percentage; unavailability above a threshold incurs a smaller proportional penalty.
  • Block rewards: emissions schedule TBD; the goal is to fund validator operations during low-fee bootstrapping without diluting long-term holders to non-recoverable levels.

We will publish a full validator economics paper before any token generation event. The paper will be open for community comment for at least 30 days before the parameters are finalised.

The token: what we will not do

Some commitments we are willing to make in advance, because investors have asked us repeatedly:

  • No silent premine. Any token allocation to founders, employees or early investors will be disclosed publicly with vesting schedules before any TGE.
  • No surprise inflation lever. The emissions schedule will be set by SIP at launch; changes will require a SIP and quorum, not a founder decision.
  • No founder veto on protocol upgrades post-mainnet. The pre-mainnet code-stewardship multisig dissolves at mainnet genesis and is replaced by the on-chain governance flow.

What we are not yet committing to is the specific economics — supply schedule, allocation percentages, vesting periods, fee burn fraction. Those are still being modelled, and we would rather get them right than publish them prematurely.

Sequencing — how we get from here to credibly decentralised

Phase What happens What it requires
Today (v0.17) Local testnet operational; permissioned wPoA. Code public, audit log public.
M14 — Public testnet External validators onboarded; faucet, explorer, public RPC at testnet.shell.org. Operator onboarding portal, validator selection criteria.
M15 — Audit #2 Second external audit on the v0.17 + testnet operational changes. Audit firm engaged, scope published in advance.
M16 — Tokenomics paper Public draft of validator economics + token schedule for 30-day community review. Internal economic model published with assumptions.
M17 — Mainnet candidate All audit findings closed; testnet runs unchanged for 90 days; release candidate signed and published. All of the above complete.
M18 — Mainnet genesis Genesis block produced; founder multisig dissolves; on-chain governance takes over. Validator set live, SIP-1 (governance bootstrap) ratified.

Dates are deliberately omitted. We will not commit to a calendar for mainnet until the audit and the testnet stability windows are passed.

How to get involved

If you want to contribute today:

  • Run a local testnet node: git clone https://github.com/ShellDAO/shell-chain && docker compose -f docker-compose.alpha.yml up -d
  • Join the wallet effort: the Shella Chrome wallet is in active development and accepting contributors.
  • File an issue: any bug, any inconsistency, any documentation gap on ShellDAO/shell-chain/issues.
  • Apply to be a public testnet validator when the M14 portal opens. Subscribe at x.com/orgShell for the announcement.

Closing

Post-quantum security is a public good. The right way to ship a public good is in public, with operators and contributors who do not need our permission to keep it running. ShellDAO is the structure we are building to make that possible.

This is a draft, not a manifesto. The next twelve months will tell us which parts survive contact with reality.