Installation
No peer dependencies required. Users must have the Exodus browser extension installed.Basic usage
Configuration
The Exodus wallet accepts the following configuration options:Genesis ID for the Algorand network (e.g., ‘mainnet-v1.0’, ‘testnet-v1.0’).
Base64-encoded genesis hash of the Algorand network.
Array of specific account addresses to request access to.
Type definition
Features
Browser extension integration
Exodus integrates via the browser extension’s injectedwindow.algorand provider, following the ARC-0001 standard.
Multi-chain support
Exodus supports multiple blockchains. Users can manage Algorand assets alongside other cryptocurrencies.Hardware wallet support
Exodus can be used with hardware wallets like Trezor for enhanced security.Methods
connect()
Initiates connection to the Exodus browser extension. Prompts the user to approve the connection. Returns:Promise<WalletAccount[]>
disconnect()
Disconnects from Exodus. Note that the extension remains authorized until the user manually revokes access. Returns:Promise<void>
signTransactions()
Signs transactions using Exodus. Opens the extension popup for user approval. Parameters:txnGroup: Transaction or array of transactions to signindexesToSign?: Optional array of indexes to sign
Promise<(Uint8Array | null)[]>
Session management
Exodus sessions are managed by the browser extension. TheisConnected state persists as long as the extension has authorized access to your dApp.
Requirements
- Exodus browser extension must be installed
- Extension must support Algorand (available in Chromium-based browsers)
Platform support
- Web: Full support (Chromium browsers)
- Mobile: Not supported
- Desktop: Full support (via browser extension)