Protocol

Known Limitations

How the closed testnet works today:

Private layer and apps

  • The private layer is going through the stress test — see the roadmap. Safeguards against flaws in the proof scheme include a pool balance check and an emergency switch. The balance check (the “turnstile”) prevents withdrawals from exceeding deposits. The emergency switch lets a new node version stop private transfers without affecting public ones. See Private Transfers.
  • The wallet and messenger run on Linux, Windows, macOS, Android and iPhone.

Gateway

  • The gateway provides blockchain data to the app. It does not receive the wallet’s private keys and cannot decrypt the user’s private payments. The wallet checks block headers and cryptographic proofs and rejects data that fails those checks. A gateway can withhold a response or show an outdated chain. To independently check the chain’s freshness and cumulative work, compare it with another gateway or your own node.
  • The gateway supports paginated lists of an address’s unspent outputs. Without a request for pagination, it returns the full list; for a large wallet, that response may exceed the size limit.

Network

  • Participation is by invitation while the network's stability is being checked; relays run on servers operated by the project.
  • There is no faucet: testnet coins are obtained by mining.
  • The explorer may be briefly unavailable.
  • Testnet balances, names and transactions do not become part of mainnet. This applies to blockchain data and does not mean that locally stored conversations are deleted.

Messenger

  • Traffic padding, which fills traffic with empty data to hide its real volume, is planned for the open testnet.
  • Version 0.3.0 has no new-message notifications. Two delivery options are planned for the open testnet, with users choosing which to use. Notifications will be off by default.
  • Sealed sender and post-quantum protection are planned after mainnet launch.
  • What stays visible on the network: with a direct connection, your provider sees connections to a relay or gateway (that is what Tor and bridges are for), and a relay sees the mailbox number and the envelope size rounded to a "bucket".
  • Shadow is a second profile for messaging only, with no wallet or MORID name. Shadow is designed to connect only through bridges or Tor. This protection is not yet fully implemented on the closed testnet: a relay operator may see the device’s IP address.
  • All relays on the closed testnet are operated by the project. Some metadata is still visible to their operators. Further protection of this data is planned for the open testnet. Metadata is information about connections and message exchanges. A relay operator can currently see the device’s IP address on some Shadow connections; read unencrypted group-chat and channel fields; distinguish cover envelopes from envelopes carrying real messages; and extract a chat identifier and time from the envelope identifier. This does not give the operator the keys to decrypt conversation contents.