Raul
    • 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
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • 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
    • Note Insights
    • 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 Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
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
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Roadmap: from Microtick to DiscoveryDEX After a public submission process to rebrand Microtick, the community decided to change the name of Microtick to DiscoveryDEX. https://explorer.microtick.zone/proposals/16 https://explorer.microtick.zone/proposals/17 The Microtick (DiscoveryDEX) community must move forward and propose and follow a new roadmap to achieve its objectives. We as community should agree and establish the points of the Roadmap. 1. Process to choose the new name (done) 2. Establish a new Roadmap (in progress) 3. Buy domain (discoverydex.io) (done) 4. Agree a new distribution of the supply (in progress) 5. Establish grants a. For new rebrand, image kit, (logo, web development, etc) (in progress) b. Front end development (discovery price & futures) c. Marketing and social management d. Core development and DAO organisation 6. Proposal to reduce to 0% inflation. (done) 7. Proposal to stop the cosoms chain at date 01-08-2022 (done) 8. Communicate it to Community and Osmosis Points to discuss: recently it have appeared a new discussion about move the new DiscoveryDEX to Ethereum-L2, we should take in consideration the two scenarios: ## 2. Establish a new Roadmap for Arbitrium - ETH-L2 (in process) Open for discussion ## 2.1. Agree the new distribution of the supply (tokenomics) for ARBITRIUM-L2 ``` Current TICK: Supply: 1,383,296.26 TICK ``` We can allocate 1:35 of current total supply * X% for current holders * Y% for Core Development * Z% for Crowfunding * Z1% designated to add liquidity. * Z2% designated for Grants, Hackatons, etc * A% for Airdrops (marketing, promotions, etc) We need to assign the % above: * X = 35% (option2: maybe 40%) * Y = 15% (option2: 10%) * Z = 40% (option2: maybe 40% as well) * A = 10% (option2: 10%) ``` Example: Simulation DiscoveryDEX: total supply: 138,329,600 X = 48,415,360 Y = 20,749,440 Z = 55,331,840 A = 13,832,960 ``` ## Plan: from Microtick to DiscoveryDEX As you know, attending the last Governance talks at Discord, the rebranding process affects also the current way to run the Discovery Price App and Market Maker App in the Cosmos SDK Blockchain. The plan for moving from Cosmos to Ethereum involves steps that need to be taken. One of them is stop the inflation to make better calculations from a fixed state about Total Supply and new Tokenomics. Another step is to plan the `microtick-1` chain halt. Before this happens existing tokenholders that want to claim the new Ethereum tokens should move forward and perform some steps. Below is a rough picture of the "Roadmap to Ethereum" as is being discussed. Comments from the community are welcome. ### Plan part 1 1) Create a new validator, a DiscoveryDEX validator with 0% fees. 2) Everyone should stake or restake their tokens to this validator with the 'memo' field set to: `$ETHEREUM_ADDRESS` replacing it by your ETHEREUM ERC20 (not exchange) address. Do not forget the memo field - this is how you register your Eth address as an existing TICK holder! 3) We give one month and half to finalize everyone's decising and then halt the validator. If the stake is > 33% this will halt the chain. 4) The new tokens must be claimed on the ERC-20 contract when it is ready. The new tokens will be tradeable on Uniswap or other Ethereum DEX's after a vesting time (tbd), even prior to the new Discovery DEX smart contract system being ready. ### Plan part 2 1. The crowdsale code must be in the ERC-20 contract when it is launched. 2. A crowdsale of Z% with proceeds going to a multisig DAO address. This will only happen after shutting down the Microtick chain ## Development A whitepaper will be created and released pending completion of the version 2 protocol research, which is currently happening. At this point the Discovery DEX smart contracts will be built and a L2 chain will be chosen. ### High level overview of the upcoming Discovery DEX v2 protocol The new DEX will eliminate the Microtick v1 order book and instead allow market makers to contribute to liquidity pools that will use a bonding curve for the option premium. This removes the need for market makers to calculate premium pricing and leaves it up to the market to determine fair premium. If the bonding curve premium is low with respect to market volatility, takers will buy options to speculate on price movement. This drives the premium price higher up the curve, similar to how uniswap and other AMM DEX's work for token prices. If premium becomes too high with respect to volatility, traders will sell options to capture premium in return for posting collateral. In this way as market conditions change, the bonding curve premium will naturally gravitate toward a fair price. Market makers, once they have contributed to the liquidity pool, can post their price assertions. These quotes do not need to be concerned with volatility the way Microtick currently requires. Trade matching will operate like this: * The taker (both short and long) will always pay or receive the bonding curve premium. * The market maker(s) with the cheapest quotes (the outlying price quotes) will be discounted according to how far they are from the consensus (similar to how Microtick v1 worked). The backing from the marker maker will transfer into a collateral pool for active trades. This will remove weight from the weighted average for those outlying quotes and automatically move the consensus price accordingly. * The difference between the bonding curve premium (taker) and the discounted premium (maker) for individual quotes will be paid as fees into the liquidity pool. In this way the disagreement between market makers on the current consensus price is what generates fees for the liquidity pools. There will be no need for a percentage commission for trades in Discovery DEX smart contracts (although this feature could be built as an option). * The collateral pool will handle the collateral for trades in progress. At the completion of a trade, collateral not payed to the taker as profit is refunded automatically to the liquidity pool. In this way the moving average consensus will track the current price as outliers are matched first, similar to how Microtick v1 worked. However, the complexity of calculating premium is moved to a bonding curve so market makers no longer need to compute premium and submit it with their price assertions. ### Token futures Token futures trading will be built in a separate smart contract system, after the release of the Discovery option pricing AMM. ###### tags: "DiscoverDEX"

    Import from clipboard

    Paste your markdown or webpage here...

    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 has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

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

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    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
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    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

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully