Ask about your wallet without naming it.
Private RPC · Robinhood Chain · 1 of 16
An RPC for Robinhood Chain that hides every wallet read among 15 real wallets. The node answers all 16 and can't tell which one you meant.
The crowd
Fifteen real wallets stand around yours.
Every decoy has moved tokens on Robinhood Chain. Same shape of read, same answer time, random order. From the node's side of the wire, the grain and the chaff look the same.
The chaff
Your read hides in a crowd.
One balance read, scattered into sixteen. To the node every request looks the same, and it has to answer all of them.
1 of 16
Sixteen wallets answer. One is yours.
The node sees sixteen real wallets asking the same kind of read. Only your side knows which one is lit, and the other fifteen answers are dropped on arrival.
01 · The log
What the node writes down.
A plain RPC logs one line per read: this IP asked about this wallet. Put those lines together and you have someone's portfolio, their timing and their agent's next move.
Through CHAFF the node gets 16 reads of the same shape, one for each wallet in your crowd. Every decoy is a real wallet that has moved tokens on Robinhood Chain.
Order and request ids are random. The node answers all 16. Your side keeps one answer and drops the other 15.
Read again tomorrow and the crowd is the same 16 wallets, so stacking a month of logs narrows nothing.
Who learns what.
Server mode is one URL change. Client mode builds the crowd on your machine, so CHAFF itself can't tell either.
| Plain RPC | CHAFF URL (server mode) | CHAFF SDK (client mode) | |
|---|---|---|---|
| The node learns | Your wallet, every read | A crowd of 16, not which one | A crowd of 16, not which one |
| CHAFF learns | Nothing, not involved | Your wallet, because it builds the crowd. Never written to disk. | The same crowd of 16 and your IP. Not which one. |
| Setup | The default in your wallet or bot | Swap the RPC URL for /rpc/<your key> | Three small ES modules, no npm install |
| Upstream cost | 1 read | 16 reads in one batch, 1 answer back | 16 reads in one batch, 1 answer kept |
| Good for | Public data | Agents, scripts, quick wins | Wallet apps and dashboards you ship to users |
Running now.
Counted by the relay. Counts only: no addresses, no keys, no IPs are kept.
Is your wallet in the crowd?
Decoys come from wallets that moved USDG, WETH, stock tokens or Pons tokens. If yours is in that pool, it looks exactly like its decoys. This check runs in your browser against the pool the page already loaded. Nothing is sent.
One line to switch.
Make a key once and keep it. The key picks your crowd, so the same key means the same 16 wallets on every read.
// server mode: one URL, every wallet read goes out in a crowd import { createPublicClient, http } from "viem"; const client = createPublicClient({ transport: http("https://chaffrpc.xyz/rpc/<key>"), }); await client.getBalance({ address: me });
import { JsonRpcProvider } from "ethers";
const rpc = new JsonRpcProvider("https://chaffrpc.xyz/rpc/<key>", 4663);
const usdg = new Contract(USDG, ["function balanceOf(address) view returns (uint256)"], rpc);
await usdg.balanceOf(me);
curl -s https://chaffrpc.xyz/rpc/<key> \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0x…","latest"]}' # the node received 16 balance reads; you get one answer
// Claude Code claude mcp add --transport http chaff https://chaffrpc.xyz/mcp // tools: private_balances, private_read, pool_status // pass the same "key" on every call to keep one crowd
// client mode: the crowd is built here, the relay can't tell either import { createChaff } from "https://chaffrpc.xyz/src/client.js"; const chaff = createChaff({ endpoint: "https://chaffrpc.xyz", key: MY_KEY }); const rows = await chaff.balances(me); // ETH, USDG, WETH, 12 stocks // or as a viem transport: custom(chaff.eip1193)
What gets hidden.
CHAFF reads the method and the calldata. Anything that names a wallet goes out in a crowd. The rest is either public already or refused.
Hidden in a crowd
- eth_getBalance
- eth_getTransactionCount
- eth_getCode
- eth_call balanceOf(wallet)
- eth_call allowance(wallet, spender)
- eth_call nonces(wallet)
The from field is dropped from these calls, since it would name you anyway.
Passed through as is
- eth_blockNumber, eth_chainId
- eth_getBlockBy*
- eth_getTransactionByHash
- eth_getTransactionReceipt
- eth_gasPrice, eth_feeHistory
- other eth_call (prices, pools)
These carry no wallet of yours unless you put one in the calldata yourself.
Refused
- eth_sendRawTransaction
- eth_estimateGas
- eth_getLogs
- eth_sign, personal_*
- everything else
CHAFF is read-only and holds no keys. Send transactions through your wallet's own RPC.
What it does not hide.
Decoys raise the cost of watching you. They do not make you invisible. Here is exactly where the edges are.
Quiet wallets stand out
Decoys are wallets that moved tokens recently. A node that keeps its own index could notice that one of the 16 has not moved in months. Use the check above: if your wallet is in the pool, it blends in.
Your IP still reaches someone
The node sees the relay's IP, never yours. CHAFF sees your IP. If that matters, connect over Tor or a VPN; the crowd works the same.
Transactions are public
CHAFF hides reads. A swap or transfer you send is on chain for everyone, and a read just before it can be linked by timing.
Passed-through calls are plain
An eth_call CHAFF does not recognise goes out unchanged. If its calldata contains your address, the node sees it.
Server mode trusts us
In server mode the relay builds the crowd, so it knows which wallet you asked about. It keeps nothing, but if you'd rather not trust that, use client mode.
Live beta, not audited
The code is small and the tests are in the repo. It has not been reviewed by a third party yet.
The token.
CHAFF is free to use and needs no token. The token pays for the relay and the node traffic a crowd costs.
Launched on Pons, on Robinhood Chain, with a 3% creator tax. The team buys 0.02 ETH in the launch transaction and holds; any sale is announced first.
When the token is doing well, part of the creator tax buys it back on the curve, spread over days and capped at 30% of the tax received. Every buyback is posted with its tx.
No promised utility or returns. Reads through CHAFF are free whether you hold it or not.
Only trust the contract address shown here and on our X account. Copies of new tickers appear within the hour.
Questions.
Short answers. The docs have the long ones.
- Are the numbers real?
- Yes. Balances, prices, the pool and the counters all come from Robinhood Chain (chain id 4663) through the same relay you would use.
- Why not run my own node?
- If you can, do. Most wallets, bots and agents use a shared RPC, and that RPC sees every wallet they look at.
- Does a crowd cost the node 16 times more?
- Sixteen balance reads in one batch are cheap for a node. The relay caps each IP at 120 wallet reads a minute and queues the rest.
- Is it fair to the decoy wallets?
- Reading a balance is public and changes nothing. A decoy is one of 16, and it appears in other people's crowds too.
- What is the key?
- 32 random bytes you make once. It decides your crowd through an HMAC, so without it nobody can work out which crowd belongs to which wallet.
- Does it log what I ask?
- It counts reads and batches. Addresses, keys and request bodies are never written. Your IP is held for one minute for the rate limit.
