Send LYTH
This page is a product placeholder, not a transfer guide. Mainnet is not running, the development testnet is value-less and resettable, and these docs do not certify a production wallet transaction flow. Do not use real funds, production credentials, a primary wallet, or a copied historical request shape.
Future safety requirements
Section titled “Future safety requirements”A released wallet transfer flow must show the full typed bech32m destination, exact network and genesis, amount and atomic-unit conversion, fees, nonce, reviewed transaction bytes, and an unambiguous final approval. A human-readable name may be advisory only; name registration and resolution are not currently certified.
No private-denomination, stealth-recipient, confidential-amount, or public/private conversion path is released. The public testnet mempool is plaintext, so future transaction contents may be observable before inclusion.
Current supported scope
Section titled “Current supported scope”The SDK documentation verifies local address parsing, local deterministic signing primitives, safe read-only RPC calls, and wallet-auth proofs. It intentionally does not publish a copy-paste transfer-preparation or submission flow. Wallet authentication does not move value or grant future signing authority.