Censorship Resistance
Simple Page is built on decentralized infrastructure. But infrastructure can fail or be blocked. This page explains what to do when that happens.
When You Might Need This
You may need to override default services if:
- The default RPC provider is censored, unavailable, or returning stale data.
- The Simple Page indexer (DService) is offline or blocked in your region.
- The frontend can't connect to Ethereum or can't load your site data.
Overriding the RPC Provider
The RPC endpoint is how Simple Page reads and writes to Ethereum. By default, it tries your connected wallet, then a built-in public RPC.
If both fail, add your own RPC directly in the URL:
https://simplepage.eth.link/?ds-rpc-1=eth.drpc.org
The value must be URL-encoded. When you open this link, Simple Page will show a banner confirming the custom endpoint and route all blockchain requests through it.
Tips:
- Use any valid Ethereum mainnet RPC URL (public or private).
- For maximum independence, use a self-hosted Ethereum node.
Overriding the DService (Indexer)
Simple Page uses DService nodes to index and serve content. Normally, these are discovered on-chain via an ENS text record on new.simplepage.eth.
If that lookup fails or the URLs are blocked, specify a DService endpoint directly:
https://simplepage.eth.limo/?ds-new.simplepage.eth=simplepg.org
This tells Simple Page to skip the on-chain lookup and use simplepg.org directly.
Tips:
- To run your own DService, see Run a Node.
- You can combine both overrides in the same URL.
- This is most useful if the main indexers are offline or blocked in your region.
The Design
Censorship resistance is not a feature — it's the architecture. Content lives on IPFS (peer-to-peer). Names live on Ethereum (decentralized). The frontend is open source. If everything we run goes down, you can still access your site by running your own node and pointing to your own RPC.
The tools exist. This page shows you how to use them.