Your RPC knows who you are

Every time your wallet opens, it tells an RPC server your IP, your device and every address you hold. Ghost RPC passes the request on and leaves you out of it.

Run the leak test
0Requests relayed
0Wallets connected now
0Heavy scans refused
0Requests logged

Leak test

This is what an RPC learns from you, right now.

Read from the request your browser just made. Nothing here is stored.

Your RPC today

Sees you

IP address
reading…
Device
reading…
Language
reading…
Location
reading…
Headers
reading…
Your addresses
every one your wallet holds

We send the same requests your wallet sends, through Ghost RPC, with nothing logged. Any other RPC gets them with your IP attached.


        
      

How it works

One URL. Your wallet stays the same.

  1. 01

    Your wallet asks

    Balances, tokens, the latest blockhash, a transaction it signed. The normal requests every wallet makes.

  2. 02

    Ghost RPC strips you out

    Only the request itself goes on: method, parameters, an id. Your IP, device, language, cookies and origin stay behind, and nothing is written down.

  3. 03

    Solana answers

    The answer comes back to your wallet unchanged. The RPC provider saw one more request from Ghost RPC, mixed with everyone else's.

What reaches who
RPC providerGhost RPC
Your IPNeverUsed to answer you, never stored
Device and headersNeverDropped on arrival
Addresses you checkMixed with every userNot logged
Your keysNeverNever

Set up

Paste it once. Done.

https://ghostrpc

Solflare

  1. Settings
  2. Network
  3. Add custom node
  4. Paste the URL and save

Backpack

  1. Settings
  2. Preferences, then Solana
  3. RPC Connection, then Custom
  4. Paste the URL

Any other wallet or app

  1. Find the RPC or custom node field
  2. Paste the URL
  3. WebSocket uses the same address with wss://

FAQ

Straight answers.

Can Ghost RPC touch my funds?

No. An RPC reads the chain and relays transactions your wallet already signed. Your keys never leave your wallet, and changing a single byte of a signed transaction breaks its signature.

What does Ghost RPC keep?

Only totals: requests relayed, scans refused, sockets open. To stop abuse it counts requests per caller with a hash of the IP under a random key that is replaced every hour, held in memory and never written.

Why are some requests refused?

Heavy scans like getProgramAccounts read huge parts of the chain. Wallets don't need them, and refusing them keeps the shared service fast for everyone.

Does it work with WebSockets?

Yes. Account, signature, slot and log subscriptions go through the same way, so confirmations arrive in real time.