Wallet Integration
Last updated March 20, 2026 ยท Estimated read time: 8 minutes
1.1 Wallet Options
Asentum supports multiple wallet types: browser extension (Chrome/Firefox), CLI keystore, SDK programmatic wallets, and hardware signers. All use Ed25519 cryptography. Choose the option that fits your use case.
1.2 Browser Extension
The Asentum Wallet browser extension injects a provider object into web pages, similar to MetaMask. dApps can request wallet connection, prompt transaction signing, and query account balances. Install from the Chrome Web Store or Firefox Add-ons.
1.3 SDK Wallet Integration
Use @asentum/sdk to connect to wallets in your application. The SDK provides connectWallet() for browser extension detection, createWallet() for programmatic generation, and importWallet(privateKey) for existing keypairs.
1.4 Sending Transactions
Construct a transaction object with to, value, and optional data fields. The SDK handles nonce management, gas estimation, and signing automatically. Transactions confirm in ~3 seconds.
1.5 Message Signing
Sign arbitrary messages for authentication, off-chain verification, or multi-sig workflows. Use wallet.signMessage(message) to produce an Ed25519 signature that anyone can verify against your public address.