Availability and development
Updated September 29, 2026.
VOUT is live on Bitcoin Mainnet: the wallet, RGB v0.12 transfers and VOUT Lightning. VOUT develops the wallet, its services, and its RGB Lightning implementation together. They have different release boundaries. A capability in the current implementation may reach a service or an app release at a different time. Use the options offered by your installed app on the selected network; do not transfer funds to test a feature that the app does not expose.
Get the app
| Channel | Status |
|---|---|
| iPhone | App Store listing |
| Android APK | Download VOUT for Android : version 1.1.1 (build 63), with its SHA-256 checksum . |
| Google Play | Coming soon. |
| Public TestFlight | No public invitation is published in these docs. |
The Android package is version 1.1.1 (build 63). The same version is awaiting App Store review on the date above. These guides describe the current app flows; some options may be absent from the version currently available in the store. Check your installed version when following a guide.
Wallet and service capabilities
The on-chain implementation supports Bitcoin and compatible fungible RGB v0.12 assets. It includes issuance, receive requests, reviewed sends, proof validation, transaction observation, and encrypted full-state backups. Compatibility depends on the exact wallet and request format, as described in Wallet compatibility.
VOUT Lightning runs on Bitcoin Mainnet. Deposits of RGB assets, transfers between VOUT users, payments of outside BTC Lightning invoices, and withdrawals of BTC and RGB to on-chain wallets have all completed there. VOUT Lightning is custodial. Its account ledger supports BTC and RGB balances, transfers inside the service, and on-chain deposits and withdrawals. External BTC Lightning payments use the node. Asset availability and the confirmation requirements for deposits are service settings; a contract being valid RGB does not by itself enable every payment path.
The app also contains asset discovery, issuance, social, and market interfaces. Those interfaces do not establish the liquidity of a market, a token’s value, or the completion of a broader exchange or yield product. No return, trading volume, or public launch date is promised here.
Native RGB Lightning
On Mainnet, RGB assets already enter VOUT Lightning through VOUT’s RGB custody wallet and move between accounts in its ledger, while the node’s channels carry BTC. Native RGB channels, whose commitments carry the asset itself, are the next step.
The native channel implementation binds RGB allocations to Lightning funding and commitment transactions. Two VOUT nodes have completed a round trip on a public test network: open a channel, pay in both directions, close cooperatively, and reconcile the resulting asset supply. Force close, HTLC recovery, revoked-state handling and anchor fee bumping have been exercised in local test environments.
Native RGB multi-hop routing and general third-party channel interoperability are not established. An anchor-channel counterparty can also omit a required RGB anchor from certain second-stage transactions, which can destroy the affected allocation. This remains a material limitation of the relevant channel path. RGB in payment channels and Settlement and failure recovery describe the mechanism and the scope of existing results.
Networks
VOUT runs on Bitcoin Mainnet by default. Some builds also offer Testnet4, a test network with valueless coins, for trying a flow or testing an integration. VOUT keeps the two networks’ keys, stored state, requests, and service balances apart, and a test asset is never redeemable for a Mainnet asset.
For an integration, agree on the network, wallet versions, contract, and payment path before testing. Report the result with those details so the next person can reproduce it. Build with RGB and VOUT lists the information an integration needs.