Network settings
- RPC endpoint
https://jsongw.mainnet.tolar.io/jsonrpc- Chain ID
1 (0x1)- Currency
- TOL
Configuration checked 2026-10-01. This is connection information, not a live availability indicator.
- RPC endpoint
https://jsongw.testnet.tolar.io/jsonrpc- Chain ID
2 (0x2)- Currency
- TOL
Configuration checked 2026-10-01. This is connection information, not a live availability indicator.
Tolar chain IDs overlap Ethereum network IDs. Confirm the RPC URL—not just the chain ID—before signing. Read compatibility guidance.
Chain IDs are not network identity
Section titled “Chain IDs are not network identity”Mainnet uses chain ID 1, also used by Ethereum mainnet. Testnet uses 2, which overlaps historical Ethereum configurations. Some wallets refuse a custom network with an already-known chain ID or silently reuse an existing network entry.
- Check the full RPC URL and selected wallet network.
- Configure providers explicitly; do not use a default Ethereum provider.
- Test the exact wallet and library version before recommending it.
- Never assume an “Add network” wallet request will work universally.
Request format
Section titled “Request format”Use JSON-RPC 2.0 over POST /jsonrpc with the Content-Type: application/json header. Ethereum quantities are hexadecimal strings, such as 0x1; legacy Tolar methods have their own documented formats.
Test funds
Section titled “Test funds”The legacy testnet faucet is an external service. Its root URL returned an unavailable response during the website review on 2026-09-30. Do not assume it is working, and do not send mainnet funds to obtain test tokens. Contact the Tolar team for the current test-funding process if it remains unavailable.
Connection troubleshooting
Section titled “Connection troubleshooting”A browser CORS failure does not prove the chain is offline. Test the same read-only request from your backend, check the URL and timeout, and inspect the returned JSON-RPC error. Never disable TLS verification to work around a connection problem.