RP1 exposes the standard Cosmos query and transaction APIs around a custom consensus/RPC layer, plus native EVM JSON-RPC when enabled.
Public testnet endpoints
The public RP1 testnet reference is:
| Surface | Endpoint |
|---|---|
| RPC | https://testnet.rpc.rp.one |
| REST | https://testnet.rest.rp.one |
| gRPC authority | testnet.grpc.rp.one — use the release-published port, TLS, and authority settings; no plaintext default is implied. |
| EVM JSON-RPC | https://testnet.evm.rp.one |
| Chain ID | chain-1 |
| Native denom | urp1 |
| Address prefix | rp1 |
| Wallet | https://app.rp.one |
| Explorer | https://testnetexplorer.rp.one |
| Docs | https://docs.rp.one |
One RP1 is 1,000,000 urp1. Treat the endpoint set, chain ID, and accepted gas settings as network configuration, not constants to hard-code across environments.
The faucet must stay server-side. Never place a faucet mnemonic or private key in a browser bundle, mobile app binary, or public repository.
Choose an API
| API | Best for | Notes |
|---|---|---|
| REST / gRPC gateway | Account, module, transaction, and parameter queries | Generated from the current protobuf services. |
| gRPC | Typed service-to-service integration | Use the current proto package and endpoint TLS policy. |
| RP1 JSON-RPC | Status, transaction broadcast, retained transaction observation, block/DAG queries, WebSocket events | RP1 has custom canonical-head and retained-data rules. |
| EVM JSON-RPC | Solidity deployment, calls, receipts, logs, and Ethereum tooling | Available when EVM is enabled; use the target network’s EVM endpoint. |
Read REST and gRPC and custom RPC before building a client that depends on historical data.
Discovery
Use the target endpoint to discover:
- chain ID and node status;
- module parameters and enabled features;
- supported assets, pools, markets, bridge chains, runtimes, and connectors;
- account sequence and balance;
- current retained height and observation capabilities.
The docs site intentionally does not publish a frozen list of every generated route. Protobuf definitions and generated gateway output are the canonical API reference for a deployed binary.