Encyclopedia Ethereum · Entry 234
What can an Ethereum RPC provider learn about a wallet?
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Balance query | eth_getBalance includes the address being queried. | [1] |
| Transaction lookup | RPC methods can request a particular transaction or receipt. | [1] |
| Public activity | Ethereum’s public ledger can reveal transaction relationships. | [3] |
Read the information sent to the endpoint
A provider cannot answer an address-specific balance query without receiving its address parameter. A wallet querying several accounts through one service can disclose that those addresses are being examined through that service. This is a privacy implication of the requests, not a claim about any provider’s retention policy.
Read the provider’s own policy to determine what it says it logs. RPC support and privacy promises are separate properties.
An apparently passive check still asks about an address
Suppose you never send a transaction but repeatedly request the balance of two savings accounts from a hosted endpoint. The endpoint receives the two account parameters even though the queries themselves do not change blockchain state.
A block explorer similarly needs enough information to show the account you search. Read-only use means no state change, not automatically no information disclosure.
A personal node changes the intermediary
Ethereum’s node documentation identifies privacy as a reason to query your own node: you need not send address and balance requests to an external RPC service. Operating the node creates its own maintenance and connectivity responsibilities.
Transactions you publish still become part of the public ledger. Self-hosting the query layer does not hide sender, recipient or contract activity recorded by the network.
Direct answers
Questions people ask
Can I infer that a provider stores every query?
No. The protocol tells you what a request contains, not how a particular service retains it. Check that service’s stated policy and configuration.
Does switching RPC providers erase earlier onchain activity?
No. Choosing another endpoint changes the service you query. Public transaction history remains on the network.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An RPC endpoint receives the requests sent to it. Ethereum balance queries can contain an account address; transaction lookups can reveal which activity you are checking. Because onchain activity is public, those requests can add context about your interests. Running your own node reduces dependence on a third-party query provider, but does not make public transactions private.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimBalance query: eth_getBalance includes the address being queried.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimTransaction lookup: RPC methods can request a particular transaction or receipt.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimPublic activity: Ethereum’s public ledger can reveal transaction relationships.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Ethereum JSON-RPC APIethereum.org contributors
RPC requests explicitly identify addresses and block scope; receipts and removed log fields support verification examples.
Locator: eth_getBalance; eth_getTransactionReceipt; block parameter; logs · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.990ZOpen source - Ethereum nodes and clientsethereum.org contributors
Post-Merge client roles, optional validators and synchronization modes.
Locator: Execution and consensus clients; synchronization; node types · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.405ZOpen source - Ethereum privacyethereum.org contributors
Public address activity and privacy consequences of sharing queries with intermediaries.
Locator: Public ledger; wallet and network privacy · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.562ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “What can an Ethereum RPC provider learn about a wallet?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-rpc-privacy/