Julio Linares
    • 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
    Authors: Apriori (Anoma) & Ajmaq (CirclesUBI/Entropy) In this piece, we would like to argue how we can *solve* the problem of MEV or the Maximum Extractable Value that is structurally inherent to different consensus algorithms in blockchains (particularly POW and POS) by using Universal Basic Income as an intent-centric protocol via Anoma and CirclesUBI. Intent centric architectures are becoming the new buzzword in crypto-town, particularly in Ethereum, but few truly understand what intents really are, and the role that solvers play in matching user intents. What if we could redistribute the value from mining, staking and solving that is extracted back to users via a universal and unconditional basic income? In order to argue for this, we first have to define what we mean by all these mouthfuls. To paraphrase the great Daoist philosopher Zhuang Ze, words are useful to understand the meaning of things, but what truly matters is the meaning. Please stay with us while we dwelve on the meaning of these things. First, some definitions. What is MEV? MEV stands for "Maximal Extractable Value" and refers to the maximum amount of profit that can be extracted by miners or other participants in a blockchain network through transaction ordering and other activities. MEV is created when miners or other participants use their power to prioritize transactions in a way that benefits them financially, such as by including their own transactions or those of others who pay them higher fees. MEV is inherent in all consensus algorithms that rely on transaction ordering, including Proof-of-Work (PoW) and Proof-of-Stake (PoS). However, it is more prevalent in PoW algorithms (what Bitcoin uses), where miners have more control over transaction ordering and can use their computational power to extract greater MEV. In contrast, PoS algorithms (what Ethereum transitioned to) typically have a more deterministic approach to transaction ordering, which can limit the amount of MEV that can be extracted relative to PoW. What is UBI? Unconditional Basic Income (UBI) is a periodic cash payment unconditionally delivered to all on an individual basis, without means-test or work requirement. The Basic Income Earth Network defines UBI as "a periodic cash payment unconditionally delivered to all on an individual basis, without means-test or work requirement." This means that every person, regardless of their income or employment status, would receive a certain amount of money regularly from the government or other institution. The purpose of UBI is to provide a basic level of financial security and freedom for all individuals, allowing them to meet their basic needs and pursue their own goals and interests. Now, the caveat here is that, since we are talking about crypto, payment in cash is not really an option, or at least not a direct option. When we speak about crypto-powered UBI, we are generally talking about two types of systems. The first one, is digital-asset based UBI, where users receive an Airdrop of an asset that has a limited supply overtime. The benefit of this approach is that users receive an asset that they can convert into cash. The downside is, because of fluctuating prices and limited supply of tokens, the value of a digital asset based UBI is not constant and it largely depends on people pumping up liquidity to the token, financial speculation and the amount of users involved, as was the case with Proof of Humanity's $UBI drip and is now the case with the controversial project Worldcoin, which scans people's eyeballs in exchange for a token. This type of approach is in line with how much of crypto-assets behave, which we could also call a form of "commodity money", in the sense that there is an assumption that the tokens have somehow intrinstic value. The second type of system is the crypto-credit based UBI, where people receive tokens that represent promises that can be used to pay for goods and services. The benefit of this approach is that users receive tokens that that they can use to go in and out of obligations with others who are willing to accept their credit tokens in exchange for stuff of value. The added benefit here is that the credit system is stable means of settling payments, which is useful when engaging in real life trade. The downside is, because these systems rely on network level effects for bootstrapping, if you're not in a place where people are not actively using it, the credits cannot be activated. This is the case with CirclesUBI, a system where everyone who joins receives 1 crc per hour, which is mostly only being used in a larger scale in specific localities, like is the case with the ongoing Berlin pilot or the recently started Bali pilot. Similar projects in the crypto-credit space could include the Trustlines protocol, albeit they do not claim to be a UBI project. For any of these projects, one can and should make the case of saying "Is this really UBI?". To what extent can we really claim that these projects are able make a system that allows people to "provide a basic level of financial security and freedom for all individuals, allowing them to meet their basic needs and pursue their own goals and interests". As it stands, it feels like both approaches are incomplete. What we need to do is to create a system that can combine the best of crypto-credit with the best of crypto-assets to bring forth a system that is better than the sum of it's parts. In the following sections we will explore how such a system could be brought into being. What are intents? According to Paradigm, intents are: “an intent is a signed set of declarative constraints which allow a user to outsource transaction creation to a third party without relinquishing full control to the transacting party”. You may have noticed that in the definition above, there is the word "declarative". As the author of this piece argues, the difference between the current paradigm in blockchains and the dawn of the new era that intents bring is the difference between How and What. Transactions say How a given user wants a transaction to happen whereas in an intent-centric universe, users ask for what they want and do not care this happens. In other words, users are declaring what they wish to exchange (I want Eth for Dai), whereas in current smart contracts you have to specify how this will happen, which leads to the UX/UI nightmares that keep us awake at nights. Anoma is spearheading the latest innovation in blockchains by creating a whole series of systems and sub-systems that are intent centric by design. Anoma's declarative post-smart contract logic not only brings elegance in how we interact with cryptographic systems, it has the potential to revolutionize how we do trade, all while keeping user's privacy. To explain how this happens, we now have to turn to solvers. What are solvers? A Solver a machine that runs a software program that uses algorithms to solve complex problems. Solvers can be used to find optimal solutions to mathematical equations, optimization problems, and other types of problems. A solver network uses algorithms to match user intents with the appropriate solution. It works by analyzing user input, identifying the intent behind it, and then matching that intent with the appropriate solution. This type of solver network is commonly used in chatbots and other conversational interfaces to provide accurate and relevant responses to user queries. Redistribution of MEV using CirclesUBI One possible method for distributing MEV-generated funds back to Ethereum or any blockchain users could involve the use of smart contracts that automatically distribute a percentage of the funds to all Ethereum wallet addresses on a regular basis. This could be achieved by creating a smart contract that calculates the total amount of MEV generated over a certain period (e.g. a day, a week, or a month) and then distributes a portion of that amount to each wallet address based on its proportionate share of the total number of Ethereum tokens held. For example, if the total amount of MEV generated in a week was 100 ETH and there were 1 million Ethereum wallet addresses holding a total of 100 million ETH, each wallet address would receive 0.001 ETH (i.e. 0.1% of the total amount generated) as an unconditional basic income. At current prices, that would be 1.82 USD for 1 million people in one week. This method could be used with the CirclesUBI protocol by integrating it into the existing Circles network. Circles is a social payment protocol that allows users to create and exchange their own digital currencies. By integrating MEV-generated funds into the Circles network, users could receive an additional stream of income in addition to their existing Circles currency. In addition to providing an unconditional basic income for Ethereum users, MEV-generated funds could also serve as a liquidity injection for businesses within the CirclesUBI network. By integrating MEV-generated funds into the existing Circles network, businesses could receive a steady stream of income that could be used to fund operations, expand their offerings, and attract new customers. For example, businesses could receive MEV-generated funds as a separate token within the Circles network, which could then be used to purchase goods and services from other Circles users or exchanged for other currencies. This would provide businesses with a reliable source of income that could help them weather economic downturns and grow their operations over time. Moreover, the integration of MEV-generated funds into the CirclesUBI protocol could also encourage businesses to adopt more sustainable and socially responsible practices. By receiving a portion of their income from MEV-generated funds, businesses would have an added incentive to prioritize environmental sustainability, social responsibility, and ethical business practices. The use of MEV-generated funds as a liquidity injection for businesses within the CirclesUBI network could help promote economic autonomy at the local level where Circles communities thrive while also fostering a more equitable and sustainable economic system. ## New Public Goods Funding Mechanism Let's think through a new design for funding public goods on Ethereum. Today the majority of MEV in a given block is sent by the builder to an Ethereum block proposer of the current slot. The builder bids a portion of the MEV in their block in order to have their block accepted by the proposer over those of competing builders. ![](https://hackmd.io/_uploads/rJEcggy3h.png) Instead of MEV going to the proposer or being burned, MEV could be sent to a contract on Ethereum which would accumulate realized MEV to be redistributed at a later time, for the purpose of funding public goods. Thereafter a public goods developer would submit a request for public goods funding by submiting proof of a minimum viable public good. This proof would act as an oracle update to the contract such that if the contract's conditions are satisfied, it releases a portion of the accumulated MEV to the developer. The goal of funding that developer would be to build an application or infrastructure for the Ethereum protocol. ![](https://hackmd.io/_uploads/ByPnge1h3.png) To further enhance this redistribution mechanism, there could also be a requirement that a particular public good MVP must first be funded by an existing DAO grant. The DAO would in turn vote to determine if the MVP meets the criteria set out in the grant funding round. If satisfactory, the DAO vote would trigger an Oracle update to the MEV contract on Ethereum which then sends funds to the developer's wallet. If the DAO rejects the MVP proof as sufficient for funding then the portion of MEV going to the developer could either be burned or continue to accumulate for future redistribution allocations. ![](https://hackmd.io/_uploads/rJ0ygekhh.png) In such a design, the accountability and filtering logisitics are determined by individual DAOs who are incentivized to fund initial grants. It is not unlikely that developers would build public goods that compliment a particular DAO's goals. ### Weaknesses There are a several weaknesses to this approach. - DAO governance is easily corrupted - Funding biases - DAOs do a poor job in advertising/managing the program - No privacy, could force developerss to dox or reveal more information about themselves than necessary - Adversarial MVPs that fool DAOs (either AI or malicious actor) - [Dark DAOs](https://hackingdistributed.com/2018/07/02/on-chain-vote-buying/) who collude to influence grants results ### Advantages The primary advantage to this design is that Ethereum governance can remain credibly neutral; in the sense that base layer governance only needs to agree to redistribute MEV but not decide what to fund. The advantage to the proposed funding mechanism is that it encourages the emergence of public goods funding DAOs whom compete for talent with compelling grants programs. Indeed these DAOs could also specialize in building relationships with existing developers in the ecosystem who could facilitate team creation. The proposed redistribution mechanism would have the added benefit of bringing legitimate value to governance tokens as ownership of such would grant funding power to token holders. If there is an incentive to form DAOs then the tooling and infrastructure will also improve. This program could also incentivize young developers not to work in Web2/tradefi and reduce pressure on existing developers to seek venture funding as a means of survival. ### Conclusion This strawman funding mechanism could remove the need for outsized venture capital funding in the Ethereum ecosystem. The protocol itself could capture MEV and use it to grow Ethereum's [infinite garden](https://ethereum.foundation/infinitegarden).

    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