AWS guarantees relevant to this relay

Checked against AWS documentation on September 12, 2026 (Pacific).

Enclave confidentiality and identity

Nitro isolates the enclave's CPU and memory from the parent instance, including its administrators. Signed attestation identifies the measured enclave and can bind its public key. This supports our assumption that AWS is trusted while the account owner and host are not. AWS does not thereby prove our application code safe, enforce our RandomX delay, or force an operator to keep the enclave alive. AWS Nitro documentation.

Stored-object durability and visibility

S3 Standard is designed for 99.999999999% annual durability and 99.99% annual availability, storing data across at least three Availability Zones within the region. It is designed to survive an entire Availability Zone's loss. These are engineering design targets, not an absolute impossibility of loss. AWS durability documentation.

After a successful S3 PUT, subsequent GET and LIST requests reflect the write; individual object updates are atomic. This does not make a set of multiple artifact uploads one transaction. Our host acknowledgement happens before its asynchronous S3 upload, so the relay's response alone does not establish that S3 has accepted the object. AWS consistency model.

Thirty-day retention

The live archive default is 30-day COMPLIANCE Object Lock. A protected version cannot be overwritten or permanently deleted by an account user, including root; its retention cannot be shortened or changed to governance mode. The protection is per version: new versions and delete markers can hide it from ordinary unversioned reads. AWS explicitly documents deletion of the associated AWS account as an exception. Public-read permissions and future retention defaults remain under account control; Object Lock does not force continued public access. AWS Object Lock documentation, access controls.

The observed production record has SSE-S3 encryption (AES256) and COMPLIANCE retention until October 12, 2026. This S3 encryption is separate from our enclave's time-locked ciphertext. It does not determine when our epoch key is recovered.

Contractual availability

S3's SLA offers eligible service credits for outages; the S3 Standard credit threshold begins below 99.9% monthly uptime under its defined metric and exclusions. That differs from the 99.99% annual design target. It is not a promise of uninterrupted public availability or eventual publication of our recovered keys. Amazon S3 SLA.

AWS therefore supplies isolation, attestation and storage primitives. Running solvers, publishing recovered keys/plaintext and maintaining independent public copies remain responsibilities of this project and its participants.