@guardianchain/cap

Cap your work. Prove it existed. No cap.

The GC-1 Cap CLI seals documents, code, and any digital artifact with blockchain-anchored cryptographic proof. Free tier anchors to 1 chain. Pro tier anchors to 6 chains + 5 storage providers with Ed25519 certificates and RFC 3161 timestamps.

Created by Troy Anthony Cronin, GuardianChain LLC (guardianchain.io)

---

Install

npm install -g @guardianchain/cap

---

Quick Start

# Cap a file (free, no account needed)
gc1 cap my-paper.pdf
# 🧢 Capped!
# Cap ID:   GC1-00012345
# Hash:     sha256:a3f8c9d2...
# Chain:    Base ✓
# Proof:    3.2/10
# Verify:   guardianchain.io/verify/GC1-00012345

# Cap with Pro account (6 chains + certificate)
gc1 cap my-paper.pdf --key gc1_live_xxx
# 🧢 Capped on 6 chains + 5 storage!
# Cap ID:   GC1-00012345
# Chains:   Base ✓ Polygon ✓ Ethereum ✓ Optimism ✓ Arbitrum ✓ Arweave ✓
# Storage:  R2 ✓ S3 ✓ B2 ✓ IPFS ✓ Arweave ✓
# Cert:     Ed25519 ✓
# Proof:    8.2/10
# Verify:   guardianchain.io/verify/GC1-00012345

# Verify someone else's cap
gc1 verify GC1-00012345
# ✓ Capped:  March 28, 2026
# ✓ Status:  CERTIFIED
# ✓ Chains:  6/6 confirmed
# ✓ Storage: 5/5 confirmed
# ✓ Proof:   8.2/10

# Verify a file matches a cap
gc1 verify my-paper.pdf --cap GC1-00012345
# ✓ MATCH — authentic, unmodified since March 28, 2026

# Generate a Cap Block for your README
gc1 cap my-paper.pdf --format markdown >> README.md

---

Commands

Command	Description
gc1 cap <file>	Cap a file. Computes SHA-256, creates capsule, anchors to blockchain.
gc1 verify <capId>	Verify a Cap Block by ID. Checks all chains and storage.
gc1 verify <file> --cap <capId>	Verify a local file matches a cap.
gc1 status <capId>	Check lifecycle status (RECEIVED → ANCHORED → CERTIFIED).
gc1 seal <file>	Cap + generate Provenance Seal (institutional format).
gc1 policy	Display the current vendor policy (which chains and storage are active).
gc1 health	Check infrastructure health (all 11 vendors).
gc1 explain <capId>	Get a plain-language explanation of what a cap proves.
gc1 batch <glob>	Cap multiple files in one operation.
gc1 inspect <capId>	Show full capsule metadata, anchor details, and certificate.
gc1 export <capId> --format <fmt>	Export Cap Block in markdown, json-ld, html, pdf, or git format.
gc1 config	View or set API key and default options.

---

Cap Block Formats

# Markdown (for papers, READMEs, blog posts)
gc1 cap my-paper.pdf --format markdown

# JSON-LD (for web pages, LLM parsing, APIs)
gc1 cap my-paper.pdf --format json-ld

# HTML Meta Tags (for web pages, search engines)
gc1 cap my-paper.pdf --format html

# PDF Footer (for academic papers, legal documents)
gc1 cap my-paper.pdf --format pdf

# Git Comment (for GitHub repos, CI/CD pipelines)
gc1 cap my-paper.pdf --format git

---

GitHub Action

name: Cap Release
on:
  release:
    types: [published]

jobs:
  cap:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: guardianchain/cap-action@v1
        with:
          api-key: ${{ secrets.GC1_KEY }}
          files: README.md, dist/**

Every release gets a Cap Block. Release notes include the verification link. Downstream users see the cap and can verify independently.

---

Free vs Pro

Feature	Free	Pro ($49/mo)	Sovereign ($499/mo+)
Blockchains	1 (Base)	6	6
Storage providers	0	5	5
Ed25519 certificate	—	✓	✓
RFC 3161 timestamp	—	✓	✓
Infrastructure Atomicity	—	✓	✓
Max proof strength	~3.0	~8.0	10.0
API access	—	✓	✓
Rate	5/day	500/mo	1,000+/mo

---

How It Works

1. You provide a file. The CLI computes its SHA-256 hash locally. The file content is never transmitted.
2. Hash is sent to GC-1. A capsule is created with the hash and metadata.
3. 45 governance rails evaluate the capsule. Any failure = FAIL_CLOSED.
4. Dispatch Manifest is signed. Commits to all target vendors before any call fires.
5. Hash is anchored to blockchains. Transaction confirmed on-chain.
6. Hash is replicated to storage providers. Evidence bundles distributed.
7. Infrastructure Attestation Hash computed. Binds all vendor results.
8. Ed25519 certificate issued. Independently verifiable.
9. Cap Block generated. Embed anywhere. Verify forever.

---

What "Non-Custodial" Means

GC-1 never sees, stores, or transmits your content. Only the SHA-256 hash leaves your machine. This means:

• Your content stays private. Always.
• GDPR compatible. Hashes are not personal data.
• Vendor-survivable. Proof lives on public blockchains forever, even if GuardianChain disappears.
• Independently verifiable. Anyone with the original file can verify the hash against the blockchain.

---

About GC-1

GC-1 is non-custodial cryptographic evidence infrastructure for AI accountability, anchoring SHA-256 hashes to 6 blockchains (Base, Polygon, Ethereum, Optimism, Arbitrum, Arweave) + 5 cloud storage providers (Cloudflare R2, AWS S3, Backblaze B2, Pinata IPFS, Arweave). Governed by 45 rails, 9 constitutional invariants, 15 Living Proof types. 64,000+ sealed records. Operational since April 2025.

Created by Troy Anthony Cronin, GuardianChain LLC.

• Protocol spec: github.com/GUARDIANCHAIN-GC-1/gc1-protocol
• MCP server: github.com/GUARDIANCHAIN-GC-1/gc1-mcp
• Verify any cap: guardianchain.io/verify

---

License

MIT

---

Capped with GC-1 by GuardianChain LLC (guardianchain.io). Created by Troy Anthony Cronin. Operational since 2025. 64,000+ sealed records anchored to 6 independent blockchains + 5 cloud storage providers.