@exodus/address-provider

This module derives addresses for assets from different wallet accounts. Addresses for software wallet accounts are encoded public keys that are derived from the seed using Keychain, whereas hardware wallet accounts use the public keys stored in the public-key-store.

flowchart LR
    A[AddressProvider] --> B[PublicKeyProvider]
    B -->|software| D[Keychain]
    B -->|hardware| E[PublicKeyStore]

Address derivation can be pretty expensive on certain platforms (*cough, mobile*). So this package also includes a simple walletAccount and bip32 path based cache.

Install

yarn add @exodus/address-provider

Usage

This feature is designed to be used together with @exodus/headless. See using the sdk.

Play with it

1. Open the playground https://exodus-hydra.pages.dev/features/address-provider
2. Try out some methods via the UI. These correspond 1:1 with the exodus.addressProvider API.
3. Run await exodus.addressProvider.getReceiveAddress({ walletAccount: 'exodus_0', assetName: 'bitcoin' }) in the Dev Tools Console.

API Side

See using the sdk for more details on how features plug into the SDK and the API interface in the type declaration.

const address = await exodus.addressProvider.getAddress({
  purpose: 44,
  assetName: 'bitcoin',
  walletAccount: 'exodus_0',
  chainIndex: 0,
  addressIndex: 0,
})

const receiveAddress = await exodus.addressProvider.getReceiveAddress({
  assetName: 'bitcoin',
  walletAccount: 'exodus_0',
})

const unusedReceiveAddress = await exodus.addressProvider.getReceiveAddress({
  assetName: 'bitcoin',
  walletAccount: 'exodus_0',
  multiAddressMode: true,
})

If you're building a feature that requires the wallet's addresses, add a dependency on the addressProvider module, which provides almost the same API as the external exodus.addressProvider API (caveat: the module expects WalletAccount instances, while the API expects WalletAccount names like 'exodus_0').

External Wallet Addresses

For wallet accounts that don't derive addresses from a seed (e.g. smart contract wallets), the address provider resolves addresses from the externalWalletAddressesAtom. Register addresses via the walletAccounts module:

await exodus.walletAccounts.setExternalAddress({
  walletAccount: 'polymarket_0',
  assetName: 'matic',
  address: '0x1234...abcd',
})

// The address provider now returns this address for the external wallet account
const address = await exodus.addressProvider.getReceiveAddress({
  assetName: 'matic',
  walletAccount: 'polymarket_0',
})

// To remove
await exodus.walletAccounts.removeExternalAddress({
  walletAccount: 'polymarket_0',
  assetName: 'matic',
})

This only applies to wallet accounts where isExternal is true. For all other accounts, normal key derivation is used.

UI Side

See using the sdk for more details on basic UI-side setup.

import exodus from '~/ui/exodus'

const MyComponent = () => {
  const { loading, value: receiveAddress } = useAsync(
    exodus.addressProvider.getReceiveAddress({ walletAccount: 'exodus_0', assetName: 'bitcoin' })
  )

  return loading ? <Text>Loading...</Text> : <Text>Your address: {receiveAddress}</Text>
}

Mocking Addresses

Occasionally you may want to simulate another wallet for which you don't have the seed or private keys. You can do this by mocking at the address level here or at the xpub/public key level in public-key-provider

Mock an address by providing all the parameters that would normally be used to derive it:

exodus.debug.addressProvider.mockAddress({
  walletAccount: 'exodus_0',
  assetName: 'ethereum',
  address: '<address>',
  purpose: 44,
  chainIndex: 0,
  addressIndex: 0,
})

Mock multiple addresses by only a subset of the parameters:

exodus.debug.addressProvider.mockAddress({
  walletAccount: 'exodus_0',
  assetName: 'bitcoin',
  purpose: 44,
  address: '<address>',
})

This would result in mocking all change/receive chain addresses with the same address.

To clear all mocked addresses, call exodus.debug.addressProvider.clear().