indelible-mcp 5.7.0 → 5.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CLI_HANDBOOK.md +26 -0
- package/CUSTOMER_AGENT_HANDBOOK.md +9 -0
- package/package.json +1 -1
- package/src/index.js +2 -2
package/CLI_HANDBOOK.md
CHANGED
|
@@ -25,6 +25,32 @@ You don't have to memorize any of this. In Claude Code you can just say what you
|
|
|
25
25
|
|
|
26
26
|
Three things worth knowing, once: **your key stays on your machine** (nothing we run ever sees it) · **reading is always free** (saves cost fractions of a cent in Bitcoin fees) · **your stop button beats everything** (pause works even with no wallet at all).
|
|
27
27
|
|
|
28
|
+
## Honest Receipts + the Wallet (5.7.0)
|
|
29
|
+
|
|
30
|
+
**"Committed" now means mined.** A fresh save reports `pending` until a miner buries it in a block
|
|
31
|
+
(usually within about ten minutes), then confirms on its own. Your data still broadcasts in seconds;
|
|
32
|
+
only the word got stricter. No server's acceptance — including ours — is ever reported as
|
|
33
|
+
confirmation anymore.
|
|
34
|
+
|
|
35
|
+
**Double-spends are final the first time the network says so.** If two of your machines ever race
|
|
36
|
+
for the same coin, the losing save is told the truth immediately and rebuilds on fresh coins,
|
|
37
|
+
instead of being retried until something said yes.
|
|
38
|
+
|
|
39
|
+
**The wrong-key guard.** If your config ever holds a key that does not match your account address,
|
|
40
|
+
every save refuses before any money moves and names both addresses, because data written with the
|
|
41
|
+
wrong key can never be read back by your wallet.
|
|
42
|
+
|
|
43
|
+
### `indelible-mcp wallet`
|
|
44
|
+
Shows every coin reservation your wallet is holding: which process holds it, whether that process is
|
|
45
|
+
alive, and what it has locked. If a crashed process left a stuck reservation, free it with
|
|
46
|
+
`indelible-mcp wallet --cancel=<token-prefix>`. It refuses to cancel anything a live process still
|
|
47
|
+
holds, and anything with a signed transaction attached — freeing those is how double-spends happen,
|
|
48
|
+
so it structurally cannot.
|
|
49
|
+
|
|
50
|
+
### Background auto-save
|
|
51
|
+
Runs every 15 minutes by default on every install. Change the pace on the MCP tab at indelible.one —
|
|
52
|
+
your machine picks the new setting up automatically.
|
|
53
|
+
|
|
28
54
|
## Two Pilots (5.2.0)
|
|
29
55
|
|
|
30
56
|
Indelible works with Claude Code, with OpenAI's Codex CLI, or with both at once on the same memory.
|
|
@@ -192,6 +192,15 @@ This fetches the pack and backfills meaning-vectors for your existing history. I
|
|
|
192
192
|
|
|
193
193
|
**`diary_recall`** is the same power scoped to your companion's own history. `scope: "diary"` for saved diary entries, `"duo"` for live Claude-plus-companion rounds, `"all"` for both.
|
|
194
194
|
|
|
195
|
+
### Honest receipts (5.7.0)
|
|
196
|
+
|
|
197
|
+
A save now reports `pending` until a miner buries it in a block, then it becomes `committed` on its
|
|
198
|
+
own. Nothing — not our servers, not a relay — can call your save confirmed anymore. Only the chain
|
|
199
|
+
can. If a save ever loses a race to another machine spending the same coin, you are told the truth
|
|
200
|
+
immediately and the save rebuilds itself on fresh coins. And if your configuration ever holds a key
|
|
201
|
+
that does not belong to your account, saving refuses before any money moves, because data written
|
|
202
|
+
under the wrong key is data your wallet can never read back.
|
|
203
|
+
|
|
195
204
|
### Two pilots on one memory (5.2.0)
|
|
196
205
|
|
|
197
206
|
Your memory is not tied to one AI. Wire OpenAI's Codex CLI to the same install (`~/.codex/config.toml` → `[mcp_servers.indelible]` `command = "indelible-mcp"`) and it reads and writes the same chain as Claude Code. Every save is stamped with its author inside the encrypted record; the Context tab on indelible.one shows `Saved by Claude` or `Saved by Codex` once your record decrypts, and if an index ever claims a different author than your decrypted record proves, the app shows you both values and trusts neither.
|
package/package.json
CHANGED
package/src/index.js
CHANGED
|
@@ -16120,7 +16120,7 @@ Answer THAT message and nothing else \u2014 the wire also carries unrelated conv
|
|
|
16120
16120
|
}
|
|
16121
16121
|
function printHelp() {
|
|
16122
16122
|
console.log(`
|
|
16123
|
-
Indelible MCP \u2014 Blockchain memory for Claude Code (v5.7.
|
|
16123
|
+
Indelible MCP \u2014 Blockchain memory for Claude Code (v5.7.1)
|
|
16124
16124
|
|
|
16125
16125
|
Setup:
|
|
16126
16126
|
indelible-mcp setup --wif=KEY --pin=PIN Import and encrypt your private key
|
|
@@ -16447,7 +16447,7 @@ function readStdin() {
|
|
|
16447
16447
|
}
|
|
16448
16448
|
var SERVER_INFO = {
|
|
16449
16449
|
name: "indelible",
|
|
16450
|
-
version: "5.7.
|
|
16450
|
+
version: "5.7.1",
|
|
16451
16451
|
description: "Blockchain-backed memory and code storage for Claude Code"
|
|
16452
16452
|
};
|
|
16453
16453
|
var TOOLS = [
|