Skip to main content
Blockchain Today

Crypto markets, protocols and policy

Can an RPC provider see your wallet address? What gets linked

Do RPC providers see your wallet address? Yes: requests expose queried addresses, signed senders and your IP, letting one operator connect wallet activity to a session.

By Blockchain Today Editorial4 min read

Can an RPC provider see your wallet address? What gets linked

Yes. An RPC provider can see the wallet address in ordinary balance and nonce requests, and can recover the sender address from a signed transaction. It also receives your IP address and request time, so it can link those addresses and actions to a network session.

What an RPC request reveals

An RPC endpoint receives the JSON-RPC method and its parameters, then returns the requested result or forwards the transaction. For eth_getBalance, the parameters include the address to check and a block reference. eth_getTransactionCount, commonly used to check a wallet’s nonce, also takes the address as a parameter. The provider can read both before it answers.

That makes an ordinary balance refresh different from a private lookup. When MetaMask asks an endpoint for a balance, the address is part of the request itself. The provider can record that address alongside the IP and time associated with the connection.

Sending a transaction exposes the sender too. With eth_sendRawTransaction, the wallet sends a signed transaction to the endpoint; its signature lets the sender be recovered before the transaction is mined. The provider can therefore associate the sender with the request’s IP and time, even before the transaction appears on-chain.

The endpoint does not need your wallet’s account name or a separate identity field to make that connection. It can observe which addresses arrive through a given session. How long those records are kept, and whether they are joined to other records, depends on the operator.

Endpoint choice changes who can observe this exchange. Chainlist helps users find EVM network endpoints and compare the network details behind them. The linked topic adds context on Chainlist and the endpoint information a wallet uses when connecting.

Consider an illustrative case: you open a wallet with four accounts selected. The wallet refreshes their balances and nonces, sending requests for each address, sometimes grouped into one batch. To the endpoint, that can look like four addresses arriving from the same IP within the same session. Even if those addresses never transact together, one operator can link them as a group of wallet activity.

This is the practical change from checking one address at a time: a wallet refresh can reveal a set of accounts in a single interaction. Batching reduces the number of network round trips, but it does not hide the addresses inside the batch from the endpoint handling it. Using one endpoint across accounts makes the association straightforward for that operator.

To limit what one provider can log, choose endpoints with clear privacy practices, use a VPN to separate the request from your home IP, or run your own node so requests go to infrastructure you control. Chainlist’s tracking labels can help compare endpoint options where labels are available. These choices shift what one operator can observe or retain; they do not remove the address from a balance request or make a signed transaction anonymous to its recipient and the network.

Related

Can an RPC provider see my IP address?

An RPC provider sees the IP address that connects to its endpoint, along with the requests made in that session. A VPN changes the IP presented to that endpoint to the VPN’s address, but the provider still sees the requested wallet addresses.

Does running my own node keep wallet activity private?

Running your own node keeps a third-party RPC operator from receiving your wallet’s requests. Your node still processes the addresses and transactions you submit, and this only addresses the RPC connection; it says nothing about other forms of network observation.

More questions

Does a VPN stop an RPC provider linking my addresses?

A VPN hides your usual public IP from the RPC provider, but it does not hide the addresses in JSON-RPC parameters or signed transactions. The provider can still group requests that arrive through the same VPN connection.

Do block explorers log my address when I search it?

A block explorer can receive the address you enter and the IP making the search. That creates a separate record from an RPC request, so using a different RPC endpoint does not change what the explorer can observe.

Can a wallet use different RPCs for different accounts?

A wallet can use different RPC endpoints for different accounts if its configuration supports that setup. This can split requests across operators, though each provider still sees the addresses sent to its own endpoint.