Overview
Privacy-preserving Web3 relay across supported blockchains.
About 1RPC
1RPC is the relay safeguarding blockchain interactions in Web3.
A product by Automata Network, the relay eradicates metadata exposure and leakage with a one-click user experience. 1RPC offers support across major blockchains, including Ethereum, BNB Chain, Polkadot, zkSync Era, Base, and more.
1RPC's underlying relay infrastructure is attested by Automata Network to guarantee the integrity of the secure enclaves that keep 1RPC computation confidential.
Background
When users perform any kind of action, such as viewing their balance, creating a transaction, or bidding for an NFT, requests are submitted to the blockchain through an RPC. Typically, the RPC endpoint can view, and sometimes store, those requests. These requests may contain both user data and metadata.
Data refers to information related to an on-chain interaction, including read requests such as wallet addresses. Metadata provides or suggests information about data:
- IP address (geolocation)
- User agent (browser version and OS platform)
- Request timestamp (timezone)
Web3 relay summary
1RPC.io provides a one-click experience for users to connect to supported blockchains, including major networks such as Ethereum, BNB Chain, and Base. The Web3 relay utilizes TEEs to eradicate metadata exposure and leakage to infrastructure providers, thereby protecting user privacy.
- Sensitive metadata such as IP addresses, device information, and timestamps, are appended to RPC requests.
- Relaying requests using a TEE relay ensures that no metadata will be stored by the operator or communicated to providers.
- An industry-standard TLS connection is established between the user, enclave, and RPC provider for end-to-end encryption.
1RPC has relayed close to over 49.1 billion relays to date, with over 5 million monthly active users.
Because the relay can cryptographically attest to running secure hardware (for example, via Automata's DCAP Attestation), anyone can publicly inspect its infrastructure, verify its functionality, and know that they are connecting to the genuine relay.
Zero-tracking methods
1RPC shields user data and metadata before requests are relayed to RPC providers. Its lightweight design is able to scale to support high traffic volume.
Metadata masking
1RPC replaces metadata attached to a user's request with its own. As a result, the original metadata attached to a particular request, and any personal information which identifies the user, is removed from the view of RPC providers.
Random dispatching
Requests are dispatched randomly to RPC providers, making it impossible to log the association between accounts with the same private key, even when multiple requests are sent from different addresses consecutively.
Burn after relaying
1RPC does not store or collect data and metadata that passes through the relay; it is discarded once the request is complete. Computation happens within a secure enclave to prevent third-party access or tampering.
Multicall disassociation
A single RPC call containing multiple batched queries can reveal the relationship between different accounts under the same wallet. When feasible, 1RPC disassembles multicall transactions back into individual requests.
Request caching
Certain read-only queries are cached to reduce response time and the information load passed to RPC providers. The cache policy can evolve as usage and capacity requirements change.