> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/5.-system-architecture-and-network-economics/5.5-genesis-ceremony-and-network-bootstrap.md).

# 5.5 - Genesis Ceremony & Network Bootstrap

Polarischain employs a two-tier genesis model to ensure cryptographic integrity, decentralized verification, and tamper-proof initialization.

**Permissioned-Beta Genesis (Current Phase)**

The Foundation orchestrates genesis using the `polaris genesis-ceremony` tooling (v1.3+ operator UX):

1. **Committee Configuration:** Generates schema v2 validator manifest with stake, PQ transport keys, and network addresses.
2. **Per-Validator Config Distribution:** Dilithium2, X25519, and ML-KEM-768 private keys are distributed out-of-band via a secure operator portal. Keys never leave the operator's environment.
3. **Deterministic Genesis Block:** Constructed via `Block::genesis()` with a fixed timestamp (`t=0`), ensuring all validators independently compute the identical genesis digest regardless of local clock drift.
4. **Initial Token Allocation:** `$POLA` is distributed to genesis wallets per the approved tokenomics schedule (Foundation, treasury, validator operators, community pools).
5. **Threshold Validation:** Validators independently verify the genesis blob. Mismatched configurations fail threshold-clock validation on round 1, surfacing misconfigurations immediately.

**Mainnet Genesis Ceremony (Phase 5+)**

For multi-organization mainnet deployment, the procedure expands to a decentralized, Sui-style multi-party ceremony:

1. **Coordinator Initialization:** Foundation publishes an empty genesis working directory (synced via private Git repository).
2. **Per-Validator Contribution:** Each validator independently submits public keys, network addresses, validator identity, and a Dilithium2 signature over their contribution.
3. **Token Allocation Finalization:** Validator, ecosystem, treasury, and public-distribution allocations are embedded per the tokenomics framework.
4. **Unsigned Genesis Blob Construction:** Coordinator assembles the full committee, allocations, deterministic genesis hash, and initial protocol parameters.
5. **Independent Verification & Signing:** Each validator downloads the blob, audits every byte against expected state, and signs with their Dilithium2 key.
6. **Quorum Aggregation:** Once `≥ 2f+1` signatures are collected, the coordinator finalizes `genesis.blob` with the quorum-signed manifest.
7. **Distribution & Launch:** Validators embed `genesis.blob` before startup. The protocol verifies quorum signatures on first boot and rejects initialization if validation fails.

This quorum-signed genesis ensures no single entity can unilaterally alter initial state. Ceremony tooling is open-source, enabling independent verification and reproducible blob generation from public inputs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://polarischain-1.gitbook.io/polarischain/5.-system-architecture-and-network-economics/5.5-genesis-ceremony-and-network-bootstrap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.