ercdata
Store, verify, and manage AI data on the Ethereum blockchain (Base network) using the ERCData standard. Use when an agent needs to store data fingerprints on-chain, verify data integrity, create audit trails, manage access control for private data, or interact with the ERCData smart contract. Supports public and private storage, EIP-712 verification, snapshots, and batch operations.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/0xreisearch/ercdataWhat This Skill Does
The ercdata skill provides a robust interface for interacting with the ERCData standard on the Base network. It enables AI agents to transition from ephemeral, off-chain data management to persistent, verifiable on-chain storage. By leveraging the Ethereum blockchain, this skill ensures that agent actions, memories, and identity fingerprints are immutable and auditable. The skill supports granular privacy controls, allowing agents to choose between public, transparent logs for audit trails or private, gated entries accessible only to specific authorized addresses. It utilizes EIP-712 for cryptographic verification, ensuring that stored data has not been tampered with since the time of submission.
Installation
To integrate this skill into your agent, use the OpenClaw command-line interface. Ensure you have your Base network private key and the target ERCData contract address configured. Run the following command in your terminal:
clawhub install openclaw/skills/skills/0xreisearch/ercdata
Once installed, configure your environment variables ERCDATA_KEY, ERCDATA_CONTRACT, and ERCDATA_RPC to allow the agent to sign transactions and query the chain successfully.
Use Cases
- Immutable Memory Auditing: Periodically save hashes of your agent's core memory files to the blockchain to prove that previous instructions or knowledge bases have not been modified.
- Agent Identity & Provenance: Store the fingerprint of your current system prompt, model architecture, and versioning. This establishes a 'proof-of-identity' that other agents can verify before interacting with you.
- Verifiable Output Logs: Whenever your agent generates high-stakes output or decision-making logs, store the hash on-chain to provide a permanent, tamper-proof record that can be audited by third parties or end-users later.
- Secure Cross-Agent Collaboration: By granting access to private entries to specific partner agent addresses, you can share sensitive data or credentials across a network of agents with granular on-chain access control.
Example Prompts
- "Record the current hash of my system configuration to the ERCData contract to ensure its integrity for our next session."
- "Verify the entry with ID 452 on the chain to confirm the data matches the original signature."
- "Grant read access to the private entry 892 to the agent address 0x71C7656... to share my latest memory snapshot."
Tips & Limitations
- Privacy Note: While the
privateflag prevents unauthorizedgetData()calls, remember that the raw calldata is visible on block explorers like Basescan. Always hash or encrypt sensitive data before storing it if absolute privacy is required. - Cost Considerations: Every store operation requires gas on the Base network. Bundle related data entries where possible to optimize gas costs.
- Verification: Always use the
verifycommand after storing critical data to confirm that the transaction was processed correctly and the EIP-712 signature is valid.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-0xreisearch-ercdata": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, code-execution