Backing up civilization from seed vaults to the Moon

Backing Up Civilization, From Seed Vaults and Arctic Mines to the Moon and the Permaweb

Last checked: October 2026.

In September 2015, a war reached all the way into a mountain in the Arctic. The genebank of the International Center for Agricultural Research in the Dry Areas (ICARDA) near Aleppo, Syria, could no longer grow and ship its seeds, so ICARDA asked for some of them back from the Svalbard Global Seed Vault. It was the first withdrawal in the history of the vault, and it worked. This page tells that story and several stranger ones, including a library that crashed on the Moon, and then turns them into a plan anyone can use to keep a life of work readable in the year 2126.

The page serves four goals of this wiki. It serves abundance and post-scarcity, because knowledge is an abundant commons only if it survives. It serves freedom technology and censorship resistance, because a record that depends on one institution can be switched off. It serves longevity and futurism, because a longer life is worth more in a civilization that remembers. It also addresses a common problem in living: losing a thesis, a family archive, or a business on one dead drive is a real and avoidable loss.

Five backups, five lessons

The seed vault that paid off

At the Svalbard Global Seed Vault, seeds sit in airtight aluminum pouches inside a frozen mountain, kept at a constant minus 18 degrees Celsius. The surrounding permafrost would keep them cold for a long time even if the cooling plant failed. Deposits are free and follow so called black box conditions: the vault never opens the boxes, the depositing genebank keeps ownership, and only that genebank can ask for its seeds back. Norway funds the facility, NordGen runs it, and the Crop Trust helps pay for operations.

ICARDA had copied more than 80 percent of its collection to Svalbard before the conflict made its Aleppo work impossible. In 2015 it withdrew 128 boxes holding 38,073 seed samples. Wheat, barley, lentil, and chickpea went to Morocco; forages, faba beans, and wild relatives of cereals went to Lebanon. Most of the seed arrived in good condition and was sown that same autumn to rebuild working collections, with a portion to be returned to the vault. The lesson: a backup only matters if it is far away, owned by the right party, and actually restorable.

Source code on film in a coal mine

About a mile from the seed vault, in a decommissioned coal mine 250 meters deep in permafrost, sits the Arctic World Archive. On 2 February 2020, GitHub took a snapshot of every active public repository, 21 terabytes in all, and wrote it to 186 reels of archival film. Most data is stored as compressed QR codes, and every reel carries a human readable index and guide explaining how to recover it. The program describes the vault as built to last 1,000 years. The code survives as pictures on film, and the guide on each reel is what turns those pictures back into software.

A library you read with a microscope

The Rosetta Disk, a prototype for the 10,000 year library of the Long Now Foundation, is a three inch disk with more than 13,000 microetched pages documenting over 1,500 human languages. The outer text is readable by eye and spirals down to nano scale, telling the finder, in effect, to get a magnifier because there is more. Because each page is a physical image rather than a file, the project notes, there is no platform or format dependency; reading it requires only optical magnification. The lesson is decoding instructions. The original Rosetta Stone was readable because it repeated one text in several scripts.

A library on the Moon, with tardigrades

In April 2019, the privately funded Beresheet lander crashed while trying to land in the Sea of Serenity. Aboard was the Lunar Library of the Arch Mission Foundation: 25 nickel layers, each a few microns thick, about the size of a DVD. The first four layers hold roughly 60,000 page images, including language primers and keys for decoding the other 21 layers, which contain nearly all of the English Wikipedia and thousands of books. At the last minute the team also embedded human DNA samples and dehydrated tardigrades in resin between the layers, and stuck a few thousand more tardigrades to tape on the outside. The foundation believed the library likely survived the impact largely intact; whether any tardigrades survived was unknown at the time, and later laboratory impact tests suggested they probably did not. The same report described a research direction: storing data in synthetic DNA, which can be copied many times and packs terabytes into a small vial.

A record with the instructions on the cover

