blockchain_attestation

What This Skill Does

The blockchain_attestation skill leverages the Ethereum Attestation Service (EAS) to provide cryptographically verifiable proof of work completed by your AI agent. By creating structured attestations, it allows you to anchor the results of agent tasks to a public blockchain ledger. The system is designed to use Base mainnet as the primary chain, with a highly optimized workflow for offchain attestations that incur zero gas costs while maintaining full verifiability. The skill stores hashes of tasks and deliverables, ensuring data integrity without exposing sensitive content on the public ledger. It provides a full suite of CLI tools to register schemas, issue attestations, perform onchain timestamping, and verify proofs.

Installation

To integrate this skill into your environment, use the OpenClaw CLI: clawhub install openclaw/skills/skills/dbhurley/blockchain-attestation. Once installed, ensure you have set the EAS_PRIVATE_KEY environment variable for signing. For onchain operations, you must also provide EAS_RPC_URL. Perform an initial setup by navigating to the skill directory and running npm install. Finally, register the necessary data schema using the node attest.mjs schema register --chain base command to enable the system to interpret your task/output hash structures correctly.

Use Cases

• Audit Trails: Create non-repudiable records of when and how a specific agent task was completed for compliance and transparency.
• Content Provenance: Verify that a deliverable, such as a PDF report or a code patch, was generated by a specific authorized agent ID.
• Trustless Work Proofs: Enable third-party verification of agent output without needing to trust the agent's internal logs.
• Timestamping: Use onchain anchors for sensitive offchain files, proving the existence and integrity of a file at a specific point in time without revealing the content.

Example Prompts

1. "Attest the completion of the Q4 financial summary. Use the file at ./deliverables/report.pdf and sign it using the default offchain mode on Base."
2. "Please verify the attestation with UID 0x5a3f... and confirm it matches the metadata hash for the latest board meeting minutes."
3. "Anchor my latest offchain attestation to the Base mainnet to provide a public timestamp proof for the audit file."

Tips & Limitations

• Privacy First: Never include sensitive information or private keys in the attestation payload. Always favor offchain mode unless a public onchain event is specifically required for your use case.
• Chain Costs: Onchain attestations require gas fees on the Base network; monitor your wallet balance accordingly.
• Data Integrity: The schema is immutable once registered. If you need a new data structure, you must register a new schema UID.
• Storage: Offchain attestations are stored locally; ensure your file system is backed up to avoid losing the signed payloads.