Category: DAO legal-disclosure standard / governance-metadata extension / compliance communication surface
Summary: DAOIP-9 is best understood as a minimal legal-publication extension to the DAO metadata stack rather than as a legal wrapper for DAOs. Its core move is to add a single legalURI field to an existing EIP-4824 / DAOIP-2 daoURI or entityURI, giving a DAO or online community one canonical place to publish legal notices, terms, jurisdictional disclosures, tax information, or a dedicated contact path for regulators and counterparties. The reusable mechanism insight is that DAOIP-9 turns “where do legal messages go?” into a standardized metadata slot, which makes control over that URI a meaningful authority surface above otherwise decentralized governance.
What it does:
Defines legalURI as an additional field to be published within an EIP-4824 / DAOIP-2 style DAO or entity metadata object
Lets the URI point to a markdown file, email address, webpage, IPFS file, or even another smart-contract address
Allows legalURI to point back to the daoURI itself if the publisher wants all DAO metadata to count as legally approved communication
Creates a standard slot for inbound and outbound legal communication without trying to standardize legal entity formation or protocol enforcement
Applies to DAOs and other online communities or entities that have an onchain presence but may not be formal legal or tax persons
Key claims:
The draft spec describes legalURI as an official mechanism for DAOs to receive and send legal communications and to display legal information to the public, which is the clearest reason to catalog DAOIP-9 as a communication-control surface rather than as generic compliance prose
The motivation explicitly compares legalURI to the Terms and Conditions or Privacy Statement links at the bottom of a website. That framing matters because DAOIP-9 is really about publishing a canonical legal touchpoint, not creating onchain legal logic
The spec intentionally allows many target types for the URI, including email, chat handles, webpages, IPFS files, and smart contracts. That flexibility is useful, but it also means the real governance question becomes who controls the endpoint and how trustworthy or durable it is
The rationale section makes the control surface concrete by listing regulators, legal proceedings, compliance documentation, tax statements, protocol risk disclosures, and participation restrictions as example uses. In other words, DAOIP-9 tries to standardize the publication slot where legal and compliance authority becomes visible
Compared with EIP-4824, DAOIP-9 is much narrower: EIP-4824 standardizes organizational metadata broadly, while DAOIP-9 adds one explicit legal/compliance channel inside that broader metadata frame
DAOIP-9 is worth keeping in the active corpus because it helps explain how DAO metadata standards can drift from discoverability and tooling into liability management, disclosure policy, and sanctioned channels for external contact
Whitepaper: No standalone DAOIP-9 whitepaper or litepaper surfaced in this pass. The clearest primary materials were the DAOIP-9 draft text plus DAOstar’s public documentation about its broader standards and regulatory-interoperability work, collected in ../whitepapers/daoip-9-primary-sources-2026-05-10.md.