Sees you
- IP address
- reading…
- Device
- reading…
- Language
- reading…
- Location
- reading…
- Headers
- reading…
- Your addresses
- every one your wallet holds
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 testLeak test
Read from the request your browser just made. Nothing here is stored.
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
Balances, tokens, the latest blockhash, a transaction it signed. The normal requests every wallet makes.
Only the request itself goes on: method, parameters, an id. Your IP, device, language, cookies and origin stay behind, and nothing is written down.
The answer comes back to your wallet unchanged. The RPC provider saw one more request from Ghost RPC, mixed with everyone else's.
| RPC provider | Ghost RPC | |
|---|---|---|
| Your IP | Never | Used to answer you, never stored |
| Device and headers | Never | Dropped on arrival |
| Addresses you check | Mixed with every user | Not logged |
| Your keys | Never | Never |
Set up
https://ghostrpc
wss://FAQ
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.
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.
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.
Yes. Account, signature, slot and log subscriptions go through the same way, so confirmations arrive in real time.