Proxies for testnet development
Recommended proxy: Datacenter proxies Validate client and RPC paths on testnet without mixing mainnet credentials.
What this workflow needs
- Pin chain ID, endpoint and test account in test scripts.
- Record request errors and transaction hashes; a proxy does not change consensus.
Recommended setup and alternatives
Datacenter proxies
Fixed HTTP datacenter access suits testnet script diagnostics; choose fixed ISP for sustained browser debugging after wallet connection. Faucet and RPC remain separate.
Explore productFrom setup to a first check
Confirm test chain ID and RPC URL
Set HTTP proxy and isolate test credentials
Send a read-only request before transaction tests
Common questions
Questions about this task
Does the proxy provide test tokens?
No; obtain test tokens from the network faucet or your development setup.
May a test private key go into the page?
No; isolate test keys and never use mainnet keys in tests.
Platform names identify use cases, not official partnerships, eligibility guarantees or tested compatibility.
Turn your choice into a connection you can check
Adjust region, protocol, line and term in configuration. Check that page for current pricing and availability.