Hey Product Hunt! 👋 I’m Justin, creator of GitProof (https://gitproof.legendrail.com). Git timestamps are hearsay. GitProof makes them evidence. Here is the problem founders and engineering teams are running into right now: 1. Git timestamps are client-controlled: Anyone can run git commit --amend --date="yesterday". Because Git records whatever your local clock claims, raw git history is legally unauthenticated hearsay under Federal Rule of Evidence 802. 2. The Post-Thaler AI Copyright Crisis: Following Supreme Court precedent and U.S. Copyright Office guidance, purely AI-generated code has zero copyright protection. To register and defend proprietary software under Title 17, founders must prove granular, iterative human authorship. During M&A tech diligence, buyers enforce strict IP Reps & Warranties—leading to valuation haircuts or escrow holdbacks if chain-of-title cannot be proven. To solve this without creating a closed black box, GitProof uses an Open Verifier, Commercial Producer architecture: 🛡 100% Open-Source Verifier (MIT): The standalone verifier (legendrail/gitproof-verify) is a zero-dependency Go CLI. Opposing counsel, auditors, or judges can inspect the Merkle tree math, parse RFC 3161 ASN.1 tokens, and verify against DigiCert/Sectigo root CAs completely offline. 📜 Self-Authenticating FRE 902 Certificates: Generates banknote-grade vector PDF certificates embedding formal statutory declarations under penalty of perjury (28 U.S.C. § 1746) ready for investor data rooms or court exhibits. 🔒 100% Offline & Zero Telemetry: Your source code never leaves your machine. Only a 32-byte SHA-256 hash imprint touches public Time Stamp Authorities. Install in one line: curl -fsSL https://gitproof.legendrail.com/... | bash It’s free forever for individual developers, with Pro and Team tiers for custom corporate entities, multi-TSA redundancy, and CI/CD automation. I’d love to hear your feedback on the cryptographic design and workflow! 🚀