history repeats itself, as usual

What about “chained events” improves anything compared to “check all my relays first, update after?” Why would you offload *your* responsibility to a relay? Both of them rely on your relays to detect any issues. However, check-before-write prevents damage before it occurs, while chained events only prevent damage after. That means the app has to sign more events to reconcile instead of doing it right just from the start. If the app discovers a really old version that diverged, it can’t do anything either except to discard it. Compared to chained events, just being competent and reading the event before you write alleviates the problems with losing your list.

"More replicas" is not the solution to scaling relays

gm nostriches

Maple still has not addressed the problem that their product’s “encrypted blobs” CAN be decrypted outside the TEE. While it is decrypted only in the TEE *during normal operation*, MapleAI can be easily compelled to decrypt the blobs for law enforcement. This can be done without any technical barriers or challenges. The root key that is used to protect all data of the enclave is *outside the enclave*, in AWS KMS. View quoted note →

gm nostriches