Parameters only.Never control of the chain.
This site is confined to governance. The board may adjust a short list of living parameters — and nothing outside that list. It cannot move funds, rewrite the axioms, break a promise, or reverse a sealed rule. Day-to-day protocol operations live at chronx.io.
What the board may decide — and what it may not.
Authority is deliberately small. The protocol enforces both lists; no vote, majority, or emergency crosses the sealed set. Enforced by construction — not by majority goodwill.
- →The executor eligibility window and the executor model.
- →The effective fee cap — downward only. Never upward.
- →Bond sizes and the bonded-agent registry.
- →Approved platforms and asset classes for autonomous agents.
- →Per-wallet limits on open instruments.
- →An emergency freeze — in defense of the protocol, and nothing else.
- ✦The total supply — 8,270,000,000 KX.
- ✦Zero protocol fees.
- ✦Every encoded axiom — the full set of eight, including “Every promise is kept.”
- ✦Every existing promise — the grantor’s intent governs, not the board.
- ✦Timelocks. A lock’s term is the lock’s term.
- ✦Any wallet’s funds. Only the owner moves them. No master key exists.
The board cannot seize, recall, or release a promise. Recovery paths answer only to the owner’s prior election — never to a board, a node, or a court acting on its own.
ChronX Protocol Axioms.
These eight axioms are encoded in the genesis block. The board cannot amend, suspend, or override them.
version genesis_zero · count 8 · verbatim from manifest-
I
Intent
The grantor's intent governs. Software carries it out and has no authority beyond it; implementations may change, the encoded intent does not.
-
II
Fidelity
Every promise is kept
-
III
Delivery
The protocol delivers exactly what was encoded.
-
IV
Custody
The protocol takes no custody and exercises no discretion. The grantor decides at encoding; the owner's keys control; the protocol only executes the encoded terms.
-
V
Transparency
Every action is committed to the permanent public record before it executes. There are no private actions; every execution is publicly verifiable.
-
VI
Obligation
No obligation exists without the explicit consent of both parties. Verification confirms identity and eligibility; it does not guarantee performance. External agreements may govern additional terms, and collection remains between the parties and the law.
-
VII
Conditions
Any promise may encode a condition that triggers an obligation. The obligor records fulfillment; the protocol acts on that record; conditions unmet at expiry return funds to the obligor.
-
VIII
Law
These axioms are technically immutable: no person, governance body, software update, or on-chain operation can alter them. That immutability is a property of the protocol's cryptography — not a claim of supremacy over law. Persons and their conduct remain subject to applicable law.
Source: ChronX genesis manifest (sha256 61f9114a…). Runtime surface when loaded: chronx_getPromiseAxioms. The Foundation does not maintain a private diverging copy.
The board & how authority is held.
The ChronX Protocol Foundation stewards the living parameters listed above. It does not operate the product, run nodes for the public, or control wallet funds.
Governing body
A nonprofit steward with deliberately bounded power. Where keys are held for foundation functions, the design intent is multi-signature control — no single hand governs.
When published, names, seats, and public keys will appear here. Until then, treat any claim of membership outside this page as unverified.
On-chain status
Sealed bounds (supply, fees, axioms, promises, keys) are protocol-enforced today.
No master key exists. The board cannot seize, recall, or unilaterally release value. That power was never created.
Proposals.
Anyone may bring a question that sits inside the living-parameter list. Anything that touches the sealed set is out of scope by construction.
There is nothing open before the board at this time. When a proposal is active, it will appear here with its question and status.
From a submission to a permanent record.
-
Propose
Write the board with subject line Governance proposal. State the living parameter in question, the change sought, and the rationale. First contact is email.
-
Scope check
The board weighs the proposal against the operating bounds. Anything that would touch supply, axioms, fees-upward, promises, or wallet keys is declined as out of scope.
-
Decide
The board records carried, declined, or amended — with reasoning. While on-chain param actions are not yet the public surface, decisions that are taken will be listed in the archive below.
-
Archive
Decided proposals remain public here. When DAG-native proposal records are the standard path, each entry will link to its permanent vertex.
Decided proposals
| ID | Question | Outcome | Record |
|---|---|---|---|
| No proposals decided yet · archive will fill as the board acts | |||
Operating rules document — not yet published as a standalone file. This page is the public summary until then.
The ChronX Ventures Fund.
The fund is patient by design.
Ten million KX becomes available each year, starting in 2026. The board is under no obligation to disburse. A year with no grant can be the right outcome — the fund exists to back the right work, not to spend on schedule.
If you are building something the protocol should carry, write the board. Submissions that proceed become part of the public record.
- Advances ChronX’s sealed promises (custody, fidelity, long horizon) — not a generic token pitch.
- Does not require the board to break sealed bounds (supply, axioms, fees-up, seizure).
- Clear deliverable, timeline, and who holds keys / liability.
- Open to public scrutiny when funded; no silent grants.
Disbursement log
| Year | Recipient | Amount (KX) | Status |
|---|---|---|---|
| No disbursements recorded · table is the public ledger when grants begin | |||
Write to the board.
Proposals, Ventures inquiries, and questions about the bounds all go to one channel. Product support and node operations are not handled here — use chronx.io.
One mailbox. Public record later.
Email is first contact. Formal public recording happens when a proposal is opened or a grant is made — not when the message arrives.