Addresses and contracts
The address book helps people review targets and select addresses as contract arguments. Adding an ABI turns an address into a callable contract capability.
Add a known address
Section titled “Add a known address”- Open Address book.
- Select Add entry.
- Enter a name and EVM address.
- Choose the relevant chains.
- Save the entry.
Use names that describe purpose, not only ownership. Always compare the full address before a sensitive transaction.
Add a contract
Section titled “Add a contract”- Start from the deployed contract’s chain and address.
- Confirm that code exists at that address.
- Supply a strongly typed JSON ABI or choose an available Sourcify candidate.
- Review whether the candidate describes the proxy or its implementation.
- Save the contract capability.
txcast stores the ABI source and a digest. A second registration with the same normalized ABI is unchanged; a different ABI conflicts instead of silently replacing the saved definition.
Safes in the address book
Section titled “Safes in the address book”A Safe may appear as a known address and as an execution account. These records serve different jobs: the address book supports identification and targeting, while the execution registry authorizes workflow steps to execute from the Safe.
Changes do not rewrite history
Section titled “Changes do not rewrite history”Editing a display name or enriching an address with an ABI does not change an already saved workflow revision or published run. Review and save a new workflow revision when registry changes affect future calls.