XP: 0 ← MISSIONS QUESTS ↗ CHAT ↗
GUARDIAN · ARCHIVE OPERATIONS
OPERATION: FIRST PIN
Every copy of a document is a vote for historical record. Governments can take down websites. They cannot take down mathematics. This mission walks you through becoming a mirror — in under 10 minutes, with free tools, no technical experience required.
—
TOTAL PINS CLAIMED
—
MEMBERS CONTRIBUTING
FREE
MINIMUM COST
<10 min
TIME TO FIRST PIN
01 CHOOSE YOUR WEAPON
How do you want to pin? All options below are free for getting started. Easier = more dependent on a company. More control = runs on your machine.
02 PICK A MISSION ARCHIVE
These are real documents that need more mirrors. Pick one — or pin them all. Each pin you claim adds to the community counter.
03 EXECUTE THE PIN
Follow the steps for your chosen method. The CID (Content Identifier) is the document's permanent address — it never changes.
← Complete steps 01 and 02 first: choose your method and select a mission archive.
04 VERIFY + CLAIM YOUR XP
Verify the pin is live, then claim your XP. This records your contribution to the Guardian Network's live counter.
CONFIRM YOUR PIN
Select an archive above to see the verification URL.
LIVE GUARDIAN PINS
Connecting to P2P network…
ABOUT IPFS PINNING
What is pinning? IPFS nodes automatically discard files that aren't "pinned" — pinning tells your node (or a service) to keep a file indefinitely. Each additional pinner is an independent mirror in a different jurisdiction.

What is a CID? A Content Identifier is a cryptographic fingerprint of a file. The same file always produces the same CID. If anyone changes even one byte, the CID changes — making tampering detectable and impossible to hide.

Why not just save a URL? URLs can return 404. Domain names can be seized. Hosting providers can delete content under legal pressure. A CID addresses content by what it is, not where it lives. 200 mirrors across 40 countries with the same CID = effectively uncensorable.

Privacy note: Running your own IPFS node makes your IP address visible to others fetching the same content. If this is a concern for your threat model, use a pinning service (Pinata, web3.storage) rather than a local node.