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.

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

Added documentation for escrow proposals with demos as gif #1

Merged
merged 3 commits into from
Jan 13, 2025

Conversation

benedictvscriticus
Copy link
Member

For completing the last outstanding deliverable prior to submission, I have documented the escrow proposal option in the style of the builder proposal page. I also added demos using gifs.


## Creating an Escrow Proposal

Functionality Funds are secured in escrow and released upon milestone completion. Milestone releases can be requested under the milestone management page.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a possible typo here? Should that be functionally ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adressed this typo.

This separate attestation flow ensures that all delegations are securely recorded, verifiable, and aligned with DAO governance protocols. If additional attestations or attesters are required for a DAO on Nouns.Builder, DAOs should contact Builder DAO or the SmartInvoice Team for assistance.

#### Attestation Flow
- Each attestation follows the schema ID `0x1289c5f988998891af7416d83820c40ba1c6f5ba31467f2e611172334dc53a0e`.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@benedictvscriticus Need to add a couple points here to ensure this is clear to the DAO members.

  1. The attestation MUST be done on same chain as where dao exists;
  2. The schema only has daoMultisig address which is what the delegated address will be and the recipient MUST be the treasury address of the dao.

cc: @wtfsayo

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adddressed this @dan13ram. Please check for wording.

@benedictvscriticus benedictvscriticus merged commit 510e0dd into main Jan 13, 2025
@benedictvscriticus benedictvscriticus deleted the escrow-doc-update-ben branch January 13, 2025 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants