X PrimeFlow

Gno.land Onyx Testnet

Gno.land Onyx Testnet
Chain ID: onyx-1
Block Height:
Network Status: Connecting
Explorer
Gno.land Onyx Testnet

Network & services

BonyNode RPC and WebSocket, Gno Explorer and practical node tools. Mainnet and Onyx use separate chains and genesis files.

Connection details

Chain ID
onyx-1
WebSocket ยท BonyNode
wss://gno-onyx-rpc.bonynode.online/websocket
Official RPC alternative

WebSocket JSON-RPC status request (height is a string):

{"jsonrpc":"2.0","id":1,"method":"status","params":["0"]}

Check this network now

RPC observation; block age and sync state matter. An online endpoint alone does not prove a healthy chain.

Not checked yet

Explorer tools

Genesis & SHA-256

Download from the official Gno release. Verify the checksum and chain ID before using it.

SHA-256
4b006fd7ccdec052865accc84dd29b2b76f8b57b2560789a15eedaa88f0e26c5

Genesis & SHA-256

(
export PATH="$PATH:/usr/local/go/bin:$HOME/go/bin"

set -euo pipefail
GNO_GENESIS_DIR="$(mktemp -d)"
curl --fail --location --output "$GNO_GENESIS_DIR/genesis.json" 'https://github.com/gnolang/gno/releases/download/chain/onyx/genesis.json'
printf '%s  %s\n' '4b006fd7ccdec052865accc84dd29b2b76f8b57b2560789a15eedaa88f0e26c5' "$GNO_GENESIS_DIR/genesis.json" | sha256sum --check
jq -e '.chain_id == "onyx-1"' "$GNO_GENESIS_DIR/genesis.json"
printf '%s\n' "$GNO_GENESIS_DIR/genesis.json"
)

Peers

Official bootstrap peers below; these are Gno infrastructure, not a BonyNode peer service.

persistent_peers
g1x5mlj5ava0dw9vkf4j6admjlzswm6f06p44krn@seed-1.onyx.testnets.gno.land:26656,g1grq5zswt0dlwwe7clr4359w70k2ewgse0gcwck@seed-2.onyx.testnets.gno.land:26656