Availability and versions
Your installed version, permissions and exact networks determine available CRM actions.
This guide describes the selected API 0.50 release and matching CRM. Publishing source and passing a build do not prove that an operator has installed that version. Reviewed Git revisions are recorded in the editorial source inventory.
Everyday screens and advanced tools
Sources, wallets, addresses, invoices, payouts, customers and tags have dedicated working screens. Advanced tools expose permitted actions only; they grant no extra rights. Address details show a QR, actions and observed balances, with separate unknown and incomplete states.
Customer fields, tag-related records and tag search are described in their articles against the actual CRM. A backend endpoint alone does not create a field or button.
Networks and test funds
Organizations and Sources have no single Mainnet/Testnet mode. Each exact network is enabled independently within the operator’s global ceiling. A globally disabled network is not offered for new activation. Disabling it does not delete earlier history or authorize spending.
Bitcoin is disabled by default for this stage; balance work is deferred. Use only enabled exact ETH/TRON/BSC networks and registered contracts. Matching symbols do not make tokens on different networks the same asset.
Faucet serves our test USDT/USDC only: up to 10,000 nominal test units per organization and network every 12 hours. This does not assert a real dollar value. Separate staff Admin can request without these limits. Admission is not delivery: an available worker, reserves and a confirmed result for the original request are still needed.
Archive and financial meaning
Archiving a wallet or address retains its record and history, with restoration through the permitted action. A catalog archive marker and a binding that blocks new operations are separate states; review the dialog explanation. Archive does not revoke an external key or cancel signed work.
A Wallet Node Invoice provides receiving instructions. An observed transfer is not a paid Invoice or an accounting credit. The unfinished Node Invoice financial linkage is excluded from this release.
Security and external components
Registering a key and confirming the current session are separate actions. On the authentication page choose Browser choice — all keys, This device — Touch ID / Windows Hello, or USB security key (FIDO2). Touch ID needs an enrolled device credential and browser support. PIN or biometric prompts depend on current user-verification requirements and the authenticator.
A WalletConnect connection or signed message proves control of an exact address, not login, payment or spending authority. Inspect the original request after an unknown result.
Physical USB/NFC/Touch ID, mobile WalletConnect, live providers and financial scenarios need separate acceptance. Native Sign Storage, the independent Widget backend and all invitation/recovery scenarios are not claimed complete.