Two denominations — public and private
The two-denomination model is planned and unavailable. The active public documentation does not certify a private-value account type, stealth transfer, confidential amount, conversion contract, disclosure key, wallet mode, SDK call, or exchange-custody procedure. Do not construct or submit transactions from historical precompile addresses, selectors, whitepaper text, or package symbols.
Intended model
Section titled “Intended model”The historical design proposed a public denomination and a separate private denomination on one chain and fee unit. Only the public LYTH display unit is current. Any future private denomination would require an explicit, independently reviewed privacy design and a clearly disclosed conversion boundary.
That boundary is not a bridge to another chain. Monolythium has no in-tree cross-chain bridge or Foundation-operated production route. No public-to-private conversion path is released either.
Current privacy boundary
Section titled “Current privacy boundary”- The public testnet mempool is plaintext.
- No encrypted, sealed, private-send, or threshold-decrypted mempool lane exists.
- No amount-hiding or recipient-hiding value path is certified by these docs.
- No confidential-transfer activation date or post-quantum range-proof release is announced.
- No wallet or exchange should expose private-denomination controls from this design page.
An implementation artifact, revert code, reserved selector, or historical snapshot is not activation evidence. A future release would need consistent runtime, genesis, SDK, wallet, explorer, indexer, audit, disclosure, recovery, and compliance evidence before this page becomes actionable.