Awaiting response
Corroboration has not been inspected yet.
- Head / finalized
- —
- Finality distance
- —
- Gateway round trip
- —
GENESIS-4 / PUBLIC GATEWAY
Read the chain.
See the evidence.
A practical RPC reference for network state, validators, UTXOs and transaction status. Run selected read-only calls against the published gateway, inspect the raw reply and carry the same request into your own tools.
No mnemonic, private key or signing workflow belongs in this console. The gateway's observations are a starting point for verification, not settlement authority.
CHAIN / LIVE SNAPSHOTCONNECTING
CANONICAL HEIGHT—
HEAD SLOT—
FINALIZED HEIGHT—
ACTIVE VALIDATORS—
SYNC LAG / SLOTS—
Waiting for a gateway responseSource: getchaininfo
Public endpoint
https://posternlabs.com/g4rpcJSON-RPC 2.0 over HTTPS · POST · Content-Type: application/json01 / GATEWAY EVIDENCE
What answered.
How it was checked.
Live read requests to the published gateway. Chain requests wait up to 20 seconds; build requests wait up to 12 seconds. The panel refreshes every 30 seconds while this tab is visible. These observations are not independent proof of consensus.
Requesting chain and build evidence…
Awaiting response
Witness freshness and plane agreement are reported by the gateway.
- Archival witnesses
- —
- Witness age
- —
- Plane agreement
- —
- Plane age
- —
Awaiting response
Self-reported identity of one answering node. A matching digest is evidence of matching source content, not remote attestation.
- Source node
- —
- Commit
- —
- Source digest
- —
A response may be cached. On a failed or invalid chain request, the live values are cleared; earlier valid replies remain in this tab's history. Compare a trusted node and your own release artifacts before operational decisions. Finality distance is a height difference, not a waiting time or confirmation policy.
THIS BROWSER TAB / GETCHAININFO
Observation history
Waiting for the first chain request.
RECORDED ATTEMPTS0
LAST VALID REPLY / LOCAL—
HEAD CHANGE SINCE PREVIOUS VALID REPLY—
FINALITY DISTANCE CHANGE—
| Observed (local) | Result | Head | Finalized | Distance | Reported evidence | Round trip |
|---|---|---|---|---|---|---|
| No samples in this tab yet. | ||||||
Kept in memory only, capped at 120 requests and cleared when this tab reloads. Failed and invalid requests are recorded. Browser timestamps and round trips come from this device. These samples cannot establish gateway uptime, chain progress, consensus or a finality SLA; responses may be cached. Compare independent nodes before operational decisions.
02 / READ-ONLY CONSOLE
Ask a specific
network question.
The console sends only the selected read method and public parameter to the gateway. The raw JSON reply is shown without interpreting it as a transaction decision.
RAW RESPONSE
Select a method and run a request.
REPRODUCE IN YOUR TERMINAL
The gateway may append corroboration metadata. Check its level and witness freshness. A node_local reading is not a multi-node consensus statement.
03 / METHOD MAP
A small surface.
Useful distinctions.
Methods below are routed in the Genesis-4 node source. The gateway may apply its own availability, cache and corroboration rules.
Chain & blocks
getchaininfo- Head, slot, finalized checkpoint and synchronization.
getblockcount- Height, slot, epoch and finalized height.
getblockbyslot- Canonical block metadata for a slot; an empty slot is an error.
getblockbyid- Block metadata by 64-hex block ID.
Validator state
getvalidatorcount- Registered and active totals with aggregate stake.
getvalidators- Current validator registry summary.
getvalidator- One validator by index, including lifecycle fields.
getvalidatoradmission- Current admission flag, stake bounds and delays; node-local.
Outputs & status
getbalance- Balance by 64-hex script hash, in satoshis.
getutxos- Unspent outputs by script hash; limited and not paginated.
gettxout- Whether one output remains unspent at the answering head.
gettxstatus- Pending, included, justified, finalized or unknown by txid.
Build & mempool
getbuildinfo- Self-reported node version and source digest.
getmempoolinfo- One node's pending pool and next base fee.
sendrawtransaction- Write operation for pre-signed bytes. Excluded from this console.
VERSIONED MACHINE-READABLE REFERENCE
Download JSON catalog ↗RPC catalog v1
Fifteen read-only methods, positional and named parameters, response fields, limits and source provenance. The checked source and the public gateway can differ; only getbuildinfo was sampled for this catalog.
OPERATOR TOOL / NODE.JS
Read-only compatibility probe
Check six bounded, no-argument methods against your HTTPS or local RPC endpoint. Receive per-method shape and error diagnostics. Keep the probe and catalog JSON in the same directory. The result is one endpoint's observation, not proof of chain identity or finality.
node probe.cjs --rpc https://posternlabs.com/g4rpc --json
04 / INTEGRATION BOUNDARIES
Build the right
decision path.
The public RPC surface is deliberately smaller than an exchange transaction index or a wallet service.
Finality needs policy
gettxstatus reports a status enum, but its current node response does not include complete transaction inputs, outputs or fee data. Track known txids and correlate with your own ledger. Finalized status needs a risk policy and independent observations.
No node-held keys
The node does not expose getnewaddress and this page never requests a secret. Address derivation, signing and key custody belong in audited client or partner-controlled components.
Separate local observations
getmempoolinfo, build identity and some admission data describe an individual observer. Two mempools can disagree without a chain fork. Treat self-reported build hashes as evidence, not remote attestation.
Check the release
Compare the live getbuildinfo response with the release you integrated. Confirm checkpoint freshness and method behavior before deposits, withdrawals or validator actions.