Documentation
Vaultro documentation explains how the wallet works for users, merchants, and technical reviewers. It covers self-custody, gasless execution, merchant payments, jackpot, investing, notifications, and the operational architecture behind the product.
Vaultro at a glance
Getting Started
Why do beginners use Vaultro?
Vaultro is built to feel simple for newcomers while keeping full self-custody intact. Users can access the same wallet across web, browser extension, Windows, macOS, Android, and iOS, with support for seven mainnet networks and twelve languages.
What can users do inside Vaultro?
Inside Vaultro, users can send and receive crypto, swap, bridge, invest, recover access, join the daily jackpot, and manage merchant flows without depending on multiple external apps or dashboards.
How do merchant payments work?
Vaultro Pay and Vaultro Store let merchants price in local currency, accept QR code, NFC, or payment-link checkout, and settle into stablecoins such as USDT or USDC while receiving real-time push notifications.
How does gasless work?
In supported flows, Vaultro removes the need to keep extra native gas tokens just to use the wallet. Instead of forcing users to hold ETH or POL for simple actions, the fee logic can use the asset already involved in the transaction.
Zero Gas (Gasless)
Hyper-Swap
Recovery Protocol
Yield & Earn
Architecture
How does the architecture stay simple for users?
Vaultro combines Argon2id local hardening, isolated signing, routed execution, relayer services, pricing, history, and notifications. Private keys and vault secrets remain local, while operational services only process the limited metadata required to quote, route, relay, index, or notify.
Why does Vaultro avoid random external dapps?
Vaultro reduces phishing exposure by keeping major actions such as swap, bridge, invest, jackpot, merchant checkout, and recovery inside the product instead of asking users to connect to random third-party sites.
How does recovery work?
The recovery system lets users designate trusted guardians or devices and restore the original private key on-chain with a delay and cancellation window, rather than relying on a centralized account reset.
SECURITY ARCHITECTURE
Reference Areas
- Wallet lifecycle: create, import, unlock, reset, hardware access, and local recovery.
- Execution flows: transfer, pay, swap, bridge, invest, jackpot, and merchant/store.
- Merchant commerce: fiat pricing, stablecoin settlement, and checkout by QR, NFC, and payment link.
- Jackpot rules: choose up to six numbers from thirty, daily draws, rollover behavior, and automatic prizes.
- Security model: local encryption, isolated signing, recovery, and operational safeguards.
- Operational surfaces: relayer, history, pricing, notifications, and the public status page.
- Platform coverage: web app, browser extension, Windows, macOS, Android, and iOS.
- Product reach: seven mainnet networks and twelve interface languages.
Help Center
Use the Help Center when you need product explanations, troubleshooting guidance, official contact channels, or links to the security and status pages.