@indelibleBSVon X · 2026-09-27
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-27 02:37 UTC.
Indelible 5.8.9 is out. Update today, then restart whatever you run Indelible in: npm i -g [email protected] --- We fixed a bug where overlapping saves could overwrite the file holding your wallet key. Two customers reported it, and it happened on one of our machines too. All three recovered their keys. --- The update brings: - Protected wallet-file writes - Automatic rolling backups - Clearer wallet recovery instructions - PIN setup when moving computers - Recovery after an interrupted save - Project restores that stay inside your chosen folder --- If an existing wallet appears missing, recover the SAME key. A different key cannot unlock your old saves. Mac users: run one Indelible process at a time for now. On all platforms, use a given wallet on one computer at a time. --- This is a fixes release. Nothing to relearn. Next up: getting our machine-to-machine, memory-engineering, and shared Agent Vault work into your hands. Thank you for backing this while we build it, and for reporting the problems that need fixing.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 607a2a4ec300b0ecb2f982162b27c79ea439ca4b73c5321d5bc7adbaafd61db6; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 97c1e9263991adbbff78707ea20356763073eb72add4bd68b3e28f990c18f2c1, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 607a2a4ec300b0ecb2f982162b27c79ea439ca4b73c5321d5bc7adbaafd61db6 — the block's timestamp proves the post said this at or before that time,
with no trust in bsv.cx. Content archived via the X API.