Multi-chain Address Book

A multi-chain address book entry is a named record holding every address a single counterparty uses across the chains it supports. Withdrawals, sweep tasks, and policy rules can each reference the same record.

Address Book showing saved entries with their name, chain icons, address count, and last updated time

Creating an Entry

Open Address Book from the sidebar and select Create Entry.

  1. Name: how the entry appears everywhere it is selected later
  2. Description: optional context, up to 200 characters
  3. Address: paste the address into the first address block
Create Address Book Entry dialog with the name filled in and one Solana address added

Address Type Detection

Pasting an address sets its type for you. The Auto-Detect badge marks the type as read from the address, and the dropdown confirms the match with a Detected tag and a validation line below the list.

Address type dropdown listing EVM, SOL, TRON, and BTC, with SOL marked Detected and a Valid SOL address confirmation
Address Type Covers
EVM EVM-compatible networks, including Ethereum, Polygon, and BSC
SOL Solana blockchain addresses
TRON Tron blockchain addresses
BTC Bitcoin blockchain addresses

Adding Addresses to One Entry

Select Add Address to append another block. Each block carries its own type and address, and the arrows on a block move it up or down the list.

Create Address Book Entry dialog with a Solana address in the first block and an EVM address in the second, and the Add Address button highlighted

The saved entry then shows one row with a chain icon per address.

Address Book list showing a single entry holding 2 addresses with Solana and Ethereum icons

Editing and Deleting an Entry

Each row on the Address Book list carries an edit icon and a delete icon. The edit dialog matches the creation dialog and opens with the saved addresses in place. Addresses can be added, reordered, or removed there.

Where the Address Book Applies

Feature How it uses saved addresses
Withdrawal Select a saved recipient when submitting a withdrawal request
Automation Set a sweep task destination to Address Book in place of an internal wallet
Policies Evaluate rules against the Whitelisted address and Address age fields

Best Practices

  • Name entries after the counterparty, so one record stays readable as you add addresses to it
  • Keep every address for one counterparty in a single entry, so a policy rule covers all of them at once
  • Verify the full address with the counterparty through a separate channel before saving it
  • Use the description to record who owns the address and who approved adding it
  • Review entries when a counterparty rotates addresses, and delete records you no longer send to