Introduction to RSS3 Governance

What is Governance?

Governance encompasses the systems and processes that facilitate decision-making within an organization or network. In conventional organizational structures, decision-making might rest with an executive team, a board of directors, or shareholders. Politically, it involves elected officials legislating in line with their constituents’ wishes.

However, these models don’t apply to decentralized systems like RSS3.

Decentralized Governance

No single individual owns or controls the RSS3 Network. Yet, decisions about its evolution and improvement are crucial for ensuring its long-term viability and success. This scenario, where centralized ownership is absent, calls for a governance model that differs significantly from traditional organizational structures.

RSS3 Governance

RSS3 governance describes the method by which changes to the RSS3 Network are discussed and implemented. This process is distinct from how individuals and applications utilize the Network. RSS3 operates on a permissionless basis, meaning anyone can access the RSS3 Network for Open Information without restrictions.

Nonetheless, a structured process exists for proposing modifications to the RSS3 Network. Considering the significant dependence on the stability and functionality of RSS3, any changes to the Network must be approached with a strict and comprehensive process. These changes must ensure security and gain the Community’s acceptance. See

Who is Involved?

There are various stakeholders in the RSS3 Community, each playing an important and distinct role in the governance process:

  • $RSS3 Holders: people hold an arbitrary amount of $RSS3.

  • RSS3 NFTs Holders: people hold RSS3 NFTs released throughout the evolution of the RSS3 Network.

  • Application Users: people interact with applications on the RSS3 Network.

  • Developers: people develop applications leveraging the RSS3 Network.

  • Node Operators: people operate RSS3 Nodes that index, structure, and provide access to, Open Information.

  • REP Proposers: people propose changes to the RSS3 Network, in the form of RSS3 Evolution Proposals (REPs).

  • Core Developers: people constantly contribute to the implementations of the RSS3 Network.

Note: an individual can be part of multiple groups (e.g. a developer could propose an REP, operate an RSS3 Serving Node, and use applications built upon the RSS3 Network).

What is an REP?

One important process used in RSS3 governance is the proposal of RSS3 Evolution Proposals (REPs). REPs are standards specifying potential new features or processes for RSS3. Anyone within the RSS3 Community can propose and comment on an REP.

For more information, please see REP-1.


What about the Whitepaper NFT hodler? :eye: :eye:

:two_hearts: you will never hodl alone.