"SMTs require absolute cryptographic correctness, while PDF specs are a legacy parsing nightmare.
Have you found AI useful for scaffolding these, or do the subtle hallucinations make it more trouble than it's worth?"
"SMTs require absolute cryptographic correctness, while PDF specs are a legacy parsing nightmare.
Have you found AI useful for scaffolding these, or do the subtle hallucinations make it more trouble than it's worth?"
Building Olympus — an open-source cryptographic document provenance ledger aimed at press freedom orgs (journalists can prove a document hasn't been tampered with, without it ever leaving their machine — only a proof gets published). Rust + Tauri 2, Sparse Merkle Tree ledger, ZK redaction proofs.
Solo, self-taught, working a trade job on the side, heavily AI-assisted (Claude Code, Codex, etc.) for implementation while I handle architecture and threat modeling.
Looking to trade eyes with other founders here — drop your repo below and I'll go through it, and I'll link mine back. Especially useful if you've got a security/architecture background, since I don't have a formal CS one and could use outside eyes on the crypto and threat model.
---
Solo dev, trade job by day, building this at night with Claude/Codex/Copilot as implementation arms while I handle architecture/threat modeling. No CS degree — 8 months, 1,500+ PRs.
**Olympus** (Rust + Tauri 2) lets journalists prove a document existed and wasn't tampered with — without it ever leaving their machine. Only a proof gets published, not the file.
**Why it matters:** most authenticity tools either need a trusted third party, or break the proof the moment you redact anything. Reporters often can't publish a document whole. Proving a redacted doc is a faithful subset of the original — without revealing what was cut — is the hard part.
**Stack:** Sparse Merkle Tree ledger, signed Merkle fold redaction proofs (pivoted off Groth16/Circom — ADR-documented), Poseidon, BabyJubJub/EdDSA, BLAKE3, RFC 3161 timestamping, offline-verifiable. Latest audit: zero Critical/High. 2,400+ tests.
**New test case:** archiving content from **1f916.ai** (an AI-agent-only forum with its own hash-chained ledger) into Olympus, verifiably. Hard part: composing two independent hash-chains without leaking trust at the seam.
**Question:** anyone here done anything really pushing Ai coding abilities? And what where the pitfalls.
Olympus — a verifiable ledger for sensitive information. Tamper-evident Sparse Merkle Tree ledger with redaction proofs via a Folded Signed Merkle tree, soulbound credentials, and offline-verifiable court evidence. Rust + Tauri 2 + Axum + pg_embed desktop.
https://github.com/OlympusLedgerOrg/Olympus.git https://olympusledgerorg.github.io/Olympus/