- MoonBite
- Governance
Governance
Every rule change,
written down first.
Every change to how MoonBite works is written down first, in the open, as an Architecture Decision Record. No silent rule changes. Read the reasoning behind the chain.
- No silent rule changes
- Full text of every record
- 8 records on file
Decision log
Every record, newest first.
Each record explains what was decided and why. Open one to read its full text, including its status and date.
8 records
Process
How a rule changes
The record comes first. The code follows it, and anyone can check the running parameters against both.
Written down as a record
A change starts as an Architecture Decision Record: what is decided, why, and which earlier records it relates to or replaces. Its status (accepted, proposed or draft) is stated at the top.
Published in the open
The full text of every record is public and listed in the decision log above.
Shipped in the source
Changes to the rules land in the source code, which anyone can read and build.
Checked against the live rules
The monetary parameters are published as JSON at
/api/consensus. Compare them with the records that set them.
In force
The rules the records set
Read from the consensus parameters, not typed into this page.
Full parameter set: /api/consensus
Check the rules yourself.
The records explain the reasoning. The source code and the consensus parameters are what the network runs.