The ENS.Tools action inbox already put expiry warnings, watchlist matches, marketplace activity, agent events, swaps, and messages in one wallet-scoped queue. The missing piece was delivery: an important event could be waiting even when ENS.Tools was not open. Email delivery closes that gap without creating a second alert system.
Enter an email once
Open the action inbox or Alerts & Calendar. If your ENS.Tools sign-in already has an email, we offer that address with a single button. If you previously saved an alert address, we reuse it. You only see an empty email field when neither source exists.
The address is attached to the authenticated wallet, so the same verified status follows that wallet across browsers and devices. A pending confirmation can be resent, email can be turned off, and a replacement address can be confirmed without typing the old one again.
How email delivery works
- Confirm the wallet scope. A short wallet signature opens the private product session. It is not a transaction and grants no spending permission.
- Confirm the email. We send a single-use link that expires after 24 hours. No digest is sent until the link is opened.
- Events enter the inbox first. Expiry workers, marketplace indexing, saved searches, and other ENS.Tools services write deduplicated wallet events.
- The delivery worker checks every 30 minutes. It groups up to 20 undelivered events into one digest instead of sending a separate message for every update.
- Review current state in the app. Email links open a fresh ENS.Tools page. Stored alerts never authorize a purchase, renewal, transfer, or other transaction.
Changing or stopping email
Every digest includes a one-click unsubscribe link. Turning email off does not delete your in-app history, mark anything as read, or change ENS state. If you switch addresses, the old verified address keeps working until the replacement is confirmed, avoiding a silent gap in delivery.
What operators need to configure
Production delivery uses Resend. The server needs a RESEND_API_KEY and a verified NOTIFY_FROM_EMAIL sender. Email addresses remain behind the service boundary; the browser receives only the contact associated with its authenticated wallet. The scheduled worker remains inactive when the provider key is absent, and the interface reports that state instead of pretending a confirmation was sent.
Turn it on
Visit your action inbox, choose the suggested address or enter one, and open the confirmation message. That is the only email-entry step. From then on, the inbox is the source of truth and email is simply a delivery channel for the events already waiting there.