spartacusvoid
    • 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 New
    • Engagement control
    • Make a copy
    • 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 Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Compensation for xToken Hack ### Purpose With the goal of retaining early project supporters, capital, and achieving a stronger community, this proposal seeks a fairer restitution for victims of the recent xToken hacks, resulting in $25m in losses. The current Team proposal offers 1% of XTC supply, a current market value of $2.5m, vested over 1 year. This proposal reflects a consensus view from victims: a fair restitution would be 2% of XTC supply, vested over 1 year. ### Fair restitution The expectation of fair restitution, when possible, should be an insurance policy for users of early stage protocols. New protocols, like xToken, are high-risk ventures. Of course this is understood and the high APYs are to help compensate this risk. But project communities, and the teams behind them, can be more attractive by adopting a social contract involving the expectation that losses resulting from hacks be answered with reasonable compensation. The pre-hack market valuation for XTK was ~$500m FDV. This valuation could be restored if trust, capital, and community were bolstered and interests aligned around ensuring a successful future for the xToken project. The $25m lost is around 5% of this prior FDV. 2% restitution is a fair compromise between the fault of the project resulting in the loss of funds, and the inherent risk participants should have expected. ### Current xToken Team Proposal | What | Team | | -------- | -------- | | Total XTK Supply| 1,000,000,000 | | 1% XTK | 10,000,000 | | Total Funds Lost | $25,000,000 | | XTK per USD Lost | 0.40 | | FDV to Break Even | $2.5b | | Example Funds Lost | $5,000 | | Example XTK Restitution | 2,000 | ### Fair Restitution Proposal | What | Value | | -------- | -------- | | Total XTK Supply| 1,000,000,000 | | 2% XTK | 20,000,000 | | Total Funds Lost | $25,000,000 | | XTK per USD Lost | 0.80 | | FDV to Break Even | $1.25b | | Example Funds Lost | $5,000 | | Example XTK Restitution | 4,000 | ---- **APPROACH #2 : I wrote out a quick draft here earlier based on what I read from others but then got pulled away by work:** We propose that we invest 2.5% of the "Community Vesting" XTK reserves into reparations for the victims of the 5/12/2021 hack. This would have two vesting periods: *1.5% vesting over the first year, and 1% vesting over the 2nd year* **What's the ROI? Why is this a better use of the reserves than other options?** *Members of the community appreciate the team's response and handling of the situation so far, but many have voiced that the 1% is lower than expected or hoped for, given the size of the losses. We believe that 2.5% would feel more commiserate to the size of the losses for the LPs, which would help retain users, strengthen brand value/trust, and foster long-term community. While there's a lot of appreciation potential for XTK and we fully expect XTK's price to reach $2 or more in the future, that doesn't account at all for the opportunity cost of the losses today (ETH, SNX, BNT) likely also being worth 2-3x more in 1 year. Which is why we believe 2.5% would be more appropriate.* *By providing 2.5%, I think a lot more of us would walk away being stronger supporters and continued users of xtokens. We think of it as a long-term investment in community that's higher ROI than saving an additional 1.5% of XTK for future community emissions programs. This is also a long-term investment in xtoken's reputation in the Defi community, which is a small world and word travels fast.* **Why 2.5%? Why over 2 years?** Before the hack, the FDV was ~$500m. The ~25m loss is ~5% of this. Splitting the difference (~2.5%) and vesting it over the long-term (2-years) feels like a more equitable approach to affected LPs, driving long term community engagement and loyalty. **What are the negative tradeoffs? Is it still worth doing this despite these risks?** Risk #1 - we are using up too much of the reserves There is still plenty of XTK in reserves (e.g., Community Vesting portion started with 50% and likely has more than 35% available for future incentives). We believe the spirit and outcomes of providing this would align with the Community Vesting portion's goals, and this still leaves the vast majority of emissions incentives untouched Risk #2 - this will negatively impact XTK price Given that this is being vested over 2 years, that should minimize most of the negative price action. Of course this will still have some increased selling pressure, but we believe in the team's ability to execute and by that point, XTK's brand, market cap, and value will grown a lot, resulting in fewer sellers and more liquidity to absorb any selling.  One way of mitigating this if needed is to add a 6-month cliff, so that the first investment doesn't occur until later **We wanted to share this perspective on behalf of the community. We have seen that you always value the community's perspective, so we hope that you may reconsider the 1% investment as you see this increased feedback from us.**

    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