Read finalized tip
The miner derives work from the current canonical state rather than mining an unbounded independent chain candidate.
PROTOCOL V5 · PROOF OF WORK ISSUANCE
ZyronChain miners compete for permissionless ZYN issuance with tip-bound SHA-256 work. Validators still provide canonical block finality. The miner decrypts and signs locally; your private key and password are never submitted to RPC.
MINING MODEL
Mining model
Mining work is committed to the chain ID, miner account, exact next confirmed nonce, next height, previous finalized block hash and deterministic reward. When the finalized tip changes, old work becomes stale. A successful claim still has to be included and finalized by validator quorum.
The miner derives work from the current canonical state rather than mining an unbounded independent chain candidate.
SHA-256 work runs on the miner machine. Private signing material remains local and encrypted at rest.
The successful public mining claim is signed with the miner key after the local keystore is decrypted.
The claim enters bounded mempool admission and only earns issuance if it is included in a finalized block.
Economics
Genesis allocations reduce the available mining budget atom-for-atom. Burned transaction fees remain burned and do not reopen mining supply.
Canonical miner workflow
Default npm run devnet is protocol v1 and will not finalize mining claims. Use the loopback RPC port printed by your local launcher after protocol v5 is actually scheduled. 127.0.0.1:9137 is only the CLI default if you started a node on that port yourself. This is not public mining and does not publish RPC. Remote RPC must be HTTPS. Legacy plaintext private-key JSON is intentionally rejected.
cd ./-zyronchain/l1
npm ci
npm run build
# Default npm run devnet stays protocol v1. Use the printed local RPC port.
chmod 600 /path/to/wallet.json /path/to/wallet.password
npm run mine -- \
--genesis /path/to/local/genesis.json \
--key /path/to/wallet.json \
--password-file /path/to/wallet.password \
--rpc http://127.0.0.1:<printed-port>Choose a platform manually when signed immutable miner releases are activated. These controls are intentionally disabled until the same public-mining and trusted-release gates as the auto-detected download pass.
No platform option executes software from the browser. After a future verified download, the operating system still requires user consent to open or run it.
Security boundaries
The packaged miner rejects legacy plaintext private-key JSON. On POSIX systems wallet and password files must be owner-only before they are read.
Plain HTTP is accepted only for loopback. Remote transport must protect the public claim submission path from interception or tampering.
Mining claims must use the exact next confirmed miner nonce, and the mining subpool is bounded so future-nonce or volume flooding cannot consume unbounded claim capacity.
This page never requests, stores or transmits a private key, seed phrase or wallet password. It is documentation, not a browser miner or custody service.
Activation boundary
Public mining remains evidence-gated. Before mainnet economics are frozen, the project still needs real multi-operator evidence for inclusion fairness, stale-work behavior, heterogeneous hardware skew, pool concentration, target calibration and Internet-facing RPC abuse resistance.
Do not treat this launchpad as a statement that public mining, public testnet value transfer or mainnet is live. There is no hosted miner RPC. Verify the repository readiness report and the target network protocol schedule first.
Public tester guide ↗ · Readiness evidence ↗