Yes. The same features should be available under the following new names, albeit potentially with some changes to behaviors.

Actions - formerly Autotask

Monitors - formerly Sentinels

Relayers - located under the Manage section

Transaction Proposals - formerly Admin proposals

Address Book - located under the Manage section used to manage contracts, EOAs, and multisigs, formerly under the Admin section

You can use the following link to submit a request to join the beta program and get early access. Once your request has been approved, you will receive an email with instructions on how to complete the process and enable Defender 2.0 from your current Defender account.

Yes. Our team will continue to maintain Defender for the foreseeable future. We will communicate our plan as things progress, ensuring there is an upgrade path for existing Defender users.

Yes. All existing configurations for Autotask, Sentinels, etc., will be automatically imported to Defender 2.0 beta under the new features naming convention.

Not at this point. We will be collecting feedback from the beta phase and based on the data we’ll collect we will announce our plan to make Defender 2.0 generally available.

Yes, there are multiple changes to the API endpoints that will require you to update your integrations. You can visit the new API docs and SDK to learn more.

We have yet to finalize the new subscriptions. Once they are finalized we will notify existing users about the expected change.

Yes. You can switch back and forth between Defender 2.0 beta to the existing Defender version by clicking on the “Switch back to Defender” option in the navigation menu.

Yes. You can reach out and submit a support request for Defender 2.0 in the same channels as the existing Defender version. Additionally, you can submit feedback or report an issue directly from the web application using the dedicated feedback form.