Accounts and addresses

Every KriptoNyx account has two representations of the same account: a Cosmos bech32 address and an Ethereum hex address. They are derived from one key pair and share one balance.

Format	Example shape	Used by
Ethereum	0x1234…abcd	Contracts, EVM tooling, the explorer, all APIs here
Cosmos	knyx1…	Staking transactions, Cosmos CLI tooling

Sending KNYX to the hex form and querying the bech32 form returns the same balance, because they are the same account.

Which to use

For everything in this documentation — contracts, the DEX, the bridge, the launchpad, the APIs — use the Ethereum 0x form. The bech32 form appears mainly when operating a validator with the kriptonyxd CLI.

Creating an account

Any Ethereum key works. There is nothing chain-specific about key generation.

import { ethers } from 'ethers';

const wallet = ethers.Wallet.createRandom();
console.log(wallet.address);            // 0x…
console.log(wallet.mnemonic.phrase);    // back this up offline

Back up the mnemonic

A mnemonic or private key cannot be recovered. Store it offline, before you send anything to the address.

Managed wallets

If you would rather not handle keys at all, the Platform REST API stores an encrypted key per wallet and signs on your behalf, authenticated by a password. That is a convenience for server integrations; for anything user-facing, let users hold their own keys.

Contract addresses

Contracts deploy to addresses derived the Ethereum way. The AMM additionally uses CREATE2 for pair contracts, so a pair's address is computable before it exists — see Liquidity and LP tokens.

All deployed platform contracts are listed in Contract addresses.