starkerz1
    • 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
    ----------------------- **Securing Digital Rights for Communities (Game Theory and Governance of Scalable Blockchains for Use in Digital Network States)** ----------------------- # Chapter 22. DAOs and Community Proposals for Self-Funding *Neutral funding removes compromise and maximises the neutrality of the tech* ## 22.1 Decentralised and Neutral Funding A major advantage of properly designed blockchain ecosystems is the ability to fund projects through truly decentralised, neutral mechanisms. Unlike traditional ventures or ICO's with centralised teams and venture capital, these models allow a community-owned treasury to fund ideas and community projects without a controlling entity or CEO. Community members vote on proposals using their stake, and once a proposal meets a threshold, funds are released on-chain to the developer or group that will perform the work. In a truly neutral environment, there is no single legal entity, foundation, or board that dictates funding. Instead, participants stake their tokens for voting power, propose initiatives, and decide on projects that add value to the network. The key benefit is that funding does not come with the usual "strings attached" seen in centralised or venture-backed deals. Rather, it aligns community incentives toward shared goals. ## 22.2 What Is a DAO? A Decentralised Autonomous Organization (DAO) is a community-governed treasury and decision-making structure on a blockchain. It generally has: - **On-chain funds**: Often funded from newly minted tokens or fees. - **Proposal system**: Projects request funding by submitting proposals. - **Stake-weighted voting**: Token holders cast votes. If a proposal meets the required threshold, funds are released. A genuinely decentralised DAO has no outside venture capital dictating decision makers. It has no single company or CEO that can override votes, and no foundation controlling funds. Instead, the community's stake decides how to allocate resources. ## 22.3 Decentralised vs. VC-Backed DAOs Many DAO's appear decentralised but are, in reality, influenced or controlled by large venture capital allocations ordained or obtained far below market price at a pre-mine stage early on in the project, often before the tokens are traded on the open market. These VC's can concentrate voting power, leading to outcomes favourable to a few stakeholders rather than the entire network. Venture Capital firms also usually reside in "regulation friendly" jurisdictions, making them prone to regulatory pressure that can significantly shape funding decisions. In contrast, a truly community-driven DAO has widely distributed tokens, no pre-mine, no ICO, and no single party holding a controlling majority stake. The ideal scenario and balance is where, even without the votes of the largest stakeholders, projects can still obtain funding via obtaining votes from the rest of the community. These are the rare DAO's that cannot be easily shut down, coerced, or dominated by external investors. Their funding decisions reflect actual community interests rather than extractive-driven agendas which do not necessarily serve the community. ## 22.4 Returning Value to DAOs Because these DAO-funded projects do not have strings attached from corporate entities, it is crucial for the community to establish accountability: - **Milestone-based releases**: Funds are released only after certain goals are achieved. - **Monthly or phase payments**: Ongoing work (e.g., maintenance) is funded incrementally, with the community free to remove votes if progress stalls. - **Open bidding**: The community can publish desired tasks, inviting multiple bids. Stakeholders then vote on the most competent developer with the fairest price. The community expects projects to benefit the ecosystem long-term. A neutral DAO often funds tools or protocols that enhance network utility (for example, off-chain storage, social features, or scaling solutions). The team's reputation is on the line: if they fail to deliver, future proposals are unlikely to pass. ## 22.5 Example: The Hive Blockchain Decentralised Hive Fund (DAO) and SPK Network On The Hive Blockchain (a text-based storage layer), the SPK Network received funding from Hive's decentralised proposal system to build off-chain media storage. SPK's work benefits Hive users who want to store large files (videos, images) beyond the scope of the base chain. In return, SPK gains community recognition and support but has no direct "contract" with a corporation. In return for this, the project dropped its mining tokens to the entirety of the Hive community in a claim drop. The users who claimed tokens are able to mine more efficiently in the network and therefore earn the network's governance token for providing infrastructure operation. Due to DAO funding, there was no need for a pre-mine or ICO to fund the project, and therefore the SPK Network has a highly neutral layer that protects the rights of users and their content storage. The community can stop funding at any time if deliverables fall behind or if the project ceases to align with Hive's goals by un-voting the proposal and dropping its total votes below the community set threshold of votes required to receive funding. This model shows how a community can sponsor critical infrastructure without relying on ICO's, venture capital, or centralised companies. It aligns incentives around expanding the chain's ecosystem while preserving user ownership and governance. ## 22.6 Alternatives to "No Strings Attached" Funding A common concern with "free" funding is that teams could run off with the money. DAO's mitigate this by: - **Clear scopes of work**: Publicly outline tasks and deliverables. - **Reputation and trust**: Developers who leave projects incomplete damage their standing, making future funding unlikely. - **Revocable votes**: If a project deviates from its stated goals, community members can un-vote their support, temporarily or permanently halting further payouts. These checks protect communities from severe losses and ensure ongoing alignment. The outcome is a more transparent, flexible funding environment that encourages collaborative development. ## 22.7 Why Neutral DAO Funding Matters - **Eliminates Venture Capital Control**: No massive early allocations or pressure to chase short-term profit. - **Scales Through Collective Effort**: Communities that must fund and maintain the chain themselves learn to optimize and reduce bloat. - **Resists Regulatory Capture**: Without a centralised owner or foundation, a decentralised treasury cannot easily be forced to censor or comply with unfavourable rules. - **Protects Against "Exit liquidity" Behaviour**: Teams funded by neutral DAO's are less likely to dump tokens or pivot abruptly because they rely on continued community approval and can be dropped governance or mining tokens in exchange for DAO funding, excluding the need for bringing in Venture Capitalists whose values and reasons for being involved in the project may not align with those of the community. - **Promotes True Decentralisation**: Everyone with stake can contribute ideas and vote, reflecting widespread consensus rather than corporate edicts. Projects developed under this model become genuinely community-oriented. Their tokens have higher community trust because there is no hidden pre-mine or venture round waiting to sell into unsuspecting community members at higher prices. As a result, DAO's with a broad, participatory user base produce ecosystems that are more censorship-resistant, equitable, and sustainable in the long run. ## 22.8 DAOs are Always More Centralised than the Witness Pool Community members that vote for Witnesses often do not also partake in DAO voting to fund projects. Fewer people vote in DAO proposals since new funding proposals are submitted on a regular bases and are more difficult therefore for the whole community to keep track of when compared to voting for Witnesses which evolves much more slowly over time. The result is that whale votes in DAO voting is more extreme than in Witness voting and DAO’s can often seem more centralised than the Witness voting distribution. This is because the influence of one whale in the consensus Witness when voting along side a vast majority of the community seems less significant when compared to that same vote when compared to the fewer number of participants that vote in DAO funding proposals. This may lead to accusations of DAO’s being centralised as it is often the case that one whale can sway a community decision on whether or not something is voted above the voting threshold for funding. There are two key things to remember here: 1) That the Witness voting remains decentralised when the voting tokens are well enough distributed that one whale cannot vote to manipulate and decide the top Witness pool such that your fundamental rights to transact and grow community on chain is no longer preserved. If one whale can vote in a super majority of the witnesses then the Witness voting mechanism is centralised and highly corruptible. 2) Should a situation arise whereby the voting threshold for funding is voted so high by the community that only whale can decide which proposals get funded and which don’t, while this is not an ideal situation, it does not mean that the base chain is centralised. Ideally there should not be a situation when only one member of the community can have a vote strong enough to elect proposals past the voting threshold for funding. Proposals should be able to be elected into funding without the vote of the largest voter on chain. Times where situation 2) may benefit the chain is when: a) the largest voter feels that a proposal is not legitimate and is an attack on the chain and that community members have been mislead into believing a proposal is genuine, when in fact it is an attempt to drain the DAO’s funds and, b) when a collective of users feel that the chain is spending from its DAO beyond its means to sustain such spending and so drastic measures are needed to increase the voting for funding threshold high enough that only the largest voter can put proposals into a position where they exceed the voting threshold for funding. The result is that spending from the DAO is vastly reduced. Scenarios a) and b) are however highly controversial situations and should only be temporary if at all, until such a time as the attacking proposal is removed, or until spending is bought into control. Should this situation continue past either of these points, then the community should find diplomatic ways to ensure that the largest voter on chain de-escalates and allows money to flow based on decentralised community decisions again. Neither of these scenarios however mean that the blockchain itself is centralised. Only that there are extreme or edge case scenarios whereby one of the funding distribution mechanisms (the DAO) can potentially be decided by one user for a temporary period when it is justified. The community itself can however collectively influence the whale in question to de-escalate prematurely if there is enough social consensus against the action taken.

    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