Solana Wallet Safety

Using a Solana application safely starts with understanding what your wallet is being asked to approve.

Connecting a wallet, signing a message, and signing a transaction are different actions. A wallet connection can expose a public address to an application, while a transaction signature can authorize on-chain instructions.

This section explains how to review wallet requests, protect recovery credentials, recognize suspicious applications, and use non-custodial tools more safely.

How wallet connections work#

Connecting a wallet allows an application to identify the public wallet address and request supported wallet interactions.

A connection normally does not authorize every future transaction. The wallet should still ask you to approve transactions and other signing requests separately.

However, a wallet connection does not prove that an application is trustworthy. Verify the website and understand what you are using before connecting.

Connection, message, and transaction signatures#

Users should distinguish between common wallet requests:

• Wallet connection: Shares the public address and may allow the application to read public blockchain data.
• Message signature: Signs a message that may prove control of an address or authorize an off-chain action.
• Transaction signature: Approves on-chain instructions that can move assets or modify accounts.

A transaction signature can authorize actions such as transfers, swaps, account creation, account closure, token approvals, or authority changes.

Before approving a request, inspect the details your wallet displays.

Reviewing Solana transactions#

Important details can include:

• the application requesting the signature;
• the connected wallet;
• the programs involved;
• SOL and token movements;
• source and destination accounts;
• account creation or closure;
• token approvals or authority changes;
• transaction fees; and
• any instructions unrelated to the feature you intended to use.

If the wallet display is unclear or the transaction contains unexpected instructions, do not sign it.

Protecting seed phrases and private keys#

A normal wallet-connected application does not need your seed phrase or private key to request a transaction signature.

Recognizing suspicious applications#

Use extra caution when an application:

• asks for recovery credentials;
• uses a lookalike or misspelled domain;
• promises unrealistic rewards or guaranteed returns;
• hides transaction details;
• pressures you to sign immediately;
• asks you to disable wallet security features;
• requests an unrelated token approval or authority change; or
• claims that signing is required merely to view public information.

Do not rely solely on branding or search-engine placement. Verify the domain through a trusted source.

Using non-custodial applications#

A non-custodial application allows users to retain control of their signing credentials rather than giving the application direct custody of the private key.

That does not make every transaction safe. Users can still authorize a malicious transfer or an unintended account change.

Non-custodial safety therefore depends on both credential protection and transaction review.

What to do if a request looks unsafe#

If something looks unexpected:

1. Reject the wallet request.
2. Disconnect the application if appropriate.
3. Do not enter recovery credentials.
4. Verify the application domain through an independent trusted source.
5. Review recent wallet activity if you already signed a suspicious transaction.
6. Seek qualified help before approving another transaction.

Learn more about Solana wallet safety#

The guides in this section explain wallet connections, signatures, transaction review, phishing prevention, domain verification, non-custodial applications, and safer wallet-cleanup practices.

For information about how Your Free SOL approaches wallet security, transaction authorization, and non-custodial interactions, see Your Free SOL Security.