Network status
This page states what is deployed. It is intentionally conservative: a release passing its checks does not by itself establish network readiness.
Summary
| Network | Chain ID | Kind | Public endpoints |
|---|---|---|---|
| Local development | centerchain-1 | Disposable single-node devnet | None; loopback only |
| Public testnet | centerchain-testnet-2 | Four validators, public RPC and REST | Yes |
| Production | — | Does not exist | — |
:::warning No production network There is no mainnet. There is no announced mainnet chain ID, genesis file, seed set, or validator set. Any instruction implying otherwise is wrong. :::
Local development chain — centerchain-1
A disposable single-node chain used by the test suite, the monitor fixtures, and the browser dashboards. It is bound to loopback and is never exposed publicly.
| Setting | Value |
|---|---|
| Chain ID | centerchain-1 |
| CometBFT RPC | http://127.0.0.1:26657 |
| Cosmos REST | http://127.0.0.1:1317 |
| gRPC | 127.0.0.1:9090 |
| Port source of truth | tests/devnet/ports.json |
| Investor dashboard | http://localhost:8000/ui/investor.html |
| Devnet console | http://localhost:8000/ui/devnet-console.html |
The devnet fixtures contain fixed recovery phrases. They are test material for this disposable chain only. Never reuse them on any other network, and never treat a devnet address as an account with value.
:::danger Do not reinitialize over existing state The initialization script can delete a node home even when the reinitialization flag is not set, if it judges the existing genesis invalid or incomplete. Inspect and back up the home directory before running it, and never run it against a home you did not create. :::
Public testnet — centerchain-testnet-2
Four validators with public RPC and REST endpoints. RPC and REST share the same
HTTPS base URL per node; CometBFT paths are served on it directly and
/cosmos/*, /centerchain/*, /ibc/*, and /cosmwasm/* are routed to the
Cosmos REST API.
| Validator | Base URL (RPC and REST) | Loopback RPC | Loopback REST |
|---|---|---|---|
| validator0 | https://rpc0.test.centerchain.org | 26657 | 1317 |
| validator1 | https://rpc1.test.centerchain.org | 26654 | 1316 |
| validator2 | https://rpc2.test.centerchain.org | 26651 | 1315 |
| validator3 | https://rpc3.test.centerchain.org | 26648 | 1314 |
A REST query against the shared base URL:
curl -s https://rpc0.test.centerchain.org/cosmos/base/tendermint/v1beta1/node_info
What the testnet does and does not prove
| Property | State |
|---|---|
| Chain ID | centerchain-testnet-2 |
| Validators | 4, all on a single host |
| Deployed app version | v1.2-testnet2-fdb815e (a build label, not a signed release) |
| Genesis SHA-256 | 3e79772a3e05c281d56e7f65c5d92ca5d175215821f74a6198b0e95070224fa7 |
Initial ucen supply | 1,000,000 CEN |
| Initial allocation | Owner 590,000; faucet 10,000; validators 0–3 × 100,000 self-delegated |
| Faucet | Address only; no HTTP faucet service |
The initial supply is not a cap: mint parameters allow ongoing inflation. A
separate testtoken denom is issued per validator for transfer testing.
Because all four validators share one host, the network exercises chain startup, transactions, module flows, and four-validator consensus. It does not test host-to-host networking or resilience to a host outage. Moving validators to separate hosts is planned and is a migration of this same chain, not a new genesis: the chain ID, genesis hash, and each validator's consensus identity stay the same.
The previous testnet is retired
centerchain-testnet-1 was stopped when v1.2 was deployed. Its data was retained
for reference but it is not producing blocks and its state is not compatible
with v1.2. The v1.2 release required a genesis reset because it changed the
authorization state schema; there is no in-place upgrade path. See
v1.2 § Applying v1.2.
Test tokens have no value
The public testnet is a closed, unauthenticated environment that can submit test transactions. Its tokens are valueless. Do not use it for private or production data, and do not advertise a download URL for a release until the repository has published a verified, signed artifact.
Releases
Release notes and the governed upgrade path live under Releases. The current release is v1.2, applied by a genesis reset; see Upgrading a network.
Pushing a v* tag starts the release workflow. Its checks run the installer
fail-closed tests, make test (vet, Go tests, monitor fixtures, production-config
checks) and make test-race. Only after those pass does GoReleaser create a
draft with Linux amd64/arm64 archives and a SHA-256 checksum manifest. The
workflow signs the manifest with Cosign, attests the archives and the manifest,
and then moves the release from draft to published.
The draft is an intermediate workflow state, not a manual review handoff: a failed check or a failed attestation prevents publication entirely.
git tag v0.1
git push origin v0.1
A successful software release does not establish testnet or production readiness.