1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
# Monzero (XMZ) chain specification
This document records the initial consensus and network parameters for the
independent Monzero chain. Any change to a consensus value after public launch
requires a coordinated network upgrade.
## Monetary policy
- Name: Monzero
- Ticker: XMZ
- Target primary emission: 100,000,000 XMZ
- Atomic precision: 11 decimal places (1 XMZ = 100,000,000,000 atomic units)
- Emission curve: Monero-style smooth emission, speed factor 20
- Target block time: 120 seconds
- Permanent tail emission: 3.26 XMZ per block
- Hard-coded premine: none
- Pre-release allocation: coins mined normally during the private bootstrap and
test period; the mined amount and addresses must be disclosed before launch
Eleven decimal places is the greatest precision compatible with a
100,000,000-coin primary emission and the core's unsigned 64-bit amount type.
Twelve decimals would overflow that type.
## Mainnet identity
- Official website: `https://monzero.org` (project metadata; not consensus-critical)
- P2P port: 6174
- RPC port: 6175
- ZMQ RPC port: 6176
- Network UUID: `fc3291ba-8666-4b87-8ebb-d59b72d4fcaa`
- Standard/integrated/subaddress prefixes: 86 / 87 / 88
- Genesis nonce: 818137480
- Genesis block hash: `3850cb9e2fb2ba3c680b24cee7574765acd6be1cc4d84a4360c7c53e83e3270d`
- Default data directory: `.monzero`
- Executables: `monzerod`, `monzero-wallet-cli`, `monzero-wallet-rpc`
The complete protected mainnet, testnet, and stagenet vectors are available in
the machine-readable `config/monzero-consensus.json` manifest. Compiled unit
tests regenerate each genesis block and fail if monetary policy, address
prefixes, ports, UUIDs, nonces, hashes, transaction version, or hard-fork
schedule drift unexpectedly.
## Bootstrap and launch policy
Monzero does not embed a special premine transaction. The team may privately
mine the initial blocks for network testing. Before public launch, publish:
1. The UTC timestamp and block height at which public launch begins.
2. Every address controlled by the team and its balance at that height.
3. The total privately mined XMZ and its intended use.
4. Stable seed-node hostnames or IP addresses.
5. Reproducible release binaries and the corresponding source commit.
The inherited protocol revisions activate over blocks 1 through 16. Public
launch should occur only after block 16 so all public mining uses v16/RandomX.
## Items intentionally pending
- Public launch date and UTC time
- Project domain
- DNS and fixed-IP seed nodes
- Public checkpoints created after the bootstrap period
- Written allocation rationale and vesting/custody commitments
- Independent consensus and cryptography review
|
