Use your native wallet safely

Before you start

• Sign in to your own account for private wallet actions.
• Use the current capability messages in Wallet; an address alone is not deposit permission.

Native, legacy and connected wallets

The native wallet is server-managed: the platform can sign authorized transactions. A connected external wallet is a separate wallet, not a replacement for native custody. App sign-in identifies your account; it is not the private key for either wallet.

If you have an original Turnkey wallet, Wallet offers a provider selector. Turnkey is recovery-only. Switching views does not transfer funds or change the wallet bound to an existing launch or strategy. Keep balances small enough for your risk tolerance.

Check setup before sending funds

Native setup is attempted automatically when the verified account and provisioning capability allow it. Setup, deposit, withdrawal and export are distinct capabilities; one successful action does not prove all others are available.

A setup error is not a new wallet request. Retry the existing setup control and read its result. If setup or deposit readiness remains unavailable, stop before transferring.

1. Open /account/wallet and select Native if a provider selector is shown.
2. Wait for setup and the wallet status to finish loading. If offered after an error, use Retry wallet setup.
3. Check that the native wallet is provisioned and deposits are enabled before copying a destination.

Read balances without guessing

Balances shows assets held by the selected wallet. SOL is displayed in decimal SOL, not raw lamports. A USD estimate is a valuation, not an additional balance or an amount you can necessarily withdraw.

Loading, unavailable and refresh-needed values are not zero. Refresh the read when offered and check its source and freshness before choosing an amount. My coins lists creator/adopter records, not wallet holdings.

Deposit on Solana only

Use the selected native wallet’s Deposit panel, not an address copied from a connected wallet or an old screenshot. Deposits can be disabled even when an address is visible. Card and Apple Pay funding are coming soon, not an alternative live checkout.

Keep SOL available separately for network fees and token-account rent. COMPUTER can have a token transfer fee, so the received balance can be lower than the sent amount. A launch hold check uses the actual eligible holdings in its selected native wallet.

1. Open /account/wallet#deposit and verify Native, the Solana network and enabled deposit status.
2. Copy the full address or use its QR code; compare the destination in your sending wallet and confirm the exact token mint.
3. Send a small test transfer first. Wait for confirmed receipt and refresh Balances before sending more.

Withdraw an exact amount

The native Withdraw panel supports SOL, USDC and COMPUTER when enabled. It is an inline form: clicking Withdraw authorizes the exact destination, asset and amount with fees no higher than reviewed. No external wallet connection is needed for native signing.

The estimate includes network fee and rent; COMPUTER also shows its token transfer fee and recipient amount. If fees increase, the form stops and shows updated fees for a new deliberate review. Pending and uncertain withdrawals block another send.

1. Open /account/wallet#withdraw, verify Native, and enter a valid Solana destination you control or have independently verified.
2. Select the asset and a positive decimal amount. Wait for the estimate; inspect recipient amount and total cost, leaving SOL for fees.
3. Click Withdraw once only after checking the destination. Keep the recorded request and transaction signature.
4. If the outcome is uncertain, use Check status on that withdrawal. Pending is not failure. Only start another withdrawal after the recorded outcome makes it safe.

Export only in a private environment

Export is optional. It exposes a 64-byte Base58 Solana private key, not a seed phrase. Anyone with it can take the funds. Exporting or importing the key does not remove the platform’s signing access.

The key starts masked and offers Reveal, Hide, Copy and Clear. The screen clears its key state when hidden or unmounted, but cannot remove copies, screenshots or clipboard history you created. An export error is not proof you have a backup.

1. Open /account/wallet#export on a private device, without screen sharing or recording, and read the acknowledgment.
2. If export is enabled, acknowledge the risk and select Export private key. Do not share the resulting grant or key.
3. Save the key privately in secure storage. If importing into Phantom, choose Add / Connect Wallet, Import Private Key and Solana—not recovery-phrase import.
4. Use Clear when finished and clear the clipboard if you copied the key. If copying fails, follow the displayed manual-copy guidance privately.

Linking does not move holdings

The Connected wallet panel manages supported external wallets and X linking when configured. A connected address may need verification before use as a Spot source. Disabled configuration or a callback error must be resolved before relying on the link.

Connecting, disconnecting or changing app identity does not move assets to the native wallet or satisfy a native launch hold requirement. Review the actual source address for each action.

Related guides