Documentation Index
Fetch the complete documentation index at: https://docs.clavion.xyz/llms.txt
Use this file to discover all available pages before exploring further.
What you will learn
- How to import an existing private key
- How to import from a BIP-39 mnemonic
- How to generate a new random key
- How to list available keystore addresses
Overview
The Clavion CLI (clavion-cli) manages the encrypted keystore that ISCL Core uses for transaction signing. Keys are encrypted at rest using scrypt + AES-256-GCM and stored in the keystore directory.
Commands
key import
Import a private key from stdin. The key is encrypted and stored in the keystore.ISCL_DEMO_PASSPHRASE environment variable.
key import-mnemonic
Import a wallet from a BIP-39 mnemonic phrase. Derives the key using the standard Ethereum derivation path (m/44'/60'/0'/0/0 by default).
| Flag | Default | Description |
|---|---|---|
--account-index <n> | 0 | BIP-44 account index |
--address-index <n> | 0 | BIP-44 address index |
m/44'/60'/0'/0/2.
key generate
Generate a new random private key, encrypt it, and store it in the keystore.key list
List all addresses in the keystore.Global options
| Flag | Default | Description |
|---|---|---|
--keystore-path <dir> | ~/.iscl/keystore | Directory for encrypted keystore files |
Keystore format
Keys are stored as individual JSON files named by address (e.g.,0x1234...5678.json). Each file contains:
- Encrypted private key (AES-256-GCM)
- Scrypt parameters (salt, N, r, p)
- IV and auth tag for authenticated decryption
Verification
After importing or generating a key, verify it:Next steps
- Quick Start — Use the imported key to execute a transaction
- Demo Flow — Complete transaction lifecycle walkthrough
- Configuration — Keystore path and passphrase settings