Protocol

Copies and checks

Three providers keep one full copy each. The keeper reads every copy back once a day and rebuilds any that stops answering.

The same bytes everywhere

Your browser packs the file into a CAR (a content-addressed archive of its blocks) with IPFS’s unixfs-v1-2025 profile. Each provider gets that CAR, or is asked to fetch the CID from the copies already online, so all three hold the root CID your browser showed you.

Providers

• Filebase: the CAR is imported over its S3 API, and the root it reports is checked against yours.
• Pinata: the CAR goes in through its upload API as it is.
• Any IPFS pinning service on the standard Pinning Service API: asked to pin the CID. Repairs work the same way.

Checks

A copy counts as there when the provider’s own gateway returns the root block and its bytes hash to the CID: a check of the bytes, not of the provider’s word. Every check is recorded, and each day’s are rooted on chain in a Checkpoint.

Repairs

Three missed checks in a row and a copy counts as lost. The keeper reads the whole file back from a copy that still answers, checks every block and puts it with a standby provider in the same slot. The deed shows the move; the CID never changes.

Renewals

30 days before a deed’s year ends, the keeper asks the program to pay the next year from the vault, bringing dollars back from Kamino first if the vault is short.