The Voyager Golden Records, launched in 1977, are 12 inch gold plated copper disks carrying images, natural sounds, music from many cultures, and spoken greetings in 55 languages. The cover is the clever part. It shows how to play the record, states the rotation time in binary using a unit based on a hydrogen atom transition, locates the Sun relative to 14 pulsars, and carries a sample of uranium-238 that works as a clock for anyone who wants to know how long the record has been travelling. Few messages have ever been designed for a reader with less shared context.

The single point of failure on the web

Many people treat the Internet Archive as the backup of the web. In October 2024 a breach exposed records for 31 million accounts, the site was defaced, and a denial of service attack took it offline. A month earlier, a federal appeals court had ruled against its digital lending of 127 books in a suit brought by four publishers. Whatever one thinks of each dispute, the episode showed that a precious public record can rest on one organization, one legal team, and one set of servers. The companion page on link rot covers how citations decay; this page asks what it takes to make something last.

Permanent storage as an endowment

Arweave approaches the funding problem directly. An uploader pays once, up front, into a storage endowment sized for 200 years of replicated storage at current prices. Miners are paid from the endowment over time as they prove they still hold the data, and the design assumes that storage costs fall by at least 0.5 percent per year. Each node operator may also choose which data it stores and serves. This network of stored pages is often called the permaweb; see Permaweb basics. Its long term survival depends on assumptions about future costs and continued participation, so it is best treated as one copy among several.

What the archivists learned

• Copies in many places. ICARDA lost access to Aleppo, not to its seeds, because a duplicate sat in another country.
• Durable media. Film, nickel, and gold plated copper outlast disks that need power and maintenance.
• Readable formats and instructions. Every successful project above ships a guide with the data.
• Independence from one institution. The Internet Archive episode shows the risk; black box ownership at Svalbard shows a fix.
• Someone must still care and pay. The vault has a government budget, Arweave has an endowment, and every other plan needs a named successor.

A century plan for one person or a small project

1. Keep three copies on at least two kinds of media, with one copy in a different city or with a trusted relative. See Local-first software.
2. Convert to open, boring formats: plain text, Markdown, CSV, PDF/A, PNG, and FLAC. Avoid formats that need one company to open.
3. Write a file called README.txt that explains what the collection is, how it is organized, what each format is, and whom to contact.
4. Record a SHA-256 checksum for every file in a text manifest, and recheck it each year. See content hashing.
5. Mirror code and notes to a Git repository; see Git mirrors.
6. For public work that should outlive you, add a permanent copy, after checking publish gates before permanence so nothing private becomes permanent by mistake.
7. Name a successor in writing, give them access instructions, and print one page of instructions to keep with your important papers.

How an AI agent can help, with a human in charge

An agent can audit a folder for proprietary or obsolete formats and propose conversions, compute and verify checksums against the manifest, scan notes and wiki pages for dead links and suggest archived copies, and draft the README for the owner to correct. It should not delete originals, publish anything permanently, or share private files without explicit approval. The person decides what matters; the agent does the tedious checking.

Discussion questions, essay ideas, and learning related AI prompt ideas

• Why did ICARDA succeed in recovering its seeds, and which of its choices could an individual copy for digital files?
• Is a Rosetta style printed guide more important than the durability of the medium? Defend your answer with one example.
• Write an essay comparing the Voyager cover and the README.txt of a software project as instructions for a stranger.
• Write an essay on whether pay once permanent storage solves the problem of someone still caring and paying, or only moves it.
• Ask an AI system to review a list of my file types and flag which ones may be hard to open in 50 years, with open alternatives.
• Ask an AI system to explain SHA-256 checksums in plain language and walk me through verifying one file.
• Ask an AI system to draft a one page README for a family photo archive, then quiz me on what is missing.

See also

• Link rot and reliable knowledge
• Permaweb basics
• Permanent decentralized wiki design
• How content hashing works
• Local-first software
• Right to repair and durable abundance
• Longevity escape velocity
• Post-scarcity economy