Browsers cannot safely provide stable inbound raw TCP, durable background consensus or production key custody. The website launches a local operator workflow instead.
Validator Launchpad
Configure in the browser.
Configure in the browser.
Run on your own machine.
ZyronChain never asks the website to hold a validator secret. This launchpad prepares deterministic operator scripts; your encrypted validator key is created locally on your device and stays there.
Private key stays local
RPC binds to 127.0.0.1
Exact release pinned
01
NO SECRET IN BROWSER
Create validator identity
Build a one-time setup script. The script creates the encrypted key on the machine where it runs.
02
PRIVATE / NON-VALUE
Join a friends/private testnet
Paste the coordinator-provided genesis and explicit PeerId-pinned peers. The browser only packages public configuration into a local start script.
03
ACTIVATION GATED
Public network enrollment (not activated)
The governance class is authorized, but public-testnet activation is still blocked by external evidence gates. Authorized does not mean activated. This launchpad prepares local scripts only—not hosted enrollment.
The honest test path today is local cd l1 && npm ci && npm run devnet — not a hosted enrollment form or public RPC.
Operator safety
What the website deliberately cannot do.
The launchpad neither requests nor stores validator private keys, passwords or HSM credentials.
Consensus RPC remains loopback-only by default. Public interfaces must use a separately bounded read-only gateway.
Friends/private testnets are available now; public-network enrollment stays disabled until activation evidence is actually closed.