Accounts and trading wallets ​

Account and Wallet Manager introduce a persistent profile with multiple trading wallets. Account sign-in must be configured for the deployed instance before these services become available.

Sign in and link accounts ​

Supported login methods are Google, email and supported external wallets. Link another method from Account settings while signed in. The provider verifies the linked identity; Sanvio does not merge accounts from an email address or public wallet address alone.

Your profile, wallet labels and signed-in market watchlist remain attached to the same verified provider identity when you return. Guest watchlists remain local to their browser.

Wallet actions stay tied to the account that requested them. Switching accounts, signing out or archiving a wallet while an action is waiting prevents a new signing request from continuing with the old wallet. Reopen its history after signing in to inspect a handoff that may already have reached the wallet.

Wallet Manager ​

Select Solana, Ethereum, Robinhood Chain or NEAR to view your linked wallets. Ethereum and Robinhood use the same EVM keys and addresses, with separate network balances and transaction nonces. Labels, archive state and the primary EVM wallet are shared between those two network views.

Use the action menu at the end of a wallet row to rename, choose a primary wallet, archive, restore or open secure key export. The summary shows the selected wallets' native balance, or all visible wallets when none are selected. A total appears only when every included balance has been verified. It is not a USD portfolio valuation.

The Wallet activity and Transfers tabs keep wallet management records and native transfers accessible. Orders & transactions opens the account transaction history.

Cross-chain conversions and prefunded opposing cycles can select owned source and destination wallets from this account. Their history is private to the profile. Each network leg has its own approval and verified receipts; one completed leg does not authorize another. See Arbitrage.

• Create additional wallets with the provider's user-owned wallet flow.
• Rename a wallet or choose a primary wallet for its network.
• Archive and restore a wallet without deleting its history.
• Select a wallet to copy its deposit address.
• Refresh native balances through the network RPC. An unavailable or inconsistent response stays unknown.

The current limit is ten wallets per wallet type, including archived wallets: Solana, EVM and NEAR. Ethereum does not create a duplicate set of EVM keys. Import is connected for Solana and EVM keys. NEAR import requires the provider's migration flow and is not connected to the current import form.

Key export and security ​

Private keys and seed phrases are not stored in Sanvio's account database. Export opens the provider's protected window, on a separate origin, where the wallet owner can view their key.

Enroll a passkey or authenticator through Account settings before exporting. Available app options do not mean your account has enrolled a factor; the interface checks your own enrollment. The export flow requests provider MFA verification. Imported keys are handed to the provider's encrypted import flow from the browser and are not sent to Sanvio's account API.

Account authentication is separate from trading authorization. Signing in does not activate a server signer or grant unlimited transaction access. Automated trading requires a supported adapter and a separately validated, limited authorization.

Account transaction history ​

The account Solana API binds new order preparation and submission to a wallet verified as owned by the signed-in user. Orders remain attached to that account and wallet across browser sessions. The earlier external-wallet workflow retains its browser-session history.

Archive and integration pauses preserve transaction reconciliation. A prepared order is not a completed trade. Check an uncertain signature before creating another order.

Native transfers ​

Select one wallet for withdrawal or distribution, or several wallets for consolidation. Preparation checks network, sender, recipient, amount and fees. Each review requires owner signing and security verification. Transfers in a group have independent outcomes.

The current native per-transfer limits are 0.01 SOL, 0.01 Ethereum ETH, 0.01 Robinhood ETH and 1 NEAR. Consolidation sends an entered amount from each selected wallet to another wallet on the same network. Token transfers and cross-chain conversions use different adapters.

If an EVM wallet response is interrupted, its recorded handoff remains pending. Attach the transaction hash from your wallet history and verify the receipt. Do not send again merely because the response was lost. History and status checks remain available when an integration is paused or a wallet is archived.

The NEAR transfer adapter supports owner-controlled implicit ed25519 wallets. Named recipient accounts must already exist. Preparation checks the full-access key and nonce; it does not claim to simulate NEAR execution.

Availability ​

Live Google sign-in and wallet provisioning require a configured Privy application. The current instance's status is available on the Account page. Native transfers and trading adapters are enabled separately. Online automatic execution uses an owner wallet and an explicit, bounded permission. Solana and Ethereum RWA permissions are scoped to their verified issuer controls. Exact reserved transactions provide a separate supported execution path after closing the app. See Availability.

Provider references: user wallet creation, key export, server-side signers.

Use Holdings & P&L to inspect checked balances and finalized app trading results for your selected network and wallets. See Portfolio and P&L for cost-basis coverage and fees.

Recover an unresolved EVM handoff ​

Use Recover an unresolved EVM transaction in trade, transfer, liquidity or owned deposit history. Check wallet nonce looks for a finalized transaction at the original nonce. If the original operation executed, its actual outcome is recovered. If a different finalized transaction consumed the nonce, the original can no longer execute. Unavailable archive data keeps the operation unresolved.

Prepare nonce cancellation creates a zero-value self-transfer at that same nonce with a higher bounded gas price. Review and approve it in the wallet. It competes with the original; cancellation is effective only after final nonce consumption is checked. A mined cancellation pays gas, including a reverted one. Executable smart/delegated accounts require a separate recovery adapter.

If the cancellation response is interrupted, attach its wallet hash or check the nonce. This flow does not repeat the original trade or transfer. Its private history stays readable while new recovery transactions are paused.

Ethereum Quick Trade and automatic orders ​

Open Ethereum Quick Trade permission in the trade panel to choose buy and sell caps and a duration. The grant belongs to this account, wallet, login and asset. Maximum native input is 0.01 ETH or 100 USDC; the transaction gas budget is capped at 0.003 ETH. RWA grants require a current V2 wrapper and review of issuer controls. RWA sell quantities use wrapped-share units.

Enable Trade within my active Ethereum permission to prepare, simulate and hand the reviewed swap to your embedded wallet in one action. Exact token approvals, liquidity and transfers retain their separate owner review. A missing allowance requires an approved token transaction before Quick Trade can swap.

For limit and TP/SL targets, select Execute with my active Ethereum permission while this app is open when creating the order. Atomic profit targets require their own Ethereum automatic cycle permission, with a maximum cycle input and minimum permitted profit. Spot permission does not cover cycles.

The browser checks fresh quotes and the server records the wallet handoff before signing. Closing the app or signing out stops automatic signing. Revoke permission to stop new automatic handoffs; already submitted transactions can still finish. Changing a grant invalidates reviews and automatic orders created under its earlier ID. Those orders remain readable and can be cancelled or reviewed manually.

An interrupted wallet response stays in Activity for hash or nonce recovery. It is never automatically resent. A triggered price or profit target still needs a liquid verified route and successful current simulation; a monitor notification alone does not establish an executable trade.

Reserved Solana orders after closing the app ​

Native SOL/USDC and supported official Solana xStock Limit, TP/SL and Profit panels include Execute this Solana order after closing the app. Create and confirm an owned durable nonce account, then review the exact input, encoded return floor and fee allowance. Your wallet signs each branch. The server encrypts those signatures and can submit the selected transaction once when a fresh quote and exact balance simulation meet the target. It cannot change the signed route or create another transaction.

Funds remain in your wallet until execution. The nonce account holds recoverable rent, displayed separately from its network fee. Both TP/SL branches share one nonce, so only one can be processed. Keep the wallet funded; an existing wrapped SOL account or changed USDC controls can prevent execution. A pinned route can become unavailable even when the target price is reached.

Stop scheduling and schedule expiry remove the stored signed bytes. They do not revoke a signature cryptographically. Use Invalidate old signatures to sign an exact advancement of the same nonce. That transaction competes with the trade; its successful finalized receipt proves the original cannot execute. A missing signature or changed nonce alone does not prove which transaction executed. An unknown handoff remains recorded and is never automatically sent a second time.

After reconciliation, Return nonce rent closes the nonce account and returns its rent to the same owner wallet. Status checks and private history remain accessible during an integration pause or wallet archive. A finalized outside broadcast can still be discovered after scheduling has stopped.

RWA targets use raw mint precision and require explicit issuer-control consent. The current official mint, transfer-hook code, issuer controls and public owner balances are checked again before execution. A changed issuer profile prevents another send. Corporate-action display multipliers do not silently change the signed raw amounts.

Future Profit orders pin two specific swaps. Their final return includes principal, requested profit and a native-cost allowance. Native cycles require a simulated actual wallet SOL increase and preserve earlier intermediate-token inventory. RWA cycles settle in USDC and additionally revalue native SOL costs with a 50% buffer; an insufficient signed floor prevents sending. A nominal route can be checked before it is profitable, but the transaction you sign contains the stronger future profit floor.

These reserved cycles use one RPC broadcast. A failed transaction can consume network fees and advance its nonce. Jito-based ordinary cycles keep their separate submission flow. A pinned future route can become obsolete; reaching a reference price alone does not authorize a new route or another signature.