el4d
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
2
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# DAO Split design (prev. known as Ragequit Threshold) ## Conditions Split can be signaled on proposals. To successfully split, the following conditions must be met: 1. You voted opposite the proposal's outcome, e.g.: 1. You voted against and the proposal passed. 2. You voted for, quorum was reached, and the proposal was defeated. 2. You signaled to split during voting period or during timelock delay. 3. Enough Nouns signaled to split on this proposal to pass the split threshold; Nouns may submit a split signal up until the end of a proposal's queuing period (before execution if successful) or up until a proposal is defeated. * As of March 2023 20% of total supply seems like the lowest threshold we can safely set. Assuming these conditions are met, a DAO split can be executed at the end of the proposal lifecycle: * **Successful proposals**: executing the proposal first executes the split; alternatively anyone can execute the split first, then execute the proposal. The split can be executed at any time after the queuing period, up until the proposal expires. * **Defeated proposals**: anyone can execute the split at any time after the proposal's defeat, and until defeat time + proposal expiration time (currently 14 days). ## Where Nouns Go What happens with Nouns that signal a DAO split? 1. Upong signaling these Nouns are transfered from the owner's account to an escrow contract. 2. The escrow contract delegates the escrowed voting power to an account the owner chooses, so they can continue voting until the split is settled. 3. Once the proposal the split was signaled on reaches an end state, Nouns are taken out of the proxy: 1. Successful split: Nouns are sent to the Nouns DAO treasury. 2. No split: owners can withdraw their Nouns. ## Outcome: a new DAO A successful split creates a new NFT DAO; including a new NFT, auction house, DAO logic, DAO treasury. The fair share of all split Nouns is sent to the new DAO's treasury. For example, if 20% of all Nouns split, then 20% of Nouns DAO treasury assets are sent to the new DAO. New DAO starting configuration: * **Token**: each DAO split account is minted the same number of tokens they split with. * **Art**: new token reuses the existing Nouns on-chain art, and the new DAO can vote to use different art. * **Founder reward**: new token has no founder rewards; it is an upgradable contract so that new DAO members can adjust it to their needs; new token also supports locking furthur upgrades. * **Token IDs and art will be the same** as the original Nouns split accounts left behind. * **Auction House**: a new auction house is deployed paused; new DAO members can vote to configure and start it. * **DAO**: * a new copy of the latest Nouns DAO logic + timelock (treasury) contracts is deployed for new DAO; all logic and configurations are the same unless stated otherwise, e.g. it has the same logic for proposals, voting, DAO split, etc. * the DAO split threshold is set to a single token, to minimize the risk of a majority attack in the new DAO. * **Vetoer**: The new DAO doesn't have a set Vetoer; DAO members can vote to set a new Vetoer. * There will be **a configurable no-proposals period at first**, to mitigate the risk of malicious proposals in the new DAO's early days. * **UI**: new DAO should be able to launch their own UI, or reuse an existing DAO UI without any coding skills. * Specific design TBD; it can be a better-packaged version of nouns.wtf, and it can also be Nouns Builder UI automatically supporting auctions and governance for any split-created DAO. ## Outcome: asset split Nouns DAO can configure which tokens are distributed upon a DAO split, while other tokens remain entirely with Nouns DAO. The tokens configured to be distributed are sent pro rata, so for example if 20% of Nouns split, then 20% of the configured assets are sent to new DAO. ### NFTs #### Rounding in favor of Nouns DAO In the case of NFTs it can get tricky as they don't have decimals. The current solution is to round down in favor for Nouns DAO. For example, say 20% of Nouns split, and Nouns DAO holds 197 tokens of a certain NFT; that comes out to 39.4 NFTs, in which case we would send 39 NFTs to new DAO and the rest will remain with Nouns DAO. #### Which NFTs will be sent? We can randomize which IDs get sent to new DAO, using Chainlink VRF or new developments in on-chain randomization that leverage ETH2 RANDAO. #### Lottery Another approach is to run a lottery of which DAO gets which NFTs. We can use random numbers to determine if a given NFT should stay with the original DAO or go to the new DAO. For example, say 30% of Nouns choose to split, we can generate a random number between 1 and 10; if the number is 1-3, it goes to the new DAO, and if it's 4-10 it goes to the original DAO. ## FAQ ### Why not just burn the Nouns left behind? TL;DR: it gives the original DAO more options, including the option to burn them. If the split is due to a malicious proposal (aka a 51% attack), where honest Nouners are escaping to the new DAO, most likely the Nouns left behind in the hands of the attacker won't be very valuable, so it seems fine to leave them in their hands. If the split leaves honest Nouners in the original DAO, they remain valuable, and we then think it's good to give the DAO more optionality; they can choose to burn these Nouns, or put them on auction again, or grant them to strategic partners, or any other creative idea they may agree upon. Important to note that these Nouns are excluded from DAO quorum and split threshold calculations; they are counted again if and when they are transferred from the treasury. ### How do we protect inactive voters? An idea we like is "split delegation", where an account can say they will split if these other accounts or Nouns choose to split. ### What about a penalty? We think it's best to have zero penalty in order to not leave anything behind for an attacker. We can include an adjustable penalty parameter which can be changed via DAO proposals should the DAO decide to have it > 0. ### Who can signal to split -- Only Noun holder or also delegates? By default it would only be the Noun holder. We don't think delegates should have this kind of power. If needed, for hot wallet kind of convenience, we can design a separate delegation system for this, but that would also add some layer of complexity

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully