keep-mail

1. Email or forward anything to that address.
2. The message is minted as a 1/1 on Base Sepolia, stored exactly as it arrived.
3. A reply comes back with a link that reads it out of the chain.

Messages up to 15,000 bytes are stored whole. Larger ones are sealed: the chain keeps their hash, because a shortened email is a worse record than an honest receipt. Auto-replies and mailing list mail are ignored, which is how mail loops start.

Every email you send is signed by the domain it came from. Gmail signs yours with a key published in DNS, covering the sender, the subject, the date and the body. That signature is what makes an email evidence rather than an assertion.

keep-mail checks the signature the moment a message arrives, while the sending domain's key is certainly still published, and records the verdict on chain alongside the message stored byte for byte. Nothing is reformatted, because any edit destroys the signature.

So a token marked verified is not our word for it. Download the original from any kept message and run it through a DKIM validator yourself. If it checks out, that domain signed those exact words on that date, whatever happens to this service.

Not every message can be verified. Some arrive unsigned, and some signatures do not check out for reasons outside anyone's control. Those are recorded honestly as unverified rather than quietly presented as proof. A verified message proves what was sent and when. It does not prove the sender meant it, and it is not legal advice. 5 of the 6 messages below are verified.

Email a picture to the address and the picture becomes the artwork. Not a card about it, the image itself.

It works because the message is stored exactly as it arrived, attachment and all, so the image is already on chain inside the email. Nothing is pinned and nothing is hosted: the bytes come back out of the same field the text does. The email around it becomes the provenance, and if it is signed, that provenance is verifiable.

The whole message has to fit in 15,000 bytes, which after mail encoding means a picture of roughly ten kilobytes. Anything larger takes the sealed lane: the chain keeps its hash and the image is not recoverable from chain data alone. Small graphics work today. Photographs need pinning, which is not wired up.

If you only want an image on chain and do not need the email around it, the ABX CLI already does that in one command and is the faster path.