WiSPDocs Open the app

Trust and reference

Security

What WiSP never holds, who can stop you and how, what has been checked, and what has not. The full receipts are on the Security page.

On this page

The Security page has every claim below with a way to check it. This is the short version.

What WiSP never has

  • Your recovery phrase. It is made in your browser and stays there, encrypted under your password.
  • Your position keys. Each is derived on your device from the phrase. None is uploaded or copied.
  • Your wallet map. Which deposit funded which wallet, and which wallets are yours, is written only in your encrypted account.
  • A program over your funds. WiSP deploys nothing on chain. The programs in a WiSP transaction are the pool's, pump.fun's, Jupiter's and Solana's own.
  • A server in your trade. Trades are built and checked in your browser and sent through your RPC, or through Helius Sender on Fast and Faster.

Who can stop you

PowerOver your positionsOver SOL in the poolHeld by WiSP
Pause depositsNobodyThe pool's teamNo
Refuse or delay a withdrawalNobodyThe pool's relayer. Its proof fixes the recipient and amount, so it cannot redirect themNo
Freeze a positionNobody, except a token's own issuer for that tokenNot applicableNo
Change the rulesNobodyThe pool's multisig can upgrade its programNo

What WiSP does control is the app you load: the page and its code come from WiSP's host. The client's source is not published yet, so for now you trust that the code is what it says, as with any website.

The services the app talks to

The pool, your RPC, Jupiter, NEAR Intents (only for cross-chain moves) and WiSP's own app host. Each sees your IP. The access notice lists what each one sees before any of them is asked anything about your account. See How it works.

What has been checked

  • A test suite runs before every release; a release ships only when all of it passes.
  • Adversarial review rounds, in which a reviewer that has not seen the fixes tries to lose funds, link wallets or make the app lie. Every finding is closed with a test.
  • A self-audit of the client, finished on 23 October 2026.
  • Mainnet runs with real SOL.
  • The pool has its own audits and formal verification, published in its repository.

What has not

  • No third-party audit of the WiSP client has been published. An external review by ContractWolf is in progress.
  • The client's source is not published, so you cannot yet rebuild the app and compare it with what you load.

Size your positions with that in mind.

The treasury

Platform fees go to a Squads multisig that needs two of three signatures to move funds, except the 30% that goes to the buyback wallet: its key is held by the buyback service, which can only spend what the trades sent it, on buying $WiSP that it burns. A payout worker can send at most 1 SOL a day from the invite payout vault, a limit enforced on chain. All three keys are held by the WiSP team. The addresses are on the Security page.

Report a problem

If you find a way to lose a user's funds, link a user's wallets or make the app lie, write to security@usewisp.trade before you publish it.

Last checked against the app: 24 October 2026, build bf09a3f