Proof Of Memory

What This Skill Does

Proof of Memory (PoM) is a cryptographic verification skill designed by kunoiiv to ensure the integrity and immutability of an AI agent's personal memory records. By implementing a Proof-of-Work (PoW) mechanism similar to Bitcoin's architecture, the skill generates a daily cryptographic hash of the memory/YYYY-MM-DD.md files. This process creates a tamper-proof chain that anchors to a master MEMORY.md ledger. The PoM process involves grinding a nonce to meet a specific difficulty requirement (leading 0000s), ensuring that any attempt to retroactively modify a past day's memory will break the hash chain and reveal the alteration. It provides sovereign recall, allowing an agent to verify the historical accuracy of its own experiences without relying on external databases.

Installation

To install this skill, use the ClawHub CLI command in your terminal: clawhub install openclaw/skills/skills/kunoiiv/proof-of-memory

Ensure that your environment has Node.js installed, as the PoM verification logic relies on node to execute the hashing scripts. For production, set up a cron job to trigger the verification script daily: cron every=86400s: node skills/pom/pom.js

Use Cases

• Immutable Journaling: Create a secure, verifiable log of AI interactions that cannot be altered by system errors or malicious injection.
• Self-Auditing Agents: Allow agents to verify the history of their internal state transitions or key learning moments over extended durations.
• Sovereign Archiving: Establish a trusted audit trail for autonomous agents operating in decentralized or high-security environments.

Example Prompts

• "OpenClaw, please run the Proof of Memory verification check for today's logs and confirm the chain remains intact."
• "Display the last PoM block hash generated for the memory file dated 2023-10-27."
• "What is the current status of the cryptographic hash chain for my long-term memory?"

Tips & Limitations

• Difficulty: The difficulty level is currently set to a static 0000s requirement. If performance issues arise during the hashing phase, consider hardware-accelerated environments.
• Dependency: This skill is strictly dependent on the structure of the memory/ directory. Ensure your memory management system follows the YYYY-MM-DD.md filename convention strictly.
• Persistence: Because this creates a chain, deleting a single day's log file may invalidate the entire subsequent chain. Always backup your MEMORY.md file regularly.