WEB WALLET

Send and receive KRNX from the browser.

A self-custodial wallet for native KRNX on the Kronex testnet, at wallet.kronex.network. It runs entirely in your browser: there is no server holding keys, no account to sign up for, and nothing to install.

testnet Testnet only, chain ID 5768. The wallet moves testnet KRNX, which has no value. Mainnet has not launched, and the wallet does not connect to it.

01 · WHAT IT DOES

Native KRNX, and nothing else

The first release does one thing well. Everything it does is listed here; everything it does not do is in section 05.

Create a wallet
A new account backed by a recovery phrase, generated in the browser from its secure random source. You see the phrase once and confirm selected words before going on.
Import a wallet
From a recovery phrase, or from a Geth-compatible encrypted keystore JSON and its password. Both are checked before the account is added.
Export a wallet
A local account can be downloaded as an encrypted Geth JSON file at any time, for a backup or for use with a node.
Connect MetaMask
MetaMask acts as an external signer. The wallet sees the public address and signing results, never the key. It checks chain 5768 and offers the add-network prompt if you are elsewhere.
Several wallets at once
Local accounts and a connected MetaMask account sit in one list, each with its own name, and you switch between them.
Send and receive
Balance from the RPC, fee estimated before you confirm, a review screen with amount, fee, total, sender and recipient, then a link to the explorer for the result. Receive shows the full address and a QR code.
Activity
The address's transactions, read from the testnet explorer. If the explorer is down, the wallet keeps working and says activity is unavailable.

02 · WHERE THE KEYS ARE

On your device, two ways

You choose how a local account is kept the moment you create or import it.

Session onlyEncrypted, persistent
Where the key livesIn memory, for this tabEncrypted Geth JSON in the browser's IndexedDB
What is storedNothingThe encrypted keystore, a name, the public address, dates
PasswordNoneSet by you; never stored
Closing the tabRemoves the walletKeeps it; unlock with the password
Auto-lock—After 15 minutes without activity; a manual Lock is always there

Passwords, recovery phrases and unencrypted private keys are never written to storage in either mode. A locked account still shows and copies its public address; signing and export need it unlocked.

There is no backend. The wallet talks to two public endpoints, rpc-testnet.kronex.network for balances, fees and broadcasting and the testnet explorer for history, and to nothing else. It ships without analytics.

03 · FOR MINERS

Where the reward lands

A block or workshare reward is paid to whatever Kronex address the miner or pool names. The wallet is the quickest way to have one.

  1. 01Create a wallet, or import the keystore your node already uses — krnxd keystores are Geth format and open as they are.
  2. 02Copy the address from Receive, where it is shown in full with a QR code, into the miner's reward flag or the pool's payout field.
  3. 03Watch it credit: the balance updates from the RPC, and the activity list shows each payout with a link to the explorer, where the block or workshare that earned it is public.

Mining on Kronex →Rewards

04 · WHAT IT CHECKS

Before anything is signed

The safeguards are ordinary and they are all on.

  • chain ID verified before signing
  • checksummed address parsing
  • balance and fee checked before review
  • review screen before broadcast
  • no secrets in URLs, logs or errors
  • bounded retries, explicit timeouts

If the RPC is unreachable the wallet still shows your accounts and says the balance is unavailable. If MetaMask is missing it says how to get it and leaves the local options in place. A pending transaction that outlives its timeout keeps its hash and its explorer link.

05 · WHAT IT IS NOT

Outside the first release

Stated so nobody looks for it.

  • ERC-20 tokens
  • mainnet
  • other EVM networks
  • WalletConnect
  • hardware wallets
  • swaps
  • staking
  • dApp browser
  • contract interaction
  • dark theme

One address per wallet entry, on the standard derivation path m/44'/60'/0'/0/0. The wallet does not derive a set of addresses from one phrase.

06 · WHAT EXISTS TODAY

What exists today

the walletwallet.kronex.network · static site, served by nginxTestnet
the networkKronex testnet, chain 5768, rpc-testnet.kronex.networkTestnet
the explorerexplorer-testnet.kronex.network, for activity and receiptsTestnet

The wallet is Vue 3, TypeScript and ethers, built to static files. Its repository is not public yet; when it is, this page will link it.

Open the walletBlock explorer