The project's network serves several public interfaces. This page says what each one is for and what you can check through it — not so that you can copy numbers away.

Interface	Used for	What you can verify yourself
Consensus interface (Cosmos RPC)	Asking node status, the list of signers, the genesis file	When this network was born · who signs blocks · whether it is advancing
EVM-compatible interface (JSON-RPC)	Pointing familiar wallets and tools at the network	Calling contracts and reading balances with tools you already trust
Query interface (REST)	Reading state per module	The parameters actually in force, rather than the ones in a document
Test faucet	Requesting a small amount to experiment with on a test period	That this is test-period money, not an asset
Explorer	Looking with your eyes, no tooling required	Blocks, transactions, signers — a view built by another party

Diagram

flowchart TB You["Your tooling"] --> C["Consensus interface status · signers · genesis"] You --> E["EVM interface wallets · contracts"] You --> Q["Query interface parameters in force"] C --> T{"Two answers must agree: which network does the address claim? when was the first block born?"} T --> OK["They agree: read on"] T -.-> NO["They differ: believe no number"]

Figure 26 — Every way in passes the same two-question check.

The naming rule, and why it is worth more than it looks. The project sets a rule: the public address of a test period carries the word testnet in its name, the official network will have a name of its own, and an address that has meant one thing never comes to mean another. Because of that rule, a link you save keeps its meaning, instead of one day quietly returning another network's data. It is also why Check the network yourself makes you ask two questions rather than one: which network does this address say it is and when was its first block born — the two answers must point to the same place, and if they differ, one of the two statements is false.

Three things this page deliberately does not do. It does not copy a list of addresses into the body as a permanent truth — the list lives in the project's technical documentation, under Public endpoints, and that is the correct version. It does not record any number of the network — live numbers belong in the read-it-directly panel in Check the network yourself. And it does not promise these endpoints will always be free or always survive any load: this is infrastructure for experimenting, not a service commitment.

The explorer is a separate project. It is not run by the same team as the network, and that is a plus rather than a minus: a second party reading the same ledger is the cheapest way to catch a first party telling it wrong.

In short: an endpoint is only trustworthy when its name says the same thing as the data it returns — ask both questions before believing any number.