Migrate from Infura / Alchemy
Select the same network as your existing provider before replacing the URL. The destination below is Ethereum; changing the provider must not silently change the chain. Compare eth_chainId on both endpoints and review the supported methods.
| Provider | Before | After |
|---|---|---|
| Infura | Your existing URL for the same network | https://ethras.org/v1/ethereum/<YOUR_KEY> |
| Alchemy | Your existing URL for the same network | https://ethras.org/v1/ethereum/<YOUR_KEY> |
Differences to check
- Filters (
eth_newFilterfamily) are not supported here — polleth_getLogs, or use subscriptions on a WebSocket-enabled network. - Trace/debug namespaces and deep archive state are unavailable — keep a specialist provider for those workloads.
- Vendor-specific APIs (e.g.
alchemy_*, enhanced NFT/token APIs) have no equivalent; standard methods only. - Batching is supported within gateway limits. This network also enables WebSocket newHeads and logs subscriptions.
- Quotas are account-wide per UTC day (see Rate limits & quotas) rather than compute units.