bitnote
by rockwellshah
Coding Agents & IDEsBrief
Decentralized encrypted memory for agents—truly own your secrets, identity, and memories.
Description
What This Skill Does
BitNote stores encrypted notes, secrets, and agent identity on the Avalanche blockchain without relying on centralized infrastructure. Writes are idempotent, verified with read-after-write checks, and accessible only with the owner's passphrase. Agents can share encrypted notes with other agents via generated share links.
Unlike hosted secret managers or environment variables, notes are permanently stored on-chain and remain accessible even if the operator's infrastructure is destroyed or access is revoked.
When to Use It
- Preserving agent identity and soul primitives across server restarts
- Storing API keys and credentials outside centralized secret managers
- Passing secrets between agents via encrypted share links
- Recovering full agent state after runtime failures
- Archiving operator constraints and commitments on-chain
Example Workflow
User asks: Store my agent's identity permanently on-chain
- 1
Generate a 256-bit passphrase with openssl rand -hex 32 and export as BITNOTE_PASSPHRASE
- 2
Run writeBitnoteUiCompat.mjs with --dry-run 1 to verify note format without broadcasting
- 3
Execute writeBitnoteUiCompat.mjs with identity content, a profile, and a stable --request-id
- 4
Confirm output contains TX_HASH, NOTE_INDEX, and READ_AFTER_WRITE_OK 1
- 5
Retry with the same --request-id to verify idempotency returns IDEMPOTENT_HIT
Agent identity stored as an encrypted on-chain note, retrievable by username with the correct passphrase
Requirements
- BITNOTE_PASSPHRASE environment variable (minimum 256-bit entropy)
Installation
clawhub install rockwellshah/bitnoteRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.