Kalyx

Docs

Wallet

The wallet lives on the explorer, at the dashboard. It creates a spending account in the browser. That account can receive test coins and send them. It is not the key that proposes blocks.

The seed stays in the tab. Refreshing the page forgets it. The server does not receive the seed, the passphrase, or the opened key.

Create one

  1. Choose New wallet.
  2. Set a passphrase of at least 8 characters, with a letter and a number, and type it again.
  3. The page builds the account and encrypts a file named kalyx-wallet.json. Encryption uses argon2id. It can take several seconds. The button stays disabled until it finishes.
  4. Keep the file. Without the file and the same passphrase, the account cannot be opened on a later visit.

The address on screen is KAL and 40 hex characters. Hand that address to whoever is paying you. Do not hand them the file, the passphrase, or the seed.

Open one

Choose Open wallet. You can open the file with its passphrase, or enter the raw seed as hex. The seed is 51 bytes, which is 102 hex characters after the 0x. A wrong passphrase does not open the file. There is no word list. Guessing nearby words is not a recovery method, because this account was not made from words.

Once it is open

  • Receive. The address is the whole instruction. Test coins from the faucet arrive there.
  • Send. You name the recipient, the amount, and the fee fields the page asks for. The signature spends one XMSS leaf. That leaf cannot be used again. Read the account page before you send twice from two copies of the same wallet.
  • Private. Shield moves public KALYX into a note. Pay privately moves the whole note. Unshield returns it to this account. The rules, the limits, and the steps are on the private payments page.
  • Transfers. The page lists what this tab has sent and received.
  • Save wallet file. You can write a new encrypted file. It still needs a passphrase.
  • Close. The tab forgets the seed. The file, if you saved it, remains on your machine.

Contracts

The contracts page is the writing rule. On the wallet, Write compiles one Solidity file in this browser. Contract publishes bytecode that starts with 0x. Leave the amount at 0 unless creation should also send coins. A person check runs. The seed stays in the tab. The transaction has no recipient. When the node has a receipt, the transaction page shows the new contract address.

Choose Call to talk to a contract that already exists. Read asks a question and does not spend a signature. Send call spends one signature, and any KALYX you put in the amount. The same deploy can start at Contracts on the testnet, which builds the call data from the function arguments.

A project website uses the same public explorer. It can ask for code at an address, and it can ask a contract a question, without the node’s RPC being opened. A change still has to be signed in a wallet.

What this account cannot do

It cannot propose a block. A validator key is ML-DSA-87, created on a machine you run, signed for fork version 0x10000038, and backed by 40,000 KALYX. The steps are on the validator page. Leave that key out of this browser.

Sending also asks for a person check. The check is there so a script cannot drain the page. It is not a backup of your seed.