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
Mine issuance.
Keep finality separate.
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
- Work
- SHA-256
- Initial target
- 20 bits
- Initial reward
- 6.25 ZYN
- Claims / block
- 1 max
- Finality
- >2/3 validator quorum
Mining model
Proof of Work issues ZYN. It does not choose the chain.
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.
Search locally
SHA-256 work runs on the miner machine. Private signing material remains local and encrypted at rest.
Sign the claim
The successful public mining claim is signed with the miner key after the local keystore is decrypted.
Submit and finalize
The claim enters bounded mempool admission and only earns issuance if it is included in a finalized block.
Economics
Finite issuance with deterministic halving.
50,000,000ZYN historical genesis + mining cap
6.25 ZYNinitial finalized claim reward
4,000,000successful claims per halving
100,000,000atoms per ZYN
Genesis allocations reduce the available mining budget atom-for-atom. Burned transaction fees remain burned and do not reopen mining supply.
Canonical miner workflow
Encrypted key custody is mandatory.
Use the packaged Node.js miner with a ZyronChain encrypted wallet and either loopback HTTP or a remote HTTPS RPC endpoint. Legacy plaintext private-key JSON is intentionally rejected.
POSIX / NODE.JS 22+
cd ./-zyronchain/l1
npm ci
npm run build
chmod 600 /path/to/wallet.json /path/to/wallet.password
npm run mine -- \
--genesis /path/to/genesis.json \
--key /path/to/wallet.json \
--password-file /path/to/wallet.password \
--rpc http://127.0.0.1:9137Security boundaries
The miner is deliberately local-first.
Encrypted keystore only
The packaged miner rejects legacy plaintext private-key JSON. On POSIX systems wallet and password files must be owner-only before they are read.
Remote RPC requires HTTPS
Plain HTTP is accepted only for loopback. Remote transport must protect the public claim submission path from interception or tampering.
Bounded mining admission
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.
No browser custody
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
Code availability is not network readiness.
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.
Current website policy
Do not treat this launchpad as a statement that public mining, public testnet value transfer or mainnet is live. Verify the repository readiness report and target network protocol schedule first.
Open readiness evidence ↗