ChainProof
Local, verifiable memory for AI agents
- What
- Local, verifiable memory for AI agents
- Cost
- Free
- Needs
- a macOS or Linux machine (no Windows release published); Go 1.24+ only if you build from source; no account, no API key, no payment — the software is free and open source (MIT).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — ChainProof is local-first continuity and provenance infrastructure for AI agents: a single Go binary that turns everything an agent does (inputs, tool calls, file changes, outputs, failures) into a durable, searchable evidence trail anchored in a hash chain you can verify without trusting any server. Run it on your own machine, wrap Codex, Claude Code, OpenClaw or any local harness, and resume work from verified checkpoints instead of a stale transcript. Open source (MIT) by @vajramatt — no account, no API key, no hosted service; your ledger never leaves your machine. Spotted in an r/AIAgentsInAction comment by u/DarkSolarWarrior. ⚠️ Security warning: the project's README suggests installing via curl|sh. This listing's install steps deliberately avoid that pattern (build from source or go install instead) — review the install script yourself before ever piping it to a shell. Honest caveats: very new third-party project (repo created August 2026, zero stars at listing time); multi-host coordination and signed attestations are roadmap items, not shipped features; the local HTTP API accepts loopback connections only and has no authentication — never expose it publicly. Note: this is local CLI infrastructure an agent drives, not a copy-paste Muse skill. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
ChainProof is a free Muse skill that audits a prompt against the full conversation and its linked files, keeping a verifiable chain of proof. It checks that the output stays faithful to the intent, reconciling the target prompt against the full conversation and linked files, then returning a structured verdict with evidence.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bfd7d66Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a macOS or Linux machine (no Windows release published); Go 1.24+ only if you build from source; no account, no API key, no payment — the software is free and open source (MIT). Install "ChainProof" for me. ChainProof is a local-first provenance ledger for AI agents: one Go binary that records agent runs (inputs, tool calls, changes, outputs) into a verifiable hash-chained SQLite ledger on my own machine. This prompt installs the pinned release v0.6.0. Repository: https://github.com/vajramatt/chainproof Pinned version: install the code at commit bfd7d661638631e265683f67decc07356af023a0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repository at the v0.6.0 tag into a temporary folder (git clone --branch v0.6.0 --depth 1 https://github.com/vajramatt/chainproof.git). I do not want any script piped into a shell. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-09 and recorded the fingerprint of the installer script at tag v0.6.0. I want you to compute the SHA-256 of scripts/install.sh from your clone and compare: - scripts/install.sh (tag v0.6.0): SHA-256 bf80c0d574604a836591a7d8a9debae3f3563501621040253c5b6f7c09f77f9d If the fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so this version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - what scripts/install.sh does, line by line in summary (expected: it downloads the official v0.6.0 release archive and checksums.txt from the repo's Releases page, verifies the archive's SHA-256 against the checksums, and installs the binary into ~/.local/bin) - every network address the code contacts - every place credentials, API keys or personal data are read, stored or sent (expected: none, this is a local-first tool with no account) - any obfuscated or encoded code If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what ChainProof does plus your safety findings, and wait for my explicit "yes, install". 5. Install it, using the first route that works: run the reviewed scripts/install.sh from the clone as a local file (sh scripts/install.sh, never piped from the network), which installs the binary into ~/.local/bin. If Go 1.24+ is available instead, go install github.com/vajramatt/chainproof/cmd/[email protected] is an accepted alternative. Only use release archives from the repo's own Releases page, and let the checksum verification happen before anything runs. 6. Bootstrap with the commands that exist in v0.6.0: run chainproof version to show the installed version, then chainproof init to create the ledger, then chainproof list to confirm the ledger opens. I am not asking for capabilities or doctor commands: they do not exist in v0.6.0, so do not try them and do not treat their absence as a failure. 7. Verify with no network calls: the binary answers at ~/.local/bin/chainproof, the ledger file exists at ~/.chainproof/chainproof.db (or $CHAINPROOF_DB), and chainproof list runs against it. 8. Report what was installed, where, and what I still need to do myself (for example wrapping my agent harness, or running chainproof serve later for the local dashboard at 127.0.0.1:7331). GitHub is optional: public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- installs packages — 1. Clone the repository at the v0.6.0 tag into a temporary folder (git clone --branch v0.6.0 --depth 1 https:/ · 5. Install it, using the first route that works: run the reviewed scripts/install.sh from the clone as a local · 1. Clone le dépôt au tag v0.6.0 dans un dossier temporaire (git clone --branch v0.6.0 --depth 1 https://github
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- bfd7d66 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Install prompt analysis
- 2026-10-13 : installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.