Skip to content

The Linux Model: Codebase vs. Instances

Society Protocol operates under an organizational and architectural framework similar to the Linux Foundation.

🐧 A Single Codebase, Many Communities

Civilization only needs one impeccably secure, highly modular, and credibly neutral codebase for Society Protocol to spawn an infinite number of customizable instances.

                  +-----------------------------------+
                  |   SOCIETY PROTOCOL CORE CODEBASE  |
                  |   (Secure, Modular, Neutral)      |
                  +-----------------------------------+
                                    |
          +-------------------------+-------------------------+
          |                         |                         |
          v                         v                         v
+-------------------+     +-------------------+     +-------------------+
|  SP Instance #1   |     |  SP Instance #2   |     |  SP Instance #3   |
| (Eco-Community)   |     | (Network State)   |     | (DeFi Guild)      |
| Custom Parameters |     | Custom Parameters |     | Custom Parameters |
+-------------------+     +-------------------+     +-------------------+

The Linux Analogy

  • The Core Codebase (Linux Kernel): Maintained by the Society Protocol organization. It provides the minimal-viable-product (MVP) state transition functions (STF), Energy state machine, account abstractions, and core Value Functions (VFs).
  • SP Instances (Linux Distributions): Independent deployments created by communities, DAOs, or nation-states (e.g. Ubuntu, Fedora, Debian equivalents). Each instance configures its own Value Functions, Constitutions, UIs, and initial Energy distributions.

🏛️ The Three Core Principles

To allow thousands of diverse communities to trust and adopt Society Protocol, the core codebase adheres strictly to three principles:

  1. Impeccable Security: Entrusting human identity and society to a state machine carries immense responsibility. The core layers undergo rigorous battle-testing and concentric audit rings.

  2. Modular Architecture: Communities configure distinct Value Functions (Parenting, Hunting, Property, Curation, Governance, Communication) without altering core security.

  3. Credible Neutrality: The stewards of the codebase remain strictly neutral. The core team does not start or rule SP instances; it builds the generic, fair infrastructure for all instances to bloom.