Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to include email in DAOIP-9 #283

Closed
wants to merge 1 commit into from
Closed

Request to include email in DAOIP-9 #283

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions DAOIPs/daoip-9.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,18 +21,24 @@ You can think of legalURI as roughly equivalent to the standard “Terms and Con
## Specification
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

To comply with this specification you MUST publish a daoURI or entityURI following the EIP-4824 / DAOIP-2 DAO JSON LD Schema and add a field called “legalURI”. This URI MAY point anywhere, e.g. to a markdown file with information, a single email address such as [email protected], a webpage with terms and conditions, an IPFS file, or another smart contract address.
To comply with this specification, you MUST publish a daoURI or entityURI following the EIP-4824 / DAOIP-2 DAO JSON-LD Schema and include a field called legalURI.

The legalURI MUST include an email field that provides a valid email address (e.g., [email protected]). Email is recognized as a legally binding form of communication in many jurisdictions and ensures a reliable, accessible, and universally accepted channel for legal correspondence.

Additional optional fields, such as a webpage with terms and conditions, an IPFS file URI, or a smart contract address, may be included to supplement the mandatory email field and enhance transparency.

```json
{
"@context": "http://www.daostar.org/schemas",
"type": "DAO",
"name": "<name of the DAO>",
"description": "<description>",
"legalURI": "<URI>"
"legalURI": {
"email": "[email protected]",
"legalDocument": <RECOMMENDED: An URI pointing to the legal document of Terms and Conditions>,
}
}
```

You MAY point legalURI back to the daoURI address, which would indicate that all data published through daoURI constitutes legally-approved communication.

## Rationale
Expand Down Expand Up @@ -62,4 +68,4 @@ Providing clear legal information helps participants understand their rights and
- Distribution statements: Sharing records of DAO Treasury payments or staking rewards distributed to participants.

## Copyright
Copyright and related rights waived via [CC0](https://eips.ethereum.org/LICENSE).
Copyright and related rights waived via [CC0](https://eips.ethereum.org/LICENSE).