Skip to content

Latest commit

 

History

History
58 lines (47 loc) · 7.51 KB

Decentralized Protocols.md

File metadata and controls

58 lines (47 loc) · 7.51 KB

Decentralized Protocols

  • Decentralized protocols become fat protocols.
    • On the internet, the main protocols take care of communications (HTTPS, SSH, ...) and apps are built on top. These apps and services store our data in silos. These protocols are necessary but not valuable. Value is captured by the apps.
      • A great example of a modern open source protocol is [[IPFS]].
    • Fat protocols contain the data. With open protocols and decentralized data ([[Decentralized Web]]), apps are only the frontend of the services.
  • Protocol and Open Source Funding. It'll add to the current ways to to fund open source projects:
    • Consulting: open source the code, sell consulting.
    • Cloud: open source some code, but sell a closed source cloud complement.
    • Community: open source all code, and issue a token or charge for access to the community.
    • Open Source projects would have a protocol. You could buy shares of Kubernetes, Tensorflow, ... or contribute to gain tokens. This [[incentives]] contributing and helping people.
    • Many more!
  • Tokens create new, scoped economies, and those economies enable new ways of organizing production and operation of goods and services. Because these economies are programmable, they can also embed and optimize for value systems and goals.
  • Moving to protocols, not platforms, is an approach for free speech in the twenty-first century. Rather than relying on a "marketplace of [[ideas]]" within an individual platform — which can be hijacked by those with malicious intent—protocols could lead to a marketplace of ideals, where competition occurs to provide better services that minimize the impact of those with malicious intent, without cutting off their ability to speak entirely.
    • The fundamental power of the internet is its interoperability. It was born out of the ability of different networks to talk to each other using common protocols. The interoperability is what we've lost in the Web 2.0 era. Even such quintessential thing as a web API has no well defined standard or protocol, just a very vague concept of REST or RPC. We need commonly accepted standards and decentralized protocols: for web APIs, for identity management, for message queuing, for web callbacks (webhooks), for online transactions, for semantic web and ontology, etc.
  • One wallet / DID / private key could allow you to login to any service. That's your credentials. [[NFTs|Owning a thing]] could allow you to enter somewhere.
  • There should be no technical or social single-point-of-failure for the overall protocol and network. There should be no single organization or individual who can entirely exclude others from the ecosystem (though the ecosystem may collectively exclude bad actors). There should be multiple independent interoperating service providers for each infrastructure component.
  • Open source protocols should favor composability over just about everything. Breaking big things into smaller things. This encourages experimentation at multiple levels.
    • Forking should be a right. Keeps authority contingent (if they abuse power, they might get forked).
  • Progressive decentralization optional centralization.
    • A decentralized protocol can work with a centralized provider. It has the benefits of both (might be fast but no lock users in).
  • A major downside of decentralized protocols/networks is that they tend to perform poorly. Hubs are efficient.
  • It's the properties decentralization gives us that we care about, not decentralization itself. Decentralization is a global, emergent property. You can feel latency, you can feel transaction fees, but networks ostensibly feel the same whether they're centralized or decentralized. Decentralization is valuable when it lets you do new things fundamentally better, not old things fundamentally worse.
  • Ultimately, users don't care about decentralization. Most of the time, it doesn't matter if the service is distributed or comes from a single server sitting in someone's basement. Users want to use services (chat, write mails, watch videos, have a website, buy stuff, sell stuff) and not run infrastructure of any kind. Decentralization is a means to an end, not an end in itself.
  • If a system requires a centralized part, a great alternative is give the user the ability to point to other centralized things taking care of that part.
  • If you have a protocol, try enforcing the desired behavior using the protocol. Your ideas of how to solve it might not be the best and adding a protocol restriction (incentives/penalties) will make people figure out.
  • When building a technology, consider: does this centralize or decentralize power?
  • Many decentralized protocols are trying to build next generation common digital infrastructure.
  • Credible neutrality is the principle that a system or protocol should be demonstrably fair and impartial to all participants, with no hidden biases or privileged interests.

Types of Decentralization

There are three distinct types of decentralization:

  • Architectural decentralization: How many physical computers make up the system and how many can fail before the system stops working.
  • Political decentralization: How many individuals or organizations control those computers.
  • Logical decentralization: Whether the interface and data structures look like a single monolithic system or can be split into independent parts.

A system can be:

  • Decentralized in some aspects but centralized in others (e.g., blockchains are politically and architecturally decentralized but logically centralized).
  • Architecturally decentralized but politically centralized (e.g., many companies running on AWS).
  • Politically decentralized but architecturally centralized (e.g., some formal democracies).

Why Decentralization Matters

Decentralization provides three key benefits:

  • Fault tolerance: Systems are less likely to fail accidentally because they rely on many separate components.
  • Attack resistance: Systems are more expensive to attack because they lack sensitive central points.
  • Collusion resistance: It's harder for participants to collude in ways that benefit them at the expense of others.

However, decentralization is not a silver bullet:

  • Common mode failures can still affect decentralized systems (e.g., all nodes running the same client software with a bug).
  • Pure economic models sometimes show that decentralization doesn't matter for security.
  • There's a paradox between fostering good coordination (e.g., quick protocol upgrades) while preventing harmful coordination (e.g., 51% attacks).