Category: DAO metadata/discoverability standard / governance interoperability schema / offchain-onchain registry interface
Summary: ERC-4824 is best understood as discoverability and governance-legibility infrastructure rather than as a voting or treasury primitive. Its core move is to standardize a daoURI pointer plus a JSON-LD schema for members, proposals, activity, governance documents, and associated contracts, so DAOs and surrounding tools can expose a common metadata surface even when governance itself is fragmented across forums, Snapshot, multisigs, L2s, and multiple contracts. The reusable mechanism insight is that ERC-4824 makes governance more portable and indexable without standardizing governance logic itself, which means practical soft power shifts toward whoever publishes, updates, indexes, and interprets the daoURI metadata path.
What it does:
Requires a DAO contract or compatible registration contract to expose a daoURI() endpoint returning a top-level JSON-LD object
Defines standard subsidiary surfaces for membersURI, proposalsURI, activityLogURI, governanceURI, and contractsURI, while also allowing embedded non-URI variants inside the top-level object
Supports either native DAO contract implementation or an external registration contract, so metadata publication can be layered onto existing DAO frameworks
Specifies indexing patterns and priority rules for direct publication versus common registration-factory publication, including a reference indexer flow
Standardizes proposal identifiers and proposal metadata fields strongly enough for discovery, simulation, and cross-tool linking without forcing a single governance engine
Extends beyond strict DAOs by allowing other entities to publish the same style of metadata under types like Organization, Foundation, or Entity
Creates an interoperable metadata layer that tools such as explorers, governance dashboards, framework providers, and registry operators can consume
Key claims:
The ERC motivation explicitly says a standard daoURI should improve DAO discoverability, legibility, proposal simulation, and interoperability between tools, which is the clearest reason to catalog ERC-4824 as metadata infrastructure instead of governance execution logic
The spec requires only a pointer to structured metadata and intentionally leaves substantive governance mechanics outside scope, which means ERC-4824 standardizes how a DAO is described rather than how it must decide
The rationale says DAOs already need offchain data to power user interfaces, governance apps like Snapshot or Tally, and discovery platforms like DeepDAO, Messari, and Etherscan, signaling that the standard is really about normalizing an already-important soft-power layer
The specification makes contractsURI especially important for DAOs whose governance spans multiple contracts and even multiple chains, which shows the standard is trying to solve legibility problems created by fragmented real-world DAO stacks
The indexing section says metadata may be published directly or through registration factories, with the most recent or factory-published registration taking precedence, which reveals that trust and authority can migrate toward registry operators and publication flows
The standard explicitly allows entities that do not identify as DAOs to publish the same style of metadata, suggesting ERC-4824 is as much an organizational-description layer as a pure DAO primitive
DAOstar’s adoption guide shows multiple publication paths — self-hosted endpoints, GitHub-hosted JSON, framework-generated endpoints, ENS text records, EAS attestations, and onchain registration contracts — making the publication path itself part of the governance surface
DAOstar’s docs also note framework and tooling support paths through Aragon, Snapshot, Boardroom, and DAODAO-style ecosystems, which reinforces that ERC-4824 matters where governance metadata is created and indexed, not only where proposals are cast
Whitepaper: No standalone ERC-4824 whitepaper surfaced in this pass. The strongest primary materials were the ERC page, the raw ERC markdown, DAOstar’s adoption guide, and DAOstar’s repository README; see ../../whitepapers/erc-4824-primary-sources-2026-05-08.md.