RISK DISCLOSURE

Solana swap and utility tool risks

Wallet-approved swaps carry token, market, program, transaction, network, and user-error risk. Depositing into a separate tool also adds risks associated with service-managed funds and keys.

Last updated

Main risks to understand

Volatility

Digital-asset prices can change sharply before, during, or after a transaction.

Liquidity and slippage

Thin liquidity can produce high price impact, poor execution, or no usable route.

Token fraud

Names, tickers, logos, websites, and social accounts can be copied or impersonated.

Transaction failure

Transactions may fail because of stale quotes, slippage, fees, program errors, congestion, or network conditions.

Irreversible actions

Token sends, burns, claims, authority changes, and completed swaps may not be reversible.

Third-party dependence

Data, routing, wallets, RPC services, block explorers, and connected applications may be delayed, unavailable, or incorrect.

Deposits and automation

The Trading Bot and Token Claim hold deposits in service-managed wallets or vaults. Service failures or compromised keys can put deposited funds at risk or delay withdrawals. Authorized bot trades can execute while you are offline and can lose money.

No guarantees or financial advice

SOLANADEX.IO does not guarantee token legitimacy, value, liquidity, availability, price, routing, execution, settlement time, security, or profit. Market data and quotes can change or be delayed. You are responsible for reviewing each token, address, amount, fee, route, authority, and wallet instruction before approval.

Nothing on SOLANADEX.IO is financial, investment, legal, tax, or accounting advice. Consider obtaining independent professional advice appropriate to your situation.

Reduce avoidable risk

  • Use the exact SolanaDEX.io hostname and avoid look-alike domains.
  • Verify complete token mint and recipient addresses.
  • Check price impact, slippage, minimum received, and fees.
  • Reject unexpected wallet instructions or authority changes.
  • Never share a recovery phrase or private key.
  • Use a small test transaction where practical.