Skip to main content

​
Wallets

AxonVault supports multiple wallet types to accommodate different use cases, from consumer apps to enterprise treasury management.

​
Wallet Hierarchy

Tenant
└── Project
    └── Wallet
        └── Account
            └── Address (per chain)
LevelDescription
TenantYour organization
ProjectApplication or environment
WalletHD wallet or single-key wallet
AccountBIP-44 account (index)
AddressChain-specific address

​
Wallet Types

​
Server Wallets

Programmatically managed wallets for backend services.
FeatureDescription
CustodyAxonVault-managed (TEE)
TypeHD only
Use CaseTreasury, automation, payments
AccessAPI Key authentication
POST /v1/server/wallets
{
  "walletName": "Treasury"
}

​
Embedded Wallets

User-facing wallets integrated into your application.
TypeDescriptionKey Storage
Cloud HDAxonVault-managed HD walletTEE
Self-Custody HDUser provides mnemonicTEE (derived)
Private Key ImportImport existing keyTEE
ExternalWalletConnect/MetaMaskExternal
ObserverWatch-onlyN/A

​
HD Wallet Structure

AxonVault uses BIP-44 compliant HD wallets: 
m / purpose' / coin_type' / account' / change / address_index
m / 44'      / 60'        / 0'       / 0      / 0
ComponentDescription
purposeAlways 44’ for BIP-44
coin_type60 (ETH), 501 (SOL), etc.
accountAccount index (0, 1, 2…)
change0 for external, 1 for change
address_indexAddress within account

​
Creating Wallets

// Create server wallet
const wallet = await api.post('/v1/server/wallets', {
  walletName: 'Treasury'
});

// Create account
const account = await api.post(`/v1/server/wallets/${wallet.walletId}/accounts`, {
  accountIndex: 0,
  accountName: 'Main'
});

// Derive address
const address = await api.post(`/v1/wallets/${wallet.walletId}/accounts/${account.accountId}/addresses/derive`, {
  chainId: 'eip155:1'
});

​
Wallet Security

  • Keys generated within TEE (Trusted Execution Environment)
  • Hardware-backed random number generation
  • Keys never leave secure enclave
  • Encrypted at rest with AES-256
  • HSM backup for disaster recovery
  • Multi-region replication
  • Tenant isolation at database level
  • Project-scoped API keys
  • User-bound embedded wallets

​
Best Practices

  1. Use HD wallets for most use cases (better key management)
  2. Create separate accounts for different purposes (trading, savings)
  3. Use observer wallets for tracking external addresses
  4. Implement policies for high-value wallets