ERC-8049: Contract-Level Onchain Metadata

[nxt3d]

Summary

Introduces a standard for storing contract-level metadata onchain using ERC-8042's Diamond Storage pattern. Extends ERC-7572's concept with onchain storage for cross-chain compatibility and upgradable contracts.

Key Features

• Diamond Storage: Uses ERC-8042 for predictable storage locations
• Cross-Chain Compatible: Storage slots remain consistent across deployments
• ERC-7572 Compatible: Maintains compatibility with existing contract metadata standards
• Upgradable Support: Metadata persists through contract upgrades

Technical Details

• Diamond Storage pattern for predictable storage locations
• Support for name, description, image, etc.

Example Use Case

Contract ENS Naming: Any contract can store its ENS name using this standard:

• name: "MyToken"
• description: "A decentralized exchange for trading ERC-20 tokens"
• ens_name: "mycontract.eth"

This enables contracts to self-identify with ENS names while maintaining consistent metadata across chains and through upgrades.

[eip-review-bot]

🛑 eip-review-bot failed for an unknown reason. Please see logs for more details, and report this issue at the eip-review-bot repository.

[github-actions[bot]]

The commit 86cecd64067dcf78cee2a15fcfe4b33f264c04be (as a parent of 65df388fc2b458ac252b2d19fdaac5e1de6ff957) contains errors. Please inspect the Run Summary for details.