The canonical CLI creates a fresh secp256k1 private key using the operating system cryptographic random source.
LOCAL-ONLY WALLET SETUP
Create your
ZyronChain wallet.
Your wallet is a cryptographic identity, not a website account. This page prepares a local setup script. The private key, wallet password and encrypted keystore are created only on your computer.
NO SECRET IN BROWSER
NO ACCOUNT REQUIRED
NO REMOTE WALLET API
ZYRON / WALLET IDENTITY
PUBLIC ADDRESS
ZYN••••••••••••••••••••••••••••••••••••••••CURVEsecp256k1
ADDRESSZYN + 40 hex
KDFscrypt
CIPHERAES-256-GCM
PRIVATE KEY STAYS LOCAL
New keystores use scrypt-derived encryption keys and AES-256-GCM authenticated encryption.
The public address is derived from the public key and encoded as ZYN plus 40 lowercase hex characters.
The website never receives the password, private key, keystore file or signing request.
01 / CREATE
Generate the wallet
Generate the wallet
on your machine.
Choose your operating system. The script checks out a pinned reviewed repository revision, installs the canonical L1 dependencies, builds the CLI and asks for the wallet password inside your local terminal.
LOCAL SETUP SCRIPTbash
HOW TO RUN
Save the script, review it, then run it from Terminal. It will request a 12+ character password locally and create files with restrictive permissions.
Review before running.
This website gives you a reproducible local setup path; it does not make terminal commands inherently trusted. Read the generated script, verify the repository URL and pinned revision, and keep your machine clean before creating a wallet.
02 / BACKUP
Two files.
Two files.
Two separate backups.
The encrypted keystore and its password are both required for local signing. Keeping them together defeats part of the protection provided by encryption.
ENCRYPTED KEYSTOREwallet.jsonContains encrypted key material + public identity
KEEP SEPARATE
PASSWORD BACKUPwallet.passwordKeep offline and away from the keystore copy
✓ Keep at least one offline backup.
✓ Never commit either file to GitHub.
✓ Never paste the password or private key into support chats.
✓ Test recovery before relying on the wallet for value.
03 / USE
Sign locally.
Sign locally.
Submit deliberately.
The canonical CLI can submit signed transfers to a wallet-facing RPC endpoint. Public wallet RPC is not currently published, so the example stays activation-gated instead of silently pointing users at validator infrastructure.
Receive ZYN
Your public ZYN… address can be shared. A private key, encrypted keystore or password must never be shared.
Read through a public gateway
When the public network activates, this website will publish the canonical chain ID and separately bounded wallet/read-only endpoint.
Sign on your machine
The CLI reads the encrypted keystore locally, creates the canonical signed transaction and submits only the signed public transaction payload.
TRANSFER TEMPLATE · ACTIVATION GATED
export ZYRON_KEYSTORE_PASSWORD_FILE=/secure/path/wallet.password
node dist/src/cli.js transfer \
--key wallet.json \
--rpc <PUBLIC_WALLET_RPC_WHEN_PUBLISHED> \
--chain-id <CANONICAL_CHAIN_ID> \
--to ZYN<receiver-address> \
--amount-atoms 100000000 \
--fee-atoms 1000
04 / SAFETY
The wallet rule:
The wallet rule:
the secret does not travel.
The canonical website intentionally has no password field for wallet creation.
The website has no wallet-upload workflow and should never request one.
Use the address stored in the authenticated keystore and compare it carefully when copying.
Do not use rehearsal/private endpoints as though they were the activated public network.
READY TO START?
Create locally.
Generate setup script ↑
Create locally.
Keep control.
No ZyronChain account is required. Your cryptographic identity belongs to the key you generate and protect.