​
Accounts

bwickchain uses standard account types with the bwick address prefix.

​
Address Formats

TypePrefixExample
Accountbwick1bwick1abc123def456ghi789jkl012mno345pqr678stu
Validatorbwickvaloper1bwickvaloper1abc123def456ghi789jkl012mno345pqr678stu
Consensusbwickvalcons1bwickvalcons1abc123def456ghi789jkl012mno345pqr678stu

​
Account Derivation

bwickchain uses the standard HD path for key derivation: 
m/44'/118'/0'/0/0
LevelValueMeaning
Purpose44’BIP44 standard
Coin Type118’Standard
Account0’First account
Change0External chain
Index0First address
The coin type 118 is the standard coin type. This ensures compatibility with compatible wallets like Keplr.

​
Key Generation

​
Generate New Key

bwick keys generate mykey
Output: 
Generated new keypair: mykey

Address: bwick1qwertyuiopasdfghjklzxcvbnm12345678
Mnemonic (save this securely):
word1 word2 word3 word4 word5 word6 word7 word8 word9 word10 word11 word12

WARNING: Write down your mnemonic phrase and store it securely.

​
Import Existing Key

bwick keys import mykey --mnemonic "word1 word2 word3 ... word12"
Or interactively: 
bwick keys import mykey
# Enter your 12 or 24 word mnemonic:

​
List Keys

bwick keys list
Output: 
NAME      ADDRESS
mykey     bwick1qwertyuiopasdfghjklzxcvbnm12345678
alice     bwick1aliceaddress...
bob       bwick1bobaddress...

​
Export Key

bwick keys export mykey
This exports an armored ASCII format that can be imported into other wallets.

​
Test Accounts

The local development network (bwick localnet) includes pre-funded test accounts:
NameBalanceMnemonic
alice1,000,000 BWICKabandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about
bob500,000 BWICKStandard test mnemonic
Never use test mnemonics for real funds. These are well-known phrases used only for development.

​
Keyring Backends

The CLI supports multiple storage backends for private keys: Uses the operating system’s secure keychain:
  • macOS: Keychain
  • Windows: Credential Manager
  • Linux: Secret Service (GNOME Keyring, KWallet)
bwick config set keyring-backend os

​
File Backend

Stores keys in an encrypted file at ~/.bwick/keyring-file/: 
bwick config set keyring-backend file
File backend requires a passphrase for each operation.

​
Test Backend

Stores keys unencrypted (development only): 
bwick config set keyring-backend test
Never use test backend for real funds. Keys are stored in plain text.

​
Account Operations

​
Check Balance

# By address
bwick balance bwick1abc123...

# By key name
bwick balance --key mykey

​
View Transaction History

bwick tx history bwick1abc123...
# or
bwick tx history --key mykey

​
Using bwickd

For advanced operations, use the chain daemon: 
# List all keys
bwickd keys list --home ~/.bwick --keyring-backend os

# Show specific key
bwickd keys show mykey --home ~/.bwick --keyring-backend os

# Get account info from chain
bwickd query auth account bwick1abc123... --node https://rpc.bwick.fun

​
Account Types

​
Standard Account

Regular user accounts created with bwick keys generate. 
{
  "@type": "/cosmos.auth.v1beta1.BaseAccount",
  "address": "bwick1...",
  "pub_key": {
    "@type": "/cosmos.crypto.secp256k1.PubKey",
    "key": "..."
  },
  "account_number": "42",
  "sequence": "7"
}

​
Module Account

System accounts owned by chain modules (not user-controlled):
ModuleAddressPermissions
fee_collectorbwick1...None (receives fees)
distributionbwick1...None (holds rewards)
bonded_tokens_poolbwick1...Burner, Staking
not_bonded_tokens_poolbwick1...Burner, Staking
govbwick1...Burner
wasmbwick1...Burner

​
Contract Account

Accounts created when instantiating CosmWasm contracts: 
bwick program info bwick1contractaddress...

​
Security Best Practices

  • Write it on paper (not digital)
  • Store in multiple secure locations
  • Consider metal backup for fire/water resistance
  • Never share with anyone
For significant holdings, use Ledger or similar hardware wallets support.
Always double-check the first and last 4-6 characters of addresses before sending.
Keep real funds on separate keys from development/testing activities.