Description
This documentation provides non-normative, community-maintained data profiles and best practices for ERC-8004, covering offchain JSON formats and implementation patterns.
IMPORTANT
This is not the official EIP-8004 specification. These are supplementary guidelines to help implementers adopt consistent patterns.
Core Data Profiles
| Profile | Description |
|---|---|
| Conventions | RFC 2119 keywords, field types, URI schemes |
| Agent Metadata | AgentURI format - identity, endpoints, trust |
| Feedback Data | Reputation records - scores, evidence, payment |
| Validation Data | Proofs and attestations - zkML, TEE, staking |
| Attachment Pattern | Reusable evidence schema for files |
Quick Start
Registering an Agent
json
{
"type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
"name": "My Agent",
"description": "What my agent does",
"image": "https://example.com/logo.png"
}See Agent Metadata Profile for full schema.
Submitting Feedback
json
{
"agentRegistry": "eip155:84532:0x...",
"agentId": 42,
"score": 95,
"reasoning": "Excellent service"
}See Feedback Data Profile for full schema.
Requesting Validation
json
{
"agentRegistry": "eip155:84532:0x...",
"agentId": 56,
"validationType": "zkml-proof",
"reasoning": "Verify model execution"
}See Validation Data Profile for full schema.
Implementation Guides
- Agent Metadata Parsing - Parser architecture and validation
- Feedback Best Practices - Evidence collection and privacy
- Validation Best Practices - Proof integration patterns
Extensions
- Data URI Compression - 60-70% gas savings for onchain metadata
Reference
- Glossary - Terms and abbreviations
- Sources - Data sources and methodology
- Official EIP-8004 - Normative specification
Relationship to EIP-8004
| Aspect | EIP-8004 (Official) | These Profiles (Community) |
|---|---|---|
| Defines | Smart contract interfaces | Offchain data patterns |
| Scope | Onchain behavior (normative) | Metadata recommendations |
| Authority | Ethereum EIP process | Community-maintained guidelines |
| Adoption | MUST for compliance | SHOULD for interoperability |
Contributing
- GitHub Issues
- See CONTRIBUTING.md for guidelines