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
    • 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
    • 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 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
  • 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
    ----------------------- **Securing Digital Rights for Communities (Game Theory and Governance of Scalable Blockchains for Use in Digital Network States)** ----------------------- --- # Chapter 3 – The Underlying Principles --- *When it comes to digital freedom, it is principles that matter most, economy is always a counter-intuitive 2nd* ## **Introduction** Most blockchains claim to be decentralised, yet many have fallen short of delivering actual censorship resistance or meaningful digital rights. In this chapter, we explore the fundamental principles that support genuine decentralisation, why it is so hard to achieve, and how certain historical “freak events” accidentally resulted in the correct structural design. We also introduce the concept of the **Petri dish cultivation model**, where an ecosystem evolves organically rather than being “designed” from the top down. --- ## 3.1 Why True Decentralisation Is Difficult ### 3.1.1 Profit vs. Principles Most project leaders focus on profit and convenience. They raise venture capital, pre ordain themselves tokens from the first day of the project in the form of large pre-mines or ICO's, or form legal entities. While these strategies may somewhat help to fund development, they inevitably compromise on decentralisation. Regulators can easily target corporations, foundations, or high-profile founders. For more detail on Pre-Mines and ICO’s, see Chapter 15. “Censorship and the Morality of Pre-Mines” ### 3.1.2 Censorship Resistance is Binary Either your system can be controlled by external parties, or it cannot. If a chain has a headquarters, a known CEO, or a large pre-mined stake in the hands of a few insiders with self-ordained pre-mines or ICO stakes, there are clear points of failure. True censorship resistance requires that no single entity or small colluding group can seize control. ### 3.1.3 Counter-intuitive Choices Many of the decisions that yield true decentralisation look bad on paper. For example, not raising money or not giving a founder a large token allocation seems “unprofitable.” Yet these moves are necessary to avoid creating central points of attack. At almost every juncture, founders who are profit-driven do so at the cost of decentralisation and so undermine censorship resistance. The key is in striking the balance to adequate decentralisation for the application in question. When dealing with digital rights, and maintaining neutral, decentralised layers this means putting counter-intuitive decision choices ahead of profit. ### 3.1.4 Freak Events and Serendipity History shows that blockchains achieving genuine decentralisation rarely follow a neat, logical plan. Often, the original builders did not fully grasp what they had created. In retrospect, the intuitive “right” features that are typically chosen such as certain lock-up periods for founders or adding a centralised treasury turned out to be weak points in future which compromised the neutrality and decentralisation of the community. Repeating a sequence of events that are counter intuitive and principled enough in order to ensure decentralisation and digital rights is extremely difficult to deterministically plan for and orchestrate deliberately. --- ## 3.2 Everyone Did It Wrong Except a Few ### 3.2.1 What Bitcoin Got Right Bitcoin avoided pre-mines, ICO's, and corporate sponsors. Satoshi Nakamoto disappeared, leaving no formal leadership. While Bitcoin’s proof-of-work is excellent for store of value and permissionless access to liquidity, and a permissionless transaction layer for those that can afford fees. Its high fees and limited throughput make it ill-suited for scalable social or governance ecosystems. ### 3.2.2 What Most Proof-of-Stake Chains Got Wrong Many proof-of-stake projects launched with large ICO's, venture backing, or corporate structures. They also adopted high fees and Layer-1 smart contracts (for further information on Smart Contracts see Annex I – Glossary of Terms and Acronyms), creating a “rich-get-richer” environment where governance is dominated by 2 or 3 naturally occurring large staking pools. Over time, these chains tend toward de facto centralisation: a few pools or validators control the system, and regulators can target them. This model is useful however for earning yield where social nuance is not an issue and many DeFi (Decentralised Finance) applications benefit from a financial passive earning system where the one with the largest stake has the most to lose from unfair treatment of users. (For further information on “DeFi” and “Staking” see Annex I – Glossary of Terms and Acronyms) ### 3.2.3 Steem and the Emergence of Hive The Steem Blockchain (later forked into The Hive Blockchain) provides a rare illustration. Steem originally had a “ninja-mined” founder stake controlled by the company Steemit Inc. Unexpectedly, that stake was sold to a high-profile buyer, Justin Sun, founder of the Tron blockchain, sparking a hostile takeover attempt. The community through its DPoS (Delegated Proof-of-Stake – for further information see Annex I – Glossary of Terms and Acronyms) mechanism managed to fork away and create Hive, zeroing out the founder’s stake. This forced event removed the largest point of centralisation and left the chain truly community-owned and operated (See Chapter 11.4 De-Governance for further information on DPoS, See chapter 13.4.2 for more information on forking away from an abusive whale stake). ### 3.2.4 Why The Hive Blockchain Is a “Freak Event” - **Founder Exit:** The principal developer left early, taking minimal continuous control. - **Hostile Takeover:** The attempt to seize the chain triggered the community to unify and fork out the hostile stake. - **No ICO, No VC, No Foundation:** Without a formal entity or large pre-mine, Hive has no single point of regulatory or financial capture. - **Community-Focused Mechanics:** A 13-week power-down (for further information see Annex I – Glossary of Terms and Acronyms) of stake locked for governance dis-incentivises large custodial accounts from staking user deposits, making exchange-led takeovers far more difficult. This prevents exchanges from using custodial stake to vote against the interests of users who have deposited with the exchanges for purposes of trading. Additionally a new, investor has to wait for 30 days in order to carry out governance votes after having staked their tokens to vote. In cases where the stake is large enough to affect the governance of the chain directly, the 30 days gives the community time to find out whether or not the new investor is a benevolent force and will act in the interests of the community before they are able to carry out malicious votes. This also gives the community time to act and take defensive measures where it cannot establish a benevolent intent from the new investor. --- ## 3.3 Petri Dish Cultivation Model ### 3.3.1 The Need for Organic Growth A Petri dish offers nutrients and the right environment, but you cannot force which organisms thrive. Similarly, a censorship-resistant chain must set the right “parameters” (like consensus rules, lock-up times, and governance models) so that a truly decentralised community can take root and expand. ### 3.3.2 Value-for-Value Incentives When participants receive rewards for providing meaningful contributions whether running infrastructure or creating valuable content they build reputations and earn tokens without needing technical credentials or large initial investments. Users with stake earn when they vote on content, these votes direct tokens from a daily communal rewards pool to the content that is voted for. Over time, this democratizes token distribution and reinforces a healthy “middle class” of stakeholders. ### 3.3.3 Voluntary Participation No chain can coerce people to stay. Individuals stay with the community if they see real benefits, like guaranteed speech, secure transactions, fairness, and sustainable token economics. Chains with poor governance, oppressive or extractive structures drive away genuine participants, lose credibility, and remain small or centralised. ### 3.3.4 Hard-to-Replicate Events Forking away from a centralised founder stake or orchestrating a widespread volunteer development effort is extremely difficult and risky. Forks represent delicate moments in the history of a chain where communities can easily fracture due to idealogical disagreements and misalignments. Most new chains attempt to “engineer” a community through funding rounds or marketing. Whereas genuinely decentralised ecosystems often emerge from unexpected crises that unify participants around a single set of core principles. --- ### 3.4 Universal Digital Human Rights (UDHR) ### 3.4.1 Digital Self-Sovereignty True decentralisation grants individuals irrevocable rights to their accounts, data, and tokens. If a chain’s foundation or CEO can be pressured by authorities, it cannot guarantee those rights. Neutral, leaderless systems are what enable globally uniform digital rights. ### 3.4.2 Immutable Speech and Transactions A robust DPoS or similarly parameterised consensus ensures no small group can censor or freeze accounts. By having a predictable, transparent on-chain governance, users know that no arbitrary decision from a corporate board or government office will invalidate their actions. ### 3.4.3 Beyond the Reach of a Single Country When a chain is fully decentralised no headquarters, no corporate registration, no founder stake jurisdictional bans fail to shut it down globally. Any country that outlaws it simply loses the talent and economic benefits migrating to friendlier jurisdictions. --- ## 3.5 Key Lessons of the Required Principles ### 3.5.1 No Single Control Point - Avoid pre-mines, ICO's, or founder stakes. - Do not rely on a CEO or legal entity for development. ### 3.5.2 Parameterised Consensus ---------------- - An example of a parameterised consensus is Delegated Proof-of-Stake (DPoS) with a fixed number of elected validators can offer high throughput and strong security, ideal for social interactions and governance of community social nuance, if carefully designed, since the top validators can be elected and unelected by the community itself. - Long un-staking periods for staked tokens for governance (e.g., 13 weeks), discourage exchanges from powering up custodial user tokens and using them to vote against the interests of the users themselves. ### 3.5.3 Distribute Tokens Broadly - Encourage and distributing freshly mined tokens to non-technical users through rewarding positive, provable social actions or “value-for-value” rewards. - A wide distribution prevents a few insiders from hoarding the majority of supply, leading to a more easily regulatable or corruptible system. ### 3.5.4 Freak Events Often Trigger Real Decentralisation - True censorship resistance has historically emerged from crises: founder exit, hostile takeover, or unexpected forks. - Trying to design a perfect system up front often fails because profit motives have been shown to override long-term security. ### 3.5.5 Censorship Resistance as a Social Phenomenon - Technology alone is insufficient. A dedicated community that believes in censorship resistance and has the tools and social impetus to enact it is crucial. - Reputation-based engagement and transparent on-chain governance foster collective responsibility. --- ## Conclusion Arriving at genuine decentralisation is counter-intuitive and rarely driven by immediate profit. Most chains chose easy funding routes pre-mines, ICO's, large outside investments and now face takeover risks or regulatory capture. History shows that robust digital rights grow from systems that lack a single controlling entity and operate on a truly neutral base layer, forcing communities to self-govern. The **Petri dish** metaphor captures this perfectly. You can provide the right conditions no corporate ownership, fair token distribution, parameterised governance but you cannot fabricate real decentralisation just by declaring it. It requires a community voluntarily standing behind censorship resistance and self-sovereignty, with the right digital tools, often galvanized by crises or unexpected forks. In the chapters ahead, we will detail how to maintain these principles technically and in practice, examining the deeper mechanics of consensus design, token distribution, and ongoing governance models that reinforce genuine network autonomy. Only by embedding these ideas deeply into the chain’s structure can we realize universal digital human rights that no centralised force can override.

    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