HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • 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
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    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
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # GnosisDAO x DXdao Mesa IDO suite agreement ###### tags: `DXdao` `Mesa` `GnosisDAO` GIP: <to be assigned> title: GnosisDAO x DXdao IDO suite agreement author: Martin Krung, DXdao (@martinkrung/mk@cryptonative.ch), Alex, GnosisDAO status: Draft type:  Meta created:  2020-12-09  [ToC] ## Simple Summary This proposal is to formalize the ongoing relationship between GnosisDAO and DXdao for the IDO use case. ## Abstract Gnosis/GnosisDAO is creator of Gnosis Protocol (GP V1) which has been designed as a batched ring-trade decentralized exchange, but found mainly traction to be used in IDOs. DXdao is currently running mesa.eth, a front-end to Gnosis Protocol V1. DXdao plans to build a product suite with different IDO mechanisms for different needs starting with "easyAuction" from GnosisDAO. Mesa has the potential to grow to a open platform where different mechanisms implementor provide token sale mechanism. Both organizations have a working relationship with Mesa/GP V1 and Omen. ## Motivation A collaboration between the two DAOs would be beneficial to leverage each DAO's strengths and to build a dedicated product for the found product-market fit of Mesa/GP V1. The workload should be shared equally between the DAOs. The DAOs split the responsibilities in the following way: **GnosisDAO** - Design the mechanism/ smart contracts with the product requirements from the DXdao - Audit the contracts - Provide the code for the prototype of the front-end **DXdao** - Provide additional product requirements - Develop UX after prototype stage and host the actual interface - Customer support for projects doing IDO - ?End-user support (In consultation with the customer)? **Shared duties** - Customer acquisition for IDO - Innovate the IDO use-case ## Specification A protocol fee will be applied at protocol level. Fee will be a percentage of the token pair in the sale. This fee will be split equally to both organization.  Fee level should be competitive enough to attract costumers and allow the organizations to cover the cost. Directly after the sale, the earned fee is moved to a swapr pool and acts as first trading venue for the pair. ?Both DAOs are free to charge extra services cost for specific IDO? ***(mk):*** If we want to build a moat by doing building services around the IDO usecase this is work which is not going into the product itself. e.g if we are doing end-user support for the IDO project this could be charged extra. ?This agreement is limited to 2021?2020 and can be renegotiated anytime if both parties agree? ## Rationale **Size of the fee** Has to be discussed in depth. ***(mk)***: I think its not wise to open a price discussion with every project. We should implement this on protocol level, not on IDO level.  My experience from my years owning a small business: you have to set a standard. Most costumers will accept the price set, but they are free to ask us for a discount or pay-back.  We start with a decent fee because lower the fee will be not a problem, but raising is not very well-received.  A fee triages serious costumers from freeloaders. Freeloaders generate a lot of noise but do not help us in any way and even may be a reputation risk. I propose to set the inital fee to 1.5%. High, but bouncer has 1.5% and we have got a reputation, and they are allowing permissionless IDO for shitcoins. (project doing ICO payed up to 10% for a token sale) For API3 with a 1.5% would have been ($23m *  0.015% is 345'000, nice but if you set a 100K wage, then you get ~3 years of work) **Move earned fee as liquidty to Swapr** At the end of the auction, the earned fee on the IDO pair is forward to a new created swapr pool. This allows instant trading after the sale closes. Because we are both DAOs and treasury management is slow, this should be done by the smart contract. Benefits - The IDO project having a instant working market - swapr having the chance ending up as the first and deepest pool of new traded coins - This benefits DXdao and GnosisDAO earn trading fee on the trades. Because liquidity is thin and trading volume high, trading fee in early hours of a pool can be quite high. - We can't sell the fee into the open market anyway. IDO Projects would not like the additional sell-pressure. ## Implementation **Fee** Implement protocol fee on protocol level on the sale pair. Inital fee level is set to 1.5%, but should be changable on protocol level.  **Move earned fee as liquidity to Swapr** ``` Pseudo Code: migrateToSwapr()     test if pool exists:         send fee to DXdao Treasury and GnosisDao     else:         create new swapr pool with token ratio of closing price         recive LP Token         send created LP Token to DXdao Treasury and GnosisDao ```

    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 lost 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?

    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

    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

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    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

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    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. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        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
        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