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
      • 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 Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync 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
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 10. Bridge to Decentralised Governance *Why Effective Consensus Mechanisms Are Essential* --- ## **Introduction** Every blockchain, no matter how it’s structured, ultimately needs a way for people to *agree* on what the chain’s rules are, how to update them, and who owns which assets. This process of collective decision-making often called “governance” is how a decentralised project remains stable and evolves over time. In practical terms, governance answers questions such as: - How do we decide on changes to the protocol, like bug fixes or new features? - Which individuals or entities have a say in these changes? - How do we resolve conflicts when the community is split on major issues? Understanding *why governance matters* and *what forms it can take* is crucial for anyone interested in building or contributing to scalable blockchains that uphold genuine digital self-sovereignty and censorship resistance. --- ## 10.1. What Is Decentralised Governance? **Definition** Governance is the process by which a community makes decisions about shared rules and resources. In a blockchain setting, these shared resources include the digital ledger (the record of all transactions) and the underlying software (the protocols that define how transactions are processed and validated). **Consensus as the Foundation** Because blockchains distribute data across many computers worldwide, there must be a *consensus mechanism* a way for all participants to confirm the state of the ledger (historical data, current balances, etc.). Governance is the umbrella under which this consensus mechanism operates, ensuring everyone agrees on not just daily updates but also fundamental protocol changes over time. **Why You Cannot Avoid It** Some projects claim “no governance” or “governance-free” systems. However, *any* distributed database that requires updates whether bug fixes, performance improvements, or new features relies on humans to come to an agreement. This agreement must be structured in a way that is as decentralised as possible, or else the system risks being dominated by a small group. --- ## 10.2. Why You Need Governance in Decentralised Systems **1. Resolving Protocol Updates** Blockchains are not static. They need software upgrades, security patches, and new features. Governance decides *how* and *when* to implement these changes so that the chain can grow without abruptly splitting the community or becoming vulnerable to attacks. **2. Handling Emergencies** When crises arise such as hacks or hostile takeovers communities must act quickly to defend the network. Governance mechanisms allow participants to coordinate a response, possibly “forking” (copying and modifying) the chain to exclude an attacker’s influence or fix a critical bug (See chapter 13.4.2 for more information on forking away from an abusive whale stake). **3. Funding and Collective Projects** Fully decentralised blockchains often rely on some form of on-chain funding (like a DAO) for development, community initiatives, and infrastructure. Governance determines who receives that funding, on what terms, and how to track accountability. **4. Maintaining Long-Term Vision** Without a structured process, short-term profit motives can overshadow the chain’s long-term mission of free speech or censorship resistance. Proper governance gives the community a voice, preventing a single founder or entity from unilaterally controlling the chain’s direction. --- ## 10.3. Data Availability and Agreement **Data Availability Layer** A blockchain’s “data availability layer” stores all the historical records transactions, smart contract states, social posts, etc. These records must be reliably accessible worldwide. If only a handful of nodes retain full history, the system becomes centralised and prone to data loss or manipulation and decentralised governance becomes compromised. **Distributed Around the Globe** To remain censorship-resistant, multiple independent operators (often called validators, witnesses, or miners) hold copies of the ledger. This distribution ensures no single party can erase or alter historical data without everyone noticing. If one server goes offline or gets compromised, many others still have the verified history. **Coming to an Agreement** Every time new information is added like a batch of transactions these independent operators must *agree* on its validity. They use consensus rules (e.g., Delegated Proof-of-Stake, Proof-of-Work, or another protocol). Governance is the higher-level process that can tweak or overhaul those consensus rules if needed, but only with broad community support. --- ## 10.4. Forms of Consensus and Voting **All Systems Have Consensus** Regardless of ideology be it coin voting, node infrastructure voting, or something else a blockchain must converge on a single “truth” about who owns what. This single truth emerges from a *vote* of some kind: - *Coin Voting:* Users stake tokens to influence upgrades or select block producers (traditionally known as Proof of Stake or PoS). - *Infrastructure Voting:* Users with specialized hardware or reputations decide the chain’s next block (traditionally known as Proof of Work or PoW - for further information on PoW see Annex I – Glossary of Terms and Acronyms). - *Reputation or Hybrid Systems (Parameterised Coin Voting):* Some networks might incorporate identity or other parameters to weight votes (Known as Delegated Proof of Stake (DPoS)). **Parameterising On-Chain Governance** No single voting method is perfect. For social Networks and Network States, the art of governance lies in *parameterising* how votes are cast and counted. This allows for social nuance to be built into the community decision making process. An example, of a parameter put on voting maybe where a chain wants to prevent large exchanges from dominating the voting with custodial stake that it did not earn itself. The blockchain might require a long un-staking period (e.g., 13 weeks) before someone can use newly acquired tokens for governance. These parameters can drastically change the power dynamics within the network. --- ## 10.5. Potential Governance Models **1. One Token, One Vote** - *Pros:* - Aligns influence with financial stake; people who invest more have a bigger say. - Collateral Provision Accountability - the user with the most tokens also has the most to lose if being used in a collateral provision or DeFi system - *Cons:* - Wealthy participants can accumulate disproportionate control, risking centralisation. **2. One Account, One Vote** - *Pros:* Every user with an account is treated equally, in principle. - *Cons:* Difficult to enforce; requires identity verification that can reintroduce central control. Newly joined, uninformed users have the same weight as long-term contributors, and it’s prone to “bot-farm” attacks, if not carefully managed, where one user can control multiple accounts. **3. Reputation-Based Voting** - *Pros:* Encourages long-term commitment and trust-building. People who add proven value over time gain more say. - *Cons:* Hard to quantify reputation objectively, and might still require coin or identity layers for synergy. **4. Hybrid Approaches** - *Pros:* Combines financial stake, reputation, and possibly time-locked tokens (like a power-down period) to balance power distribution. - *Cons:* More complex to implement and explain. Possibly confusing for newcomers, but can address many pitfalls of simpler models. **5. Top Elected Infrastructure Operator Voting** Many DPoS chains, in order to take into account social nuances of communities elect their top 20 validators (or witnesses) who run the software of the chain. They elect them usually using stake weighted voting. These witnesses then become social representatives of the community, running only the code that they are elected to represent. This code contains all of the governance systems that best reflect the communities values. See chapter 11.4 for further details on top witness voting --- ## 10.6. Governance and the Human Element **Social Coordination Is Key** Even the most elegant on-chain mechanisms ultimately rely on *human* agreement. If a large fraction of the community rebels against a proposed update, they can “fork” the chain. Technology does not settle disputes; it only provides pathways. People must use those pathways wisely. **Reputation and Trust** Successful governance also hinges on intangible social factors like reputation. Leaders who have consistently acted in the network’s best interest earn community trust over time. At crisis moments, such leaders can guide the network to fork or adopt specific policies. Without this social cohesion, governance devolves into chaos or central authority. --- ### Conclusion Governance in a decentralised blockchain isn’t an optional add-on; it’s the backbone that coordinates consensus, updates, and community direction. Even if a project tries to minimize “human decision-making,” it still depends on individuals to maintain code and respond to emergencies. Recognizing that *all distributed systems require some form of structured governance* is the first step in building blockchains that remain truly open, censorship-resistant, and capable of scaling into digital Network States. **Key Takeaways** 1. **Governance Underpins Consensus:** Whenever multiple nodes hold the ledger, they need a method to agree on updates and fixes. 2. **No “One-Size-Fits-All” Voting:** Different chains use different models (coin stake, node infrastructure, reputation). Each has strengths and weaknesses. 3. **Parameters Shape Power Dynamics:** Lock-up times, voting weights, and reputation scoring can prevent unhealthy centralisation. 4. **Human Community Is Inseparable:** Technology alone does not ensure freedom. Dedicated people defending open source, decentralised processes are vital. 5. **Crucial for Network States:** As communities evolve into full-fledged digital sovereignties, robust, social nuanced governance becomes the cornerstone of self-rule and stability. By grasping these governance fundamentals, communities can design systems that genuinely live up to the promise of decentralised power resisting censorship, welcoming newcomers, and fostering the trust needed to build entire online nations.

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