This directory contains the official documentation for the CAFE (Crypto-Agility Framework for Ethereum) project. Last updated: April 2026.
- 01-introduction-cafe-crypto-agility.md — Introduction to CAFE and the crypto-agility problem for the Ethereum blockchain
- 02-cafe-user-guide.md — Complete user guide for the CAFE frontend: navigation (Discovery, Platform, CPM, Remediation), anonymous mode (view-only without account; sign-in to run scans), and all features
- 03-cafe-developer-guide.md — Complete developer guide with API documentation (including anonymous token and anonymous scan endpoints), code examples in multiple languages (cURL, Go, Python, Java, JavaScript), and the Discovery -> CPM normalized wallet observation contract (
discovery.wallet.observedv0.1) for cross-service integration
CAFE (Crypto-Agility Framework for Ethereum) is a three-service platform designed to discover, govern, and remediate cryptographic assets on Ethereum—ensuring compliance, resilience, and trust in the post-quantum and zero-knowledge era.
CAFE is composed of three main services:
- Discovery — Identification of on-chain and network quantum exposures
- Crypto Policy Manager — Definition and enforcement of cryptographic policies
- Remediation — Secure migration and attested key operations
- CAFE Whitepaper — May be private while content is prepared for public release
- Discovery Repository — Cryptographic discovery service with PQC (see README Data structure (CPM export contract) for the CPM-facing observation shape)
- Crypto Policy Management (
cafe-cpm) — Policy service; normative contract and vocabulary for Discovery exports - Frontend Repository — User interface
- Infrastructure Repository — Infrastructure and deployment
- Crypto backend Repository — Cryptographic backend; tooling for building and running applications with Post-Quantum Cryptography (PQC) support
- Edge Repository — Reverse-proxy images with PQC
- TLS scanner Repository — TLS scanner service with PQC
- CAFE Website — Public website
- Deploy repository is not public for security reasons; deployment is straightforward to reproduce without it
To contribute to the documentation, please follow Markdown formatting conventions and maintain consistency with existing documents.