INDEPENDENT LAYER-1 · 9 DECIMALS

Your keys.
Your ZX.

Create, import, and verify a self-custody ZX wallet. Only encrypted backups are stored on this device. Private keys and passphrases never leave this device. Signed transactions are sent only after explicit broadcast approval when a pinned Signed Core is configured.

Before using funds: Verify the official HTTPS domain, save an encrypted backup offline, and never share your password or backup. Browser storage can be deleted. This wallet is not yet externally security-audited or approved for Mainnet funds. Unsupported browsers fail closed.

Device compatibility

Testing native ML-DSA-87 support…

Only native WebCrypto ML-DSA-87 is accepted; no classical-crypto or fake-key fallback.

Create new wallet

Wallet password (16+ UTF-8 bytes)Confirm password

Creates a native ML-DSA-87 keypair on this device. The generated encrypted backup must be saved before using the wallet.

Restore encrypted wallet

Select ZYQRAX Web Wallet backup (.json)Backup password

Only the ZYQRAX Web Vault format is supported here. Existing desktop encrypted vaults use a different format.

My wallets on this device

Select wallet

—

Password to unlock for signing

Locked. Keys are decrypted only when you explicitly unlock.

Community activity login proof

Use only a challenge obtained from the official ZYQRAX activity service. Review the chain, address, Genesis hash, nonce and expiry before signing. This produces a login proof, not a ZX transaction.

Paste the exact login Challenge JSONSigned proof (copy into trusted activity client)

Activity acceptance and ZX payout remain subject to the original attestor and on-chain Claim validation. This page does not broadcast or mint.

ZX transfer — verify, sign, broadcast

The HTTPS wallet host must be configured with pinned original Signed Core commitments before broadcast can be enabled. Keys stay on-device. This is producer-signed inclusion, not Byzantine finality. Independent device security audits and real network testing remain necessary before public funds.

Checking signed network configuration…

Account not loaded

Recipient ZX address Amount in ZX (up to 9 decimal places) Network fee in ZX (up to 9 decimal places) Current wallet nonce (from pinned chain when connected) Original-chain signed envelope (public data only)

Transaction hash / signed block receipt

Import unsigned ZX Origin / Construct / Commons request

Paste ONLY a request you reviewed. The wallet rechecks the Genesis and config pins, and verifies the original Signed Core itself. Import fills fields only: it NEVER signs or broadcasts. Review and approve each action separately below.

No public intent imported.

ZX Origin — ZTS fixed utility credits

Create, transfer or redeem ORIGINAL on-chain service credits through the pinned Signed Core. No private key reaches the server. Creation requires at least 1,000 ZX network gas. Not a public Mainnet readiness claim.

Action

Token name (3–40 characters)Symbol (uppercase, 2–10 characters)Token decimals (0–9)

Credit amount in native token base unitsZX gas fee (in ZX) Signed ZTS envelope (public data)

Signed-Core transaction hash / verified receipt

Requires a locally unlocked wallet and explicitly pinned Genesis.

ZX Construct — on-chain service-credit checkout

Build a deterministic checkout for an existing ZTS service-credit asset, or import an issuer-provided blueprint. Both the actual asset issuer and your token balance are read from the pinned Signed Core before signing. Redeeming transfers credits back to the issuer, records a one-use order hash on-chain, and charges the original ZX fee. The on-chain receipt does not prove off-chain service delivery or issuer identity. Verify the issuer independently.

Original ZTS asset ID (64 lowercase hex) Expected service issuer ZX address Checkout title Signed-Core-bound Construct blueprint JSON (share only via trusted issuer channel) Credits to redeem (token base units) Unique opaque order reference (never sent in plaintext) ZX transaction fee Signed original ZTS redeem envelope (public data)

Accepted transaction hash

Requires a configured Signed Core and a compatible browser for local signing.

ZX Staking — Delegation / Full Node bond

All actions use the original signed bond contracts and real funded ZX State. A bond does not automatically prove validator service or Full Node mining work. Delegation unbonding takes 21 days under the current protocol; Full Node unbonding takes 14 days. Never sign for an unknown validator public key.

Participation Action

Validator ML-DSA-87 public key (5184 lowercase hex)Existing Delegation lock ID (for beginUnbond / withdraw only)

Original collateral amount (ZX; for unbond use exact bonded amount) Network fee (ZX)

No verified bond state loaded.

Original-chain signed bond envelope

Signed transaction hash

No signed action submitted.

FLM — original on-chain ZX/zUSD Convert / Redeem

Quotes come exclusively from funded reserves held in the original Signed Core. They are ZX/zUSD quotes, not independent USD collateral Oracle prices or a guaranteed price peg. Conversion and redemption use original on-chain assets and a user-approved minimum output.

Operation Amount in input asset base units (9 decimals per asset)

No on-chain quote read.

Minimum accepted output (output asset base units) Original network fee in ZX Signed original FLM action

Transaction hash

Pool must have real funded reserves; no quote exists for an unfunded pool.

zSwap/CDP — genuine on-chain collateral and debt

Original Signed Core only. An internal FLM reserve price is not a borrowing price. New debt is accepted only with a fresh independent ML-DSA-87 Oracle quorum under Genesis. Minting remains capped at 70% LTV; repay burns existing zUSD; unlock requires zero remaining debt. No public Mainnet approval is implied.