Skip to content

Using VaultX Receive Addresses

Overview

VaultX Receive Addresses let you accept messages without exposing your legacy Safe Message ID. Each Receive Address has its own keypair and policy controls, and the server only receives a hashed version of the address. This gives you clean, compartmentalized inboxes with rules you control and doors you can close at any time. Share a link, receive a drop, stay off the grid.

VaultX vs. legacy Safe-to-Safe

Safe-to-Safe (EyesOnly) messaging still exists for legacy workflows, but Receive Addresses are recommended for new conversations and anonymous intake.

Prerequisites

  • Sovereign or HighRisk tier: required to create and manage Receive Addresses.
  • Authenticated Safe session: you must be signed in.

All tiers can receive messages to their legacy Safe Message ID and reply via reply-only addresses; only Sovereign/HighRisk can create Receive Addresses.

Create a Receive Address

  1. Open Messaging In the Safe app, open the Messaging section.

  2. Go to Receive Addresses Select the Receive Addresses (or Addresses) tab.

  3. Create a new address Click New Receive Address.

  4. Configure address settings Set optional controls:

  5. Sender message: public note shown to senders in the Drop Client.
  6. Private label/description: internal-only label for your inbox.
  7. Usage limit: cap how many times the address can be used.
  8. Throttle: rate limit incoming drops.

  9. Attachments: allow or block file uploads.

  10. Save and generate The app generates a Receive Address and a shareable URL.

Share a Receive Address

  • Copy the address and share it directly, or
  • Share the URL to open the VaultX Drop Client with the address prefilled.

Rotate or Revoke an Address

  • Disable an address to stop new messages while keeping it visible.
  • Delete an address to revoke it entirely.
  • Create a new address for fresh intake or compartmentalization.

Where Messages Appear

Messages sent to a Receive Address appear in Messaging, grouped by address. Decryption happens client-side inside your Safe.

Operational tip

Use separate Receive Addresses for different sources or projects. This keeps conversations compartmentalized and easy to revoke.

If you are looking for anonymous sending instructions, see How to Send a VaultX Message.