# CryptoProto

> Decentralized content ownership powered by cryptography, not contracts.

CryptoProto encrypts content with AES-256-GCM, stores ciphertext permanently on Arweave, and gates access with Solana NFTs. Ownership is verified on-chain — no platforms, no subscriptions, no middlemen.

## Key Features

- AES-256-GCM encryption with permanent Arweave storage
- NFT-gated access via Solana with on-chain ownership verification
- Cloudflare Worker key escrow across 300+ edge nodes
- MCP-native: 7 composable tool calls for AI agent integration
- Zero servers, zero config infrastructure

## How It Works

1. Creator encrypts content with AES-256-GCM
2. Ciphertext is uploaded permanently to Arweave
3. An NFT is minted on Solana representing ownership
4. The decryption key is registered with the key escrow
5. To access content, the viewer signs a challenge with their wallet
6. The escrow verifies NFT ownership on-chain via Helius DAS API
7. Upon verification, the decryption key is released

## MCP Tools

- `encrypt(file, key)` — Encrypt content
- `upload(ciphertext)` — Store on Arweave
- `mint(nft, metadata)` — Mint ownership NFT
- `register(key)` — Register key with escrow
- `challenge(wallet)` — Issue verification challenge
- `verify(signature, nft)` — Verify ownership
- `decrypt(ciphertext, key)` — Decrypt content

## Pages

- `/` — Landing page: hero, feature cards, MCP tool list, manifesto.
- `/docs` — Single-page documentation: overview, architecture diagram, getting started, full tool reference, escrow API, security model, FAQ.
- `/tools` — Install hub: MCP server config snippets for Claude Desktop, Cursor, and Claude Code; project info; seven-tool summary.
- `/about` — Why CryptoProto exists, the protocol design rationale, and the project block (a project by Joey Janisheck).

## Links

- Website: https://cryptoproto.com
- Full documentation: /llms-full.txt