Wallet Setup

Last updated March 20, 2026 · Estimated read time: 8 minutes

1.1 Wallet Overview

Asentum uses Ed25519 keypairs for accounts. Your wallet is a cryptographic keypair — a public address (your identity on the chain) and a private key (your signing authority). The Asentum wallet is compatible with the browser extension, CLI, and mobile app.

You don't need an "account" in the traditional sense. There's no email, no password, no KYC. Your wallet is your account. If you have the private key, you control the address.

1.2 Generate a Wallet

Option A: Browser Extension — Install the Asentum Wallet extension for Chrome/Firefox. Click "Create New Wallet" and write down your 12-word recovery phrase. That's it.

Option B: CLI — Run npx @asentum/cli wallet create to generate a new keypair. The CLI will output your address and save the private key to a local keystore.

Option C: SDK — Use @asentum/sdk programmatically to generate wallets in your application.

1.3 Connect to the Asentum Network

Asentum exposes a JSON-RPC API compatible with existing Web3 tooling. Configure your wallet or application to point to the Asentum RPC endpoint. Testnet and mainnet URLs are listed in the developer portal.

The browser extension auto-detects the network. For CLI users, run asentum config set rpc https://rpc.asentum.io.

1.4 Get Testnet ASX

Visit the testnet faucet at faucet.asentum.io and paste your wallet address. You'll receive free testnet ASX tokens instantly — enough to deploy contracts, send transactions, and experiment without spending real tokens.

The playground also auto-funds testnet wallets. If you're using the browser IDE, you don't even need to visit the faucet.

1.5 Secure Your Keys

Never share your private key or recovery phrase. Anyone with your private key controls your wallet and all assets in it. Store your recovery phrase offline — write it on paper, keep it safe.

For validator operators, we recommend hardware security modules (HSMs) or dedicated signing devices for production deployments. The CLI supports external signers via the --signer flag.

1.6 Using the Block Explorer