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.

While private transactions may still be vulnerable to some form of tracing, 1RPC achieves true zero-tracking through a number of technical methods:

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, which makes 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, which are discarded once the request is complete. All computation happens within a secure enclave which prevents access and tampering by third parties.

Multicall disassociation

A single RPC call containing multiple batched queries can reveal the relationship between an umbrella of different accounts under the same wallet. When feasible, 1RPC disassembles multicall transactions back into its individual requests.

Request caching

Certain read-only queries are cached to reduce response time and the information load passed to RPC providers. The current LRU (least recently used) policy will be iterated as we learn more about usage and capacity requirements.

Last updated