Status · updated 2026-08-09
What works today. What's coming.
Inverba is open source and in active development. This page is the honest line between the two: everything under "works today" you can run right now; everything under "planned" is a published design, not running code. If a claim on this site contradicts this page, this page wins — and it's a bug worth reporting.
Releases
v0.1.0
2026-08-09
First public release of the open core: fetch → sign → verify, agent-to-agent verify_handoff with replay defense, and C2PA export.
Works today
- ✓Solo scraping with signed provenance records — fetch, hash, Ed25519-sign, fully local (inverba scrape)
- ✓Offline verification — records check out on any machine with ~30 lines of any language, no Inverba install
- ✓Change detection with signed before/after evidence, significance-classified
- ✓C2PA export of provenance records as Content Credentials manifests
- ✓Agent-to-agent verification — one agent independently checks another's records
- ✓241 tests passing on the open core · Apache-2.0, every line auditable
- ✓Replay defense — an opt-in verifier seen-cache returns REPLAYED instead of a second TRUSTED on a re-presented record
Planned — designed, not yet running
- ◦Cross-verifier challenge-binding for replay defense — designed for the hosted enforcement layer, not built
- ◦Hosted Merkle transparency log (registry) for anchoring records, with public roots
- ◦Watchtowers — independent monitoring of the log by anyone
- ◦Hosted notary for opt-in two-party corroboration at N=2 (open security items remain before hosted exposure)
- ◦Multi-vantage cloaking detection and trust-scored distributed extraction across worker swarms
Why this page exists
Inverba's entire value is that you don't have to take anyone's word for anything. That has to include ours. Full commit history and diffs on GitHub.