Skip to content
MoonBite
  1. MoonBite
  2. 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

Process

How a rule changes

The record comes first. The code follows it, and anyone can check the running parameters against both.

  1. 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.

  2. Published in the open

    The full text of every record is public and listed in the decision log above.

  3. Shipped in the source

    Changes to the rules land in the source code, which anyone can read and build.

  4. 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.

Block time2 minSet by ADR-010
Initial block subsidy10 MBITESet by ADR-010
Halving interval1,650,000 blocksSet by ADR-010
Supply cap32,999,999.78550000MBITE, locked by ADR-011

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.