Skip to content

Web3 Outpost: The Web4 Launchpad

The Web3 Outpost functions as the central Schelling point and launchpad bridging humanity from Web3 and Nation States into Web4 and Synchronized States.

🚀 The Launchpad Concept

Building the full Society Protocol ecosystem is a multi-decade journey. The minimal-viable-product (MVP) codebase is expected in ~3–5 years, while the overall transition of human society into Synchronized States will stretch over 20 to 75 years.

During this transition, the Web3 Outpost provides crucial censorship-resistant infrastructure on Ethereum Mainnet to:

  1. Build a Subjective Identity Map (Accounts & Badges): Users construct a single, sybil-resistant history recorded via Accounts and Badges (ERC-1155), capturing credentials, referral chains, and characteristics.

  2. Measure Objective Contribution (SPEC Token): The SPEC token (ERC-20) stores objective contribution value, quantifying participant skin-in-the-game.

  3. Supply Genesis Starting Parameters: When independent Web4 Society Protocol instances spawn, they need to know who to include (Subjective Map) and how much Energy to grant (Objective Map).

âš¡ How the Outpost Powers Web4 Instances

When a community, family, DAO, or nation-state decides to launch a new Society Protocol Instance, they face two fundamental questions:

  1. "Who gets to be the initial Genesis Actors in our instance?" (Answered by Accounts & Badges)

  2. "How much initial Energy does each Genesis Actor receive?" (Answered by SPEC Token Holdings)

Attempting to resolve these questions manually for thousands of participants creates severe coordination friction, sybil vulnerability, and political deadlock.

The Web3 Outpost resolves this friction:

+-------------------------------------------------------------------------+
|                           WEB3 OUTPOST                                  |
|                                                                         |
|  [Subjective Map] Accounts + Badges (zkTLS, Builder, Country, Roles)    |
|  [Objective Map]  SPEC Token Balances (Stored Contribution Value)       |
+-------------------------------------------------------------------------+
                                    |
                                    | Exports Genesis Parameters
                                    v
+-------------------------------------------------------------------------+
|                  UPSTART WEB4 SP INSTANCES (GENESIS)                    |
|                                                                         |
|  - Community A Instance   --> Invites Builder Badges (Who) + SPEC (Energy)
|  - Community B Instance   --> Invites Argentine Badges (Who) + SPEC (Energy)
|  - Network State Instance --> Invites All Outpost Accounts + SPEC (Energy)
+-------------------------------------------------------------------------+

Examples of Community Genesis Parameters

Communities launching SP instances can slice the Web3 Outpost data in endless ways:

  • Builder-Focused Instance: Invites only accounts possessing the Builder Badge (26), allocating initial Energy proportional to each account's SPEC token holdings.
  • Regional Network State: Invites only accounts with a verified Country Badge (via zkTLS), requiring a minimum SPEC balance for sybil-resistance, and allocating equal starting Energy.
  • Partner Community Instance: Invites members holding custom Community Wrapper Badges and grants bonus Energy to SPEC token holders.