Roadmap

The path to mainnet

Four main stages: closed testnet with economics testing, stress testing, open testnet, and mainnet with the same rules. Mainnet is planned for Q1–Q2 2027 — a working target, not a promised date.

Closed testnet — now

We are here

The network rules are on from the start: a block every 60 seconds, the XMOR coin, private transfers and names from block 1, and rewards for relays (the servers that deliver messenger traffic) from block 2. Nodes, pool, gateway and relays run on servers operated by the project; participation is by invitation. Four weeks of relay and name economics testing are planned for the closed testnet. The testing will use the project’s relays, fake relays set up specifically for testing and name-buying bots.

Stress testing

The network is deliberately attacked: malformed transactions it must reject, long fuzzing runs on the private structures, cross-checks against Zcash reference vectors, and testing the emergency switch. Testers’ findings are part of this check. Before the open testnet there will also be a week of resilience testing: the network will be tested under deliberate attacks and service failures. Everything found is fixed before mainnet.

Open testnet

Planned

Independent relays, miners and nodes on independently operated machines will be able to join the testnet. The open testnet is planned after about 30 days of closed testnet with no consensus bugs found — bugs in the rules nodes use to accept blocks.

Mainnet — target: Q1–Q2 2027

Planned

Before launch: final network parameters, signed releases and a release candidate for a final check. Before mainnet launch, the open testnet must run for 30 to 90 days with no consensus bugs found. Mainnet starts with the same rules from the first block: no reserve, no premine, no coin sale. The date is a working target, not a promise.

Open testnet

Separate tests

Separate tests of relay-based VPN and the MorPow algorithm are planned for the open testnet. The results will determine whether they are used on mainnet.

VPN on relays

In the test branch, relay operators will be able to choose to run a VPN on their server with a separate IP address. By default, connections will pass through two endpoints run by different operators: the entry sees the user’s IP address but not the destination; the exit sees the destination but not the user’s IP address. The VPN is planned as a messenger module. Users will pay operators directly through private transfers, with no accounts. The testnet will offer a free quota and payment in test coins. The test results will determine whether the VPN is used on mainnet.

MorPow

MorPow is the working name for a KawPow variant with its own constants and a small table in the GPU cache. It is intended to support older GPUs as well. The goals are to make attacks using rented standard-KawPow hashpower harder and to reduce power consumption on individual cards. Compatibility and power use will be checked on a separate test network with its own miner. The current network runs on KawPow. The mainnet algorithm will be chosen based on the test results.

Roadmap

What is switched on, and where

This section shows the block heights at which rules take effect on testnet and mainnet. The data comes from the node’s code. “Not activated” means no activation height has been set.

Relay economy

RelayActionsV2Mainnet: not activatedTestnet: 2

RelayFormulaMainnet: not activatedTestnet: 2

RelayLivenessMainnet: not activatedTestnet: 2

RelayRegistryMainnet: not activatedTestnet: 2

RelayRewardMainnet: not activatedTestnet: 2

Names and identity

IdentityMainnet: not activatedTestnet: 1

MoridStateCommitmentMainnet: not activatedTestnet: 10080

MoridTransferMainnet: not activatedTestnet: 1

MoridUaDeclarationMainnet: not activatedTestnet: 1

MrstMainnet: not activatedTestnet: 10080

MrstV2Mainnet: not activatedTestnet: 10080

Private transfers

PrivateMainnet: not activatedTestnet: 1

SaplingMainnet: not activatedTestnet: 1

SaplingNoteRootMainnet: not activatedTestnet: 1

SaplingSighashMainnet: not activatedTestnet: 1

ShieldedMainnet: not activatedTestnet: 1

ShieldedTurnstileMainnet: not activatedTestnet: 1

Development share

MdevMainnet: not activatedTestnet: 1

A rule takes effect at its assigned block height. If no height has been set, the rule remains inactive.