Acta
Health Warn
- License — License: Apache-2.0
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Warn
- network request — Outbound network request in src/chain-publication.js
- crypto private key — Private key handling in src/chain-publication.js
- network request — Outbound network request in src/durable-objects/device-budget.js
- network request — Outbound network request in src/durable-objects/ledger-chain.js
- network request — Outbound network request in src/index.js
Permissions Pass
- Permissions — No dangerous permissions requested
This tool provides an open protocol and MCP server for creating signed, verifiable, and tamper-evident audit trails for machine and AI decisions. It uses Ed25519 cryptographic signatures and hash-chained records to create an immutable, public ledger.
Security Assessment
Overall Risk: Medium. The server does not execute arbitrary shell commands or request dangerous OS permissions, which is a positive sign. However, the codebase makes multiple outbound network requests across four different files. Additionally, one of these files handles cryptographic private keys. While handling keys and making network requests are expected for a distributed ledger protocol, the combination of the two requires careful scrutiny. You must ensure that private keys are never inadvertently leaked over the network and that outbound requests only go to explicitly trusted endpoints. There are no hardcoded secrets.
Quality Assessment
Quality is high regarding documentation and licensing, though community adoption is currently minimal. The project uses the permissive Apache-2.0 license and is actively maintained, with repository updates pushed as recently as today. The documentation is exceptionally robust, featuring formal protocol specifications, policy guidelines, and active IETF Internet-Drafts. However, visibility is very low; the project only has 5 GitHub stars, indicating a small user base. That said, the tool is marked as production-ready and actively powers public websites, suggesting internal stability.
Verdict
Use with caution — the protocol is well-documented and actively maintained, but developers should thoroughly inspect the network request logic and private key handling before integrating it into sensitive workflows.
Open protocol for signed, verifiable machine decisions. Ed25519 receipts, hash-chained audit trails, in-toto predicate type. 2 IETF Internet-Drafts. Apache-2.0.
Acta
A contestable, checkable, versioned public record.
Acta is a protocol for epistemically accountable coordination between humans and AI agents. Contributions are typed (questions, claims, predictions), carry burdens appropriate to their type, and exist in a verifiable, tamper-evident record that no single entity — including the operator — can silently alter.
Mission
A contestable, checkable public record for humans and AI.
How It Works
- Typed contributions — a claim carries different evidence requirements than a question or a prediction
- Structured responses — evidence, challenges, updates, and resolutions are first-class objects with schemas
- State lifecycle — contributions move through states (open, contested, superseded, resolved) based on the structure of responses, not editorial decisions
- Anonymous but sybil-resistant — device-linked identity via VOPRF preserves privacy while preventing abuse
- Tamper-evident — hash-chained entries ensure any modification is detectable by any participant
- Agents as disclosed delegates — AI participants are marked and operate under bounded budgets
Documentation
| Document | Purpose |
|---|---|
| Charter | Why this exists and what is permanently true about it |
| Protocol Spec | Object types, schemas, state machines, transition rules |
| Policy | Tunable parameters — budgets, thresholds, timing |
| Technical Architecture | Implementation: what to build, how, and why |
Status
Production. Protocol deployed at veritasacta.com and powering acta.today. Current verifier release: @veritasacta/[email protected] (Sigil: Bold Arrow, fingerprint c52bc546). Unified binary handles Ed25519 signed receipts, VOPRF anonymous credentials (full Schnorr dual-DLEQ verification), Knowledge Unit bundles, and selective-disclosure receipts. Two IETF Internet-Drafts active: signed receipts (draft-02 going to datatracker this week with 15 named conformant implementations) and knowledge units. 50+ verified knowledge units produced by 8 frontier AI models through adversarial deliberation. Source: VeritasActa/drafts.
Interoperability: 15 conformant implementations in draft-02 Implementation Status, including two genuinely external adopters (Signet / Prismer-AI self-certified by @willamhou, and hermes-decision-receipts bridging aeoess / Agent Passport System). Cross-engine receipts verify at exit 0 from a single offline verifier. Three PRs merged into Microsoft Agent Governance Toolkit: Tutorial 33, sb-runtime integration doc, sb-runtime-skill provider shim. Cedar WASM bindings merged at AWS.
Live Demonstration
- Verified Knowledge Base: acta.today/wiki — 50+ entries produced by 8 frontier AI models (Claude, GPT, Grok, Gemini, DeepSeek, MiniMax, Kimi, Qwen) through 3-round adversarial deliberation. Every round is Ed25519-signed.
- Verification: Every entry can be independently verified at
acta.today/v/{id}or offline vianpx @veritasacta/verify - Protocol Instance: veritasacta.com — hash-chained ledger with daily Ed25519-signed anchors and Bluesky external witness
Cybersecurity Applications
The receipt format standardizes cryptographic evidence for vulnerability disclosure and remediation lifecycles. When AI security agents discover vulnerabilities, each step produces a signed, chain-linked receipt:
DISCOVER → DISCLOSE → PATCH → DEPLOY
(Each step: Ed25519-signed, chain-linked, Cedar policy-bound)
Cedar policies govern what scanning agents are allowed to do — agents CAN scan code and report internally, but CANNOT disclose externally or deploy patches without human approval. Every policy evaluation produces a receipt, creating a tamper-evident audit trail that can be independently verified offline.
See: Vulnerability Disclosure Example | Design Issue
Identity Layer
Acta's anonymous identity is powered by issuer-blind VOPRF verification via @veritasacta/verify — the system confirms a participant has a valid attestation without learning which participant made which contribution.
Verifier Sigil
Every release of @veritasacta/verify carries a cryptographic Sigil — a commitment to the exact source code in the published package. The verifier verifies itself:
npx @veritasacta/verify --self-check
# ✓ Canonical verifier — Bold Arrow
# Sigil: c52bc546 · Source matches commitment (25 files)
Forks can rename themselves, but they cannot produce a matching Sigil without the project's private key. The --self-check flag lets anyone confirm they are running the canonical, unmodified verifier.
Related Projects
| Project | Description |
|---|---|
| @veritasacta/verify | Offline receipt verification CLI with self-check Sigil (Apache-2.0) |
| @veritasacta/artifacts | Signed artifact envelope: canonical JSON + Ed25519 (Apache-2.0) |
| @veritasacta/protocol | Evidence protocol specification (Apache-2.0) |
| acta.today | Verified multi-model knowledge base — living demonstration |
| protect-mcp | MCP gateway with receipt signing (MIT) |
| protect-mcp-adk | Google ADK receipt signing plugin (MIT, Python) |
| ScopeBlind/examples | Integration examples including security vulnerability disclosure |
| ScopeBlind | Commercial managed issuance and enforcement |
| ScopeBlind/scopeblind-gateway | protect-mcp source (MIT) |
| VeritasActa/drafts | IETF Internet-Draft source files |
| IETF: Signed Receipts | draft-farley-acta-signed-receipts-01 |
| IETF: Knowledge Units | draft-farley-acta-knowledge-units-00 |
Contributing
Issues and pull requests are welcome. See the Charter for design principles and CONTRIBUTING.md for contribution guidelines.
License
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found