Migrating from Defender legacy

On June 1st 2024, you will no longer have access to Defender legacy UI and API.

With the announcement of Defender general availability, we are deprecating Defender legacy (also known as legacy) in favor of Defender. To make the transition as smooth as possible, we’ve developed an onboarding assistant to help you with just a few clicks. To use the assistant, click here, log in with our account, and follow the steps. You can find the FAQ here.

Differences

Features from Defender legacy have been reorganized and improved in Defender. All of your created assets will be completely available when migrating.

Tenant-wide pages → Manage

Tenant-wide pages in the Defender legacy dropdown menu can now be found under the Manage tab.

User managament is now called Team Members
Team API Keys and Fireblocks API Keys are now under API Keys

Learn more here.

Defender legacy

Defender

Admin / Add Contract → Manage / Address Book

Now, you can add smart contracts to use across the platform via the Address Book, which is accesible under the Manage tab. Learn more here.

Defender legacy

Defender

Admin / Create Safe → Deprecated

The ability of creating a Safe smart contract via Defender is not available in Defender. We recommend using the Safe interface to create a Safe, and then import it to Defender using the Address Book.

Defender legacy

Admin / Create Timelock → Deprecated

The ability of creating a Timelock smart contract via Defender is not available in Defender. We recommend using the OpenZeppelin Contracts 5.0 TimelockController implementation with a development framework, like Hardhat or Foundry, to deploy it. You can then import it to Defender using the Address Book. Learn more here.

Defender legacy

Admin / Add Proposal → Actions / Transaction Proposals

In Defender, you can now use Transactions Proposals within Actions to send transactions via Approval Processes, like Safes, EOAs, Relayers, and more. Learn more here.