Configuration
The CLI works with zero configuration out of the box - it targets the live network (https://rpc.bwick.fun / https://rest.bwick.fun). Everything below is optional, controlled entirely through environment variables.
Environment variables
| Variable | Purpose | Default |
|---|
BWICK_RPC | Chain RPC endpoint | https://rpc.bwick.fun |
BWICK_REST | REST endpoint | https://rest.bwick.fun |
BWICK_CHAIN_ID | Chain id | bwick-1 |
BWICK_PASSWORD | Keystore password (non-interactive) | - |
BWICK_MNEMONIC | Mnemonic for keys import (non-interactive) | - |
BWICK_SOLANA_RPC | Solana RPC (for bridging) | public mainnet RPC |
Point at a different endpoint
export BWICK_RPC=https://rpc.bwick.fun
export BWICK_REST=https://rest.bwick.fun
bwick status
BWICK_RPC=http://localhost:26657 bwick status
Scripting (non-interactive)
Commands that touch a wallet normally prompt for a password. For automation, supply it through the environment instead so nothing blocks on a prompt:
BWICK_PASSWORD='…' bwick send --to bwick1… --amount 5 --from main --json
keys import can likewise take the mnemonic from BWICK_MNEMONIC:
BWICK_MNEMONIC='word1 word2 …' BWICK_PASSWORD='…' bwick keys import main
Passing secrets via environment variables can leak them into shell history and process listings. Prefer the interactive prompts for day-to-day use; reserve the env vars for controlled, ephemeral automation.
Where data lives
Wallets are stored as encrypted JSON keystores (scrypt + AES-256-GCM) under:
Your password never leaves your machine and is never written to disk.
