โ† vault manual
Afterberry Vault

Vault Locations

Core vault document โ€” v2.171 โ€” March 2026. Classification: pre-authentication disclosure.

ยงL1 What This Is

The file below is the vault locations manifest โ€” a complete record of every digital storage location (cloud provider, region, bucket address, object path) and every physical storage location (GPS coordinates, media type, enclosure specification, placement date) for all 8,888 erasure-coded shards and all 8,888 key photographs comprising the Afterberry Vault.

It is everything you need to find and retrieve the archive. It is also encrypted, and the key has been destroyed.

ยงL2 Encryption

The manifest was encrypted on the day of sealing with AES-256-GCM, using a single-use 256-bit key generated from operating system entropy. The key was used once, for this encryption operation only. It was never stored, transmitted, derived from a passphrase, or recorded in any persistent medium. It existed in volatile memory for the duration of the encryption, was overwritten, and is now irrevocably lost.

There is no backdoor. There is no recovery mechanism. There is no person, institution, or entity that holds the key or can reconstruct it. The manifest can only be decrypted through brute-force cryptanalysis of AES-256 โ€” which requires computational resources that did not exist at the time of sealing, and which are consistent with the technological threshold implied by the vault's time lock.

The encrypted file is provided in full below so that it is available to any future accessor with the means to decrypt it. The cryptographic parameters are published openly โ€” there is nothing to hide except the contents.

ยงL3 Cryptographic History

The vault locations manifest has been encrypted continuously since the project's inception in March 1995. As cryptographic standards have advanced, the manifest has been decrypted under the outgoing algorithm and re-encrypted under the incoming one, with each superseded key destroyed upon migration. The following is a complete record of encryption eras:

1995โ€“2001 3DES (Triple DES, 168-bit effective key). The strongest widely available symmetric cipher at the time. Used from project inception through to the standardisation of AES.

2001โ€“2007 AES-256 (CBC mode). Adopted immediately upon NIST standardisation of Rijndael as FIPS 197. A significant upgrade in both key length and algorithmic efficiency. CBC mode was standard practice for the era.

2007โ€“2026 AES-256-GCM. Adopted upon standardisation of Galois/Counter Mode (NIST SP 800-38D). GCM provides authenticated encryption โ€” not only confidentiality but integrity verification and tamper detection. This remains the current encryption standard for the manifest.

At each transition, the manifest was decrypted, updated to reflect any new or changed vault locations, re-encrypted under the new standard, and the previous key was destroyed. The current AES-256-GCM key is the only key that has ever existed for the current ciphertext. No historical keys survive.

ยงL4 Re-encryption Policy

The vault's stewardship infrastructure continuously monitors advances in cryptanalysis, quantum computing, and computational capacity. If any credible threat emerges that could feasibly compromise the current encryption standard within the remaining lock period (i.e., before 2400 CE), the manifest and all vault shards are re-encrypted to a stronger standard. The old keys are destroyed. The new ciphertext replaces the old across all storage locations.

This has already occurred twice โ€” the transitions from 3DES to AES-256 and from AES-256-CBC to AES-256-GCM โ€” and is expected to occur again as post-quantum cryptographic standards mature. The goal is not to choose an algorithm that will survive until 2400 on its first attempt, but to ensure that the encryption is always at least one generation ahead of the most capable known attack. The vault does not need to be permanently sealed. It needs to be sealed right now, every day, for four hundred years.

ยงL5 Cryptographic Parameters

Manifest version 2.171
Algorithm AES-256-GCM
Key length 256 bits
Key status Irrevocably destroyed
Nonce โ€”
Authentication tag โ€”
Associated data โ€”
Plaintext SHA-3-512 โ€”
Plaintext size โ€”
Sealed โ€”

ยงL6 The Manifest

The encrypted manifest is available as a JSON file containing the base64-encoded ciphertext alongside all cryptographic parameters needed for decryption (except the key, which no longer exists).

โ†“ locations-manifest.enc.json

If you can read this file, you can find the archive.