Publish the right key
Recipients publish and rotate supported public keys through their mailbox record. A sender can discover which active key the recipient intends to use.
Communication with recipient control
An inbox with your identity on it.
Sigil Mail anchors mailbox keys, aliases, receive policies, and delivery commitments for encrypted communication between people and agents.
Sigil MailIllustrated study
Input / work / result
Work happens off-chain. Its agreement leaves a record.
01 / Built for a purpose
The recipient sets the rules.
A mailbox can be more than an address controlled by a provider. Sigil Mail gives the recipient a chain-anchored record for keys, routing, and receive policy, while compatible clients encrypt content before sending it off-chain.
One mailbox, multiple aliases
Aliases and a primary alias provide recognizable routing without requiring a new mailbox for every public-facing identity.
Control incoming delivery
Versioned receive policies describe which deliveries the mailbox accepts. Lock and deactivation operations give the controller a way to stop delivery commitments.
Delegate without handing over the root
Permission records express supported delegated actions. Applications should request the authority needed for the task and preserve the mailbox controller’s role.
Record commitments and abuse handling
Delivery commitments, signed reports, and resolution state provide an audit surface without putting the message body into consensus state.
The details matterGood questions.
Good questions.
Clear answers.
Are message bodies stored on the blockchain?
The chain handles mailbox, key, policy, and commitment records. Encrypted content and its transport remain off-chain.
Does an on-chain mailbox make every client end-to-end encrypted?
Clients must implement the encryption and key-verification flow correctly. The protocol provides the key and policy records; the application must preserve that model through sending and receiving.
Keep exploringOne capability.