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.

📱 Telefona kur / Install on phone New: a separate phone wallet app (iOS + Android, Add to Home Screen, works offline). Unlike this CLI page, it creates keys inside your phone's browser and stores them encrypted. Testnet only, unaudited.
NO SECRET IN BROWSER NO ACCOUNT REQUIRED NO REMOTE WALLET API
ZYRON / WALLET IDENTITY
PUBLIC ADDRESSZYN••••••••••••••••••••••••••••••••••••••••
CURVEsecp256k1
ADDRESSZYN + 40 hex
KDFscrypt
CIPHERAES-256-GCM
PRIVATE KEY STAYS LOCAL

What works today

01Generate

The canonical CLI creates a fresh secp256k1 private key using the operating system cryptographic random source.

02Encrypt

New keystores use scrypt-derived encryption keys and AES-256-GCM authenticated encryption.

03Derive

The public address is derived from the public key and encoded as ZYN plus 40 lowercase hex characters. A mixed-case checksum form is for display only.

04Control

The website never receives the password, private key, keystore file or signing request.

01 / CREATE

Generate the wallet
on your machine.

Choose a task and your operating system. The script checks out the exact canonical release revision shown below, installs the locked L1 dependencies, builds the CLI and asks for the wallet password (twice) inside your local terminal, rejecting weak passwords. No password file is kept: it exists only in a private temporary file for the few seconds the CLI needs it and is then shredded. Right after creating the wallet it runs a restore test and prints the address, its checksummed form and the keystore SHA-256 for your backup records. For automation only, ZYRON_WALLET_PASSWORD skips the prompt (the script warns: environment variables can leak to other processes of your user, shell history and CI logs).

OUTPUTwallet.json
PASSWORDPrompted; never stored
RELEASEloading…
NETWORKNot required to create
LOCAL SETUP SCRIPTbash
HOW TO RUN

Save the script, review it, then run it from Terminal. It will request a strong password locally and create the keystore 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

Keystore + password.
Two separate backups.

The encrypted keystore and its password are both required for local signing. The scripts do not save the password anywhere, so remember it or write it down offline. Keeping it next to the keystore defeats part of the protection provided by encryption.

  1. Write down the address and the Keystore SHA-256 the script prints.
  2. Copy wallet.json to one offline medium and keep the password (on paper or in an offline password manager) in a different place.
  3. Test the copy with 2 · Verify / restore a backup above. It asks for the password and must print the same address and hash.
  4. Restore on a new computer the same way: run the verify script against your backup, then use the verified keystore with the CLI.
ENCRYPTED KEYSTOREwallet.jsonContains encrypted key material + public identity
KEEP SEPARATE
PASSWORD BACKUPyour passwordNever saved by the scripts; keep it 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 / CHECK

Check an address
before you share it.

ZyronChain addresses are ZYN + 40 lower-case hex characters, derived as the first 20 bytes of SHA-256 of the 64-byte secp256k1 public key. The consensus form has no checksum, so ZyronChain also defines a display-only checksum: some letters are upper-cased according to SHA-256 of the address (like Ethereum's EIP-55). A wrong upper/lower-case pattern means a typo. The plain lower-case form stays valid everywhere and is what the chain stores (spec ↗). This checker runs entirely in your browser; it never asks for a private key, password or keystore.

Paste a ZYN address, a public key, or both.

Never paste a private key anywhere, including here. A public key and an address are safe to share.

04 / USE

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.

The honest way to exercise a transfer today is local, not a hosted testnet: cd l1 && npm ci && npm run devnet. Follow the public tester guide for loopback RPC, wallet creation and the printed disposable keys. This website does not publish a public RPC, explorer or faucet.

Read docs/PUBLIC_TEST.md
ADDRESS

Receive ZYN

Your public ZYN… address can be shared. A private key, encrypted keystore or password must never be shared.

BALANCE

Read only after activation

No public wallet RPC is published today. When the public network activates, this website will publish the canonical chain ID and a separately bounded read-only endpoint—not a custody or hosted wallet service.

TRANSFER

Sign on your machine

The CLI reads the encrypted keystore locally, creates the canonical signed transaction and submits only the signed public transaction payload.

Fill in receiver and amount to build the command. Nothing is sent.

TRANSFER TEMPLATE · ACTIVATION GATED
# Today's CLI reads the password from a 0600 file: create it only for this command, then delete it.
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
05 / SAFETY

The wallet rule:
the secret does not travel.

NEVEREnter a wallet password on zyronchain.com

The canonical website intentionally has no password field for wallet creation.

NEVERUpload wallet.json to “verify” a wallet

The website has no wallet-upload workflow and should never request one.

CHECKConfirm the address before receiving funds

Use the address stored in the authenticated keystore and compare it carefully when copying.

CHECKConfirm chain ID and public endpoint

Do not use rehearsal/private endpoints as though they were the activated public network.

NEVERTrust anyone offering a “recovery” or “airdrop claim”

ZyronChain has no support desk that needs your files, and mining rewards do not exist (mining is retired).

Key
secp256k1, 32 bytes from the OS CSPRNG (crypto.randomBytes), redrawn if outside the valid range
Address
ZYN + first 40 hex of SHA-256(64-byte public key x||y)
KDF
Current release (v1): scrypt N=32768, r=8, p=1, fresh 32-byte random salt per keystore. v2 in review (PR #921): N=131072 (2^17), parameters bound into the authenticated data, v1 still readable and migratable
Cipher
AES-256-GCM, fresh 12-byte random IV, 16-byte authentication tag; public key + address bound as associated data
Decrypt check
Wrong password or any tampering fails authentication; the decrypted key must re-derive the stored public key and address
Password
Scripts require 12+ characters, 6+ distinct characters and about 60+ estimated bits; a long random passphrase is strongly recommended. Never stored by the scripts
Checksum
Display only: letter i upper-cased when nibble i of SHA-256("zyronchain/address-checksum/v1:" + address) ≥ 8. Consensus unchanged
TÜRKÇE ÖZET

Cüzdan: kısa ve net.

READY TO START?

Create locally.
Keep control.

No ZyronChain account is required. Your cryptographic identity belongs to the key you generate and protect.

Generate setup script ↑