chore: unify bold syntax to single asterisk in .org files and update legacy memex-amero references
This commit is contained in:
@@ -7,7 +7,7 @@
|
||||
|
||||
* 1. Introduction to the Agora Protocol
|
||||
|
||||
The Agora Protocol defines a novel architecture for decentralized digital interaction. Its primary objective is to replace extractive, centralized platforms—the era of **"Digital Feudalism"** where corporations own user data and control visibility via secret algorithms—with a decentralized **"Social Operating System"** that provides Identity, Justice, and Commerce for sovereign individuals and communities.
|
||||
The Agora Protocol defines a novel architecture for decentralized digital interaction. Its primary objective is to replace extractive, centralized platforms—the era of *"Digital Feudalism"* where corporations own user data and control visibility via secret algorithms—with a decentralized *"Social Operating System"* that provides Identity, Justice, and Commerce for sovereign individuals and communities.
|
||||
|
||||
Agora returns power to the edges by providing a modular protocol stack where trust is cryptographic, privacy is inherent, and freedom is architectural. This document provides a comprehensive overview of Agora's foundational principles, core technical differentiators, and a detailed exploration of its capabilities across various use cases, including communication, content creation, e-commerce, collaboration, and liquid democracy. It serves as a high-level technical summary, articulating the design philosophy and the synergistic effects of its integrated components.
|
||||
|
||||
@@ -39,14 +39,14 @@ Agora's unique capabilities stem from the synergistic integration of three prima
|
||||
|
||||
At the heart of Agora's data model is the "Note"—the atomic, universal unit of information. Every piece of content or interaction within the protocol, regardless of its semantic meaning (e.g., a social post, a message, a contract, an encyclopedia entry, a product listing), is encapsulated within a Note.
|
||||
|
||||
For a comprehensive technical breakdown of the Note's structure, cryptographic hashing, and content flag schema, see **[[file:agora-requirements-04-the-primitive.org][04: The Primitive]]**.
|
||||
For a comprehensive technical breakdown of the Note's structure, cryptographic hashing, and content flag schema, see *[[file:agora-requirements-04-the-primitive.org][04: The Primitive]]*.
|
||||
|
||||
*** 3.1.2. Benefits of the Unified Note Primitive
|
||||
|
||||
The "Everything is a Note" paradigm yields significant architectural advantages:
|
||||
- **Universal Interoperability:** A single, standardized data model allows any Agora-compatible client application to understand and process any Note, fostering an open ecosystem where diverse applications can seamlessly interact.
|
||||
- **Immutable Audit Trail:** The content-addressed and signed nature of Notes inherently creates an unalterable, verifiable history of all digital interactions and content evolution.
|
||||
- **Simplified Development:** Developers can focus on application-layer semantics and user experience, leveraging a robust and consistent underlying data primitive.
|
||||
- *Universal Interoperability:* A single, standardized data model allows any Agora-compatible client application to understand and process any Note, fostering an open ecosystem where diverse applications can seamlessly interact.
|
||||
- *Immutable Audit Trail:* The content-addressed and signed nature of Notes inherently creates an unalterable, verifiable history of all digital interactions and content evolution.
|
||||
- *Simplified Development:* Developers can focus on application-layer semantics and user experience, leveraging a robust and consistent underlying data primitive.
|
||||
|
||||
** 3.2. Self-Sovereign Identity: Personas and the Master Key
|
||||
|
||||
@@ -55,23 +55,23 @@ Agora's identity system grants users absolute control over their digital presenc
|
||||
*** 3.2.1. The Master Key (Anima)
|
||||
|
||||
The Master Key serves as the absolute root of a user's digital being within Agora.
|
||||
- **Root of Trust:** A single, securely generated and stored secret seed from which all other identities are derived.
|
||||
- **Hierarchical Derivation:** Utilizes a BIP-44 compatible HD derivation path (`m/44'/1'/account'/persona'/key_purpose/key_index`) to generate an infinite number of unlinkable Personas, each acting as a sovereign sub-root for its own functional keys.
|
||||
- **Secure Storage:** Recommended for offline storage or within Hardware Security Modules (HSMs) to ensure maximum protection.
|
||||
- *Root of Trust:* A single, securely generated and stored secret seed from which all other identities are derived.
|
||||
- *Hierarchical Derivation:* Utilizes a BIP-44 compatible HD derivation path (`m/44'/1'/account'/persona'/key_purpose/key_index`) to generate an infinite number of unlinkable Personas, each acting as a sovereign sub-root for its own functional keys.
|
||||
- *Secure Storage:* Recommended for offline storage or within Hardware Security Modules (HSMs) to ensure maximum protection.
|
||||
|
||||
*** 3.2.2. Personas: Functional Digital Identities
|
||||
|
||||
Personas are the active, functional identities through which users interact with the Agora network.
|
||||
- **Distinct Identities:** Each Persona represents a distinct Decentralized Identifier (DID), allowing users to maintain separate digital roles (e.g., personal, professional, anonymous) with granular control.
|
||||
- **Key Management:** Each Persona possesses its own signing and encryption keypairs, which can be revoked or rotated independently without affecting the Master Key or other Personas.
|
||||
- **Asset Ownership & Rights:** Personas are analogous to legal entities, capable of owning digital assets (e.g., Bitcoin wallets), entering into binding contracts, and claiming protected rights such as due process and freedom of expression.
|
||||
- *Distinct Identities:* Each Persona represents a distinct Decentralized Identifier (DID), allowing users to maintain separate digital roles (e.g., personal, professional, anonymous) with granular control.
|
||||
- *Key Management:* Each Persona possesses its own signing and encryption keypairs, which can be revoked or rotated independently without affecting the Master Key or other Personas.
|
||||
- *Asset Ownership & Rights:* Personas are analogous to legal entities, capable of owning digital assets (e.g., Bitcoin wallets), entering into binding contracts, and claiming protected rights such as due process and freedom of expression.
|
||||
|
||||
*** 3.2.3. Decentralized Identity Management Benefits
|
||||
|
||||
- **Absolute User Control:** Full ownership of identity and keys, independent of any central authority.
|
||||
- **Granular Access Control:** Ability to manage access to specific Personas and their associated data.
|
||||
- **Efficient Organizational Revocation:** For collective entities, the HD model enables atomic revocation of access for departing members directly from the Master Key control point, streamlining offboarding and enhancing security across all associated assets and services.
|
||||
- **Resilient Social Recovery:** Utilizes Shamir's Secret Sharing with trusted "Guardians" to enable Master Key recovery without reliance on centralized services.
|
||||
- *Absolute User Control:* Full ownership of identity and keys, independent of any central authority.
|
||||
- *Granular Access Control:* Ability to manage access to specific Personas and their associated data.
|
||||
- *Efficient Organizational Revocation:* For collective entities, the HD model enables atomic revocation of access for departing members directly from the Master Key control point, streamlining offboarding and enhancing security across all associated assets and services.
|
||||
- *Resilient Social Recovery:* Utilizes Shamir's Secret Sharing with trusted "Guardians" to enable Master Key recovery without reliance on centralized services.
|
||||
|
||||
** 3.3. Distributed Infrastructure: PDS, Relays, and Thin Clients
|
||||
|
||||
@@ -80,24 +80,24 @@ Agora's infrastructure is specifically engineered to underpin user sovereignty,
|
||||
*** 3.3.1. Personal Data Store (PDS): The User's Digital Vault
|
||||
|
||||
The PDS is the central component for data ownership, acting as the user's sovereign digital vault.
|
||||
- **Exclusive Control:** Every user controls their own PDS, whether self-hosted or through a trusted provider.
|
||||
- **Master Archive:** Stores all user content (client-side encrypted) and identity data.
|
||||
- **Access Gatekeeper:** Enforces access control, issuing decryption keys based on validated credentials or payments.
|
||||
- **PDS-as-a-Service:** Services can integrate seamlessly, offering free sign-ups with grace periods and requiring in-Agora payments (e.g., Lightning) for continued service, bypassing traditional financial intermediaries.
|
||||
- *Exclusive Control:* Every user controls their own PDS, whether self-hosted or through a trusted provider.
|
||||
- *Master Archive:* Stores all user content (client-side encrypted) and identity data.
|
||||
- *Access Gatekeeper:* Enforces access control, issuing decryption keys based on validated credentials or payments.
|
||||
- *PDS-as-a-Service:* Services can integrate seamlessly, offering free sign-ups with grace periods and requiring in-Agora payments (e.g., Lightning) for continued service, bypassing traditional financial intermediaries.
|
||||
|
||||
*** 3.3.2. Relay Network: The Intelligent Communication Backbone
|
||||
|
||||
The Relay Network forms the intelligent communication backbone of Agora, efficiently routing encrypted Notes between Personas.
|
||||
- **Ephemeral Routing:** Relays route ciphertext based on CIDs and Persona subscriptions, without long-term storage of user data.
|
||||
- **Pub/Sub Model:** Facilitates efficient, real-time delivery of Notes based on user subscriptions.
|
||||
- **Censorship Resistance:** Users can publish to multiple Relays, ensuring availability and resilience against censorship.
|
||||
- *Ephemeral Routing:* Relays route ciphertext based on CIDs and Persona subscriptions, without long-term storage of user data.
|
||||
- *Pub/Sub Model:* Facilitates efficient, real-time delivery of Notes based on user subscriptions.
|
||||
- *Censorship Resistance:* Users can publish to multiple Relays, ensuring availability and resilience against censorship.
|
||||
|
||||
*** 3.3.3. Agile Client Architecture: Broad Accessibility and Adaptability
|
||||
|
||||
Agora adopts a flexible client architecture to balance user sovereignty with broad accessibility, particularly concerning app store ecosystems.
|
||||
- **PDS-Proximate Logic:** Core application logic can reside and execute securely on the user's PDS.
|
||||
- **Thin Clients:** Edge devices (mobile, desktop) run lightweight applications that interface with the PDS, mitigating app store restrictions and reducing device resource demands.
|
||||
- **Strategic Imperative:** This architecture ensures Agora's reach to a wider user base while maintaining security and privacy.
|
||||
- *PDS-Proximate Logic:* Core application logic can reside and execute securely on the user's PDS.
|
||||
- *Thin Clients:* Edge devices (mobile, desktop) run lightweight applications that interface with the PDS, mitigating app store restrictions and reducing device resource demands.
|
||||
- *Strategic Imperative:* This architecture ensures Agora's reach to a wider user base while maintaining security and privacy.
|
||||
|
||||
* 4. Agora Use Cases: A Paradigm Shift
|
||||
|
||||
@@ -109,14 +109,14 @@ Agora provides a robust framework for secure, private, and censorship-resistant
|
||||
|
||||
*** 4.1.1. Asynchronous Interaction (The Note Primitive)
|
||||
|
||||
- **Unified Model:** All async interactions—whether directed messages or broadcast posts—are built on the same cryptographically signed **Note** primitive, utilizing the **DIDComm** protocol for secure transport.
|
||||
- **Storage Sovereignty:** Employs a "Copy-on-Send" model for directed communication (ensuring recipient data ownership) and a "Reference-on-Send" model for broadcast content (ensuring owner control). The PDS acts as an encrypted mailbox proxy.
|
||||
- **End-to-End Encryption:** Default for directed communications, utilizing standard encrypted envelopes. Double Ratchet and MLS ensure forward secrecy.
|
||||
- *Unified Model:* All async interactions—whether directed messages or broadcast posts—are built on the same cryptographically signed *Note* primitive, utilizing the *DIDComm* protocol for secure transport.
|
||||
- *Storage Sovereignty:* Employs a "Copy-on-Send" model for directed communication (ensuring recipient data ownership) and a "Reference-on-Send" model for broadcast content (ensuring owner control). The PDS acts as an encrypted mailbox proxy.
|
||||
- *End-to-End Encryption:* Default for directed communications, utilizing standard encrypted envelopes. Double Ratchet and MLS ensure forward secrecy.
|
||||
|
||||
*** 4.1.2. Synchronous Interaction (Real-time)
|
||||
|
||||
- **WebRTC Integration:** Supports peer-to-peer real-time chat, voice, and video calls with end-to-end encryption and **decentralized signaling** via DIDComm handshakes.
|
||||
- **Off-the-Record Mode:** Provides absolute privacy for ephemeral interactions by utilizing extremely short `ephemeral_duration` or bypassing PDS storage entirely, with content existing only in volatile client memory.
|
||||
- *WebRTC Integration:* Supports peer-to-peer real-time chat, voice, and video calls with end-to-end encryption and *decentralized signaling* via DIDComm handshakes.
|
||||
- *Off-the-Record Mode:* Provides absolute privacy for ephemeral interactions by utilizing extremely short `ephemeral_duration` or bypassing PDS storage entirely, with content existing only in volatile client memory.
|
||||
|
||||
** 4.2. Social Publishing and Knowledge Management
|
||||
|
||||
@@ -124,22 +124,22 @@ Agora fundamentally reshapes how content is created, published, and managed, emp
|
||||
|
||||
*** 4.2.1. Feeds and Pages
|
||||
|
||||
- **Immutable History:** Social posts (`is_feed: true`) and wiki pages (`is_feed: false`) are signed Notes, providing an unalterable history of creation and edits.
|
||||
- **Auditable Threads:** Replies are Notes referencing parent CIDs, creating verifiable discussion threads across the distributed network.
|
||||
- **Direct Monetization:** Paywalled content and seeder rewards enable direct creator-to-consumer economic models via Lightning micro-payments.
|
||||
- *Immutable History:* Social posts (`is_feed: true`) and wiki pages (`is_feed: false`) are signed Notes, providing an unalterable history of creation and edits.
|
||||
- *Auditable Threads:* Replies are Notes referencing parent CIDs, creating verifiable discussion threads across the distributed network.
|
||||
- *Direct Monetization:* Paywalled content and seeder rewards enable direct creator-to-consumer economic models via Lightning micro-payments.
|
||||
|
||||
*** 4.2.2. Decentralized Wikis and Encyclopedias
|
||||
|
||||
- **Versioned Pages:** Each wiki page is an `is_feed: false` Note, with edits creating new Notes that supersede previous versions, building an immutable, auditable version history.
|
||||
- **Collaborative Ownership:** Access control and editing rights are managed via **Contract Notes** (Consent or Service Contracts) with `Collective Personas`.
|
||||
- **Incentivized Contributions:** Micro-payments can reward contributions, fostering a collaborative, trustworthy, and censorship-resistant knowledge base.
|
||||
- *Versioned Pages:* Each wiki page is an `is_feed: false` Note, with edits creating new Notes that supersede previous versions, building an immutable, auditable version history.
|
||||
- *Collaborative Ownership:* Access control and editing rights are managed via *Contract Notes* (Consent or Service Contracts) with `Collective Personas`.
|
||||
- *Incentivized Contributions:* Micro-payments can reward contributions, fostering a collaborative, trustworthy, and censorship-resistant knowledge base.
|
||||
|
||||
*** 4.2.3. Verifiable News Ecosystem
|
||||
|
||||
- **Signed Articles:** News articles are `is_feed: true` Notes, signed by journalist Personas, ensuring clear provenance and ownership.
|
||||
- **Immutable Record:** All versions of an article are archived, preventing historical revisionism or "disappearing" stories.
|
||||
- **Decentralized Distribution:** Resilient against censorship attempts, as distribution occurs via the Relay Network.
|
||||
- **Reputation Systems:** Notes referencing Persona DIDs and community-driven verification mechanisms can build transparent reputation for sources and journalists.
|
||||
- *Signed Articles:* News articles are `is_feed: true` Notes, signed by journalist Personas, ensuring clear provenance and ownership.
|
||||
- *Immutable Record:* All versions of an article are archived, preventing historical revisionism or "disappearing" stories.
|
||||
- *Decentralized Distribution:* Resilient against censorship attempts, as distribution occurs via the Relay Network.
|
||||
- *Reputation Systems:* Notes referencing Persona DIDs and community-driven verification mechanisms can build transparent reputation for sources and journalists.
|
||||
|
||||
** 4.3. Decentralized E-commerce and Markets
|
||||
|
||||
@@ -147,14 +147,14 @@ Agora enables peer-to-peer economic interaction without intermediaries, fosterin
|
||||
|
||||
*** 4.3.1. Market Interaction Contracts
|
||||
|
||||
- **Offer as Early Contract:** A **Contract Note** (product listing) serves as a unilateral declaration of intent (**Offer**) by a seller, transitioning into a bilateral agreement (**Take**) upon buyer acceptance.
|
||||
- **Transparent Listings:** Offers are signed Notes, providing verifiable details of items or services.
|
||||
- **Questions and Reviews:** Notes that `reply_to` or `references` listings allow public or private dialogue, building transparent market trust and reputation based on Owner Reputation.
|
||||
- *Offer as Early Contract:* A *Contract Note* (product listing) serves as a unilateral declaration of intent (*Offer*) by a seller, transitioning into a bilateral agreement (*Take*) upon buyer acceptance.
|
||||
- *Transparent Listings:* Offers are signed Notes, providing verifiable details of items or services.
|
||||
- *Questions and Reviews:* Notes that `reply_to` or `references` listings allow public or private dialogue, building transparent market trust and reputation based on Owner Reputation.
|
||||
|
||||
*** 4.3.2. Fungible vs. Non-fungible Assets
|
||||
|
||||
- **Non-Fungible:** Agora's **Contract Note** model is inherently well-suited for unique goods and services (e.g., digital art, custom work), with each contract representing a distinct agreement.
|
||||
- **Fungible:** While Agora provides the identity, communication, and settlement rails (e.g., Lightning micropayments), high-speed trading of fungible assets (e.g., cryptocurrencies, commodities) would require specialized architectural layers (e.g., decentralized exchanges or AMMs) built *on top of* the Agora protocol for order matching and liquidity.
|
||||
- *Non-Fungible:* Agora's *Contract Note* model is inherently well-suited for unique goods and services (e.g., digital art, custom work), with each contract representing a distinct agreement.
|
||||
- *Fungible:* While Agora provides the identity, communication, and settlement rails (e.g., Lightning micropayments), high-speed trading of fungible assets (e.g., cryptocurrencies, commodities) would require specialized architectural layers (e.g., decentralized exchanges or AMMs) built *on top of* the Agora protocol for order matching and liquidity.
|
||||
|
||||
** 4.4. Decentralized Collaboration and Project Management
|
||||
|
||||
@@ -162,21 +162,21 @@ Agora offers robust primitives for secure, auditable collaboration, empowering t
|
||||
|
||||
*** 4.4.1. Version-Controlled Documents and Code
|
||||
|
||||
- **Signed Commits/Edits:** Each change to a collaborative document or codebase is a signed Note with appropriate `content_type` (for code) or a versioned `is_feed: false` Note (for documents), creating an immutable, auditable history.
|
||||
- **Collective Ownership:** Repositories or documents can be owned by `Collective Personas`, with access and editing rights managed via **Contract Notes**.
|
||||
- **Decentralized GitHub/Git Integration:** Codebases are stored as Merkle DAGs of commit Notes, enabling decentralized version control. Issues and pull requests are also Notes, facilitating transparent project management.
|
||||
- *Signed Commits/Edits:* Each change to a collaborative document or codebase is a signed Note with appropriate `content_type` (for code) or a versioned `is_feed: false` Note (for documents), creating an immutable, auditable history.
|
||||
- *Collective Ownership:* Repositories or documents can be owned by `Collective Personas`, with access and editing rights managed via *Contract Notes*.
|
||||
- *Decentralized GitHub/Git Integration:* Codebases are stored as Merkle DAGs of commit Notes, enabling decentralized version control. Issues and pull requests are also Notes, facilitating transparent project management.
|
||||
|
||||
*** 4.4.2. Project Management and Task Tracking
|
||||
|
||||
- **Tasks as Contracts:** Project tasks are **Contract Notes** in a negotiation state, allowing for assignment, progress tracking, and integration with payment mechanisms.
|
||||
- **Incentivized Development:** Lightning bounties (**Contract Notes**) can be attached to issues or tasks, directly rewarding contributions upon completion and verification.
|
||||
- *Tasks as Contracts:* Project tasks are *Contract Notes* in a negotiation state, allowing for assignment, progress tracking, and integration with payment mechanisms.
|
||||
- *Incentivized Development:* Lightning bounties (*Contract Notes*) can be attached to issues or tasks, directly rewarding contributions upon completion and verification.
|
||||
|
||||
*** 4.4.3. The Aletheia Portfolio (Professional Integration)
|
||||
|
||||
The convergence of native hosting, identity, and contracts enables a unified professional workflow. For example, a freelance photographer can:
|
||||
- **Generate & Publish:** Build a professional portfolio using a static site generator and publish it natively to the network via their "Professional Persona" root CID.
|
||||
- **Sovereign Hosting:** The portfolio remains available via any Gateway, resilient against PDS downtime.
|
||||
- **Contractual Linkage:** Directly link the portfolio Note to a binding service contract for client hiring, with payments settled via Lightning.
|
||||
- *Generate & Publish:* Build a professional portfolio using a static site generator and publish it natively to the network via their "Professional Persona" root CID.
|
||||
- *Sovereign Hosting:* The portfolio remains available via any Gateway, resilient against PDS downtime.
|
||||
- *Contractual Linkage:* Directly link the portfolio Note to a binding service contract for client hiring, with payments settled via Lightning.
|
||||
|
||||
** 4.5. Liquid Democracy and Governance: Evolvable Collectives
|
||||
|
||||
@@ -184,15 +184,15 @@ Agora's identity and contract primitives lay the groundwork for a dynamic, adapt
|
||||
|
||||
*** 4.5.1. Adaptive Constitutions and Policy Execution
|
||||
|
||||
- **Signed Votes and Execution:** Individual votes are signed Notes that `references` a proposal CID. Unlike immutable blockchain code, Agora governance is built around **Adaptive Constitutions**.
|
||||
- **Recursive Rule-Making:** Successful votes trigger the Governance Executable Module (GEM) to automatically update the Collective's policy parameters (e.g., membership fees, arbitration rules) in its active Smart Constitution.
|
||||
- **Immutable History, Mutable State:** While the complete audit trail of every vote and version is permanently recorded as a chain of CIDs, the organization can evolve its logic over time without requiring complex migrations.
|
||||
- *Signed Votes and Execution:* Individual votes are signed Notes that `references` a proposal CID. Unlike immutable blockchain code, Agora governance is built around *Adaptive Constitutions*.
|
||||
- *Recursive Rule-Making:* Successful votes trigger the Governance Executable Module (GEM) to automatically update the Collective's policy parameters (e.g., membership fees, arbitration rules) in its active Smart Constitution.
|
||||
- *Immutable History, Mutable State:* While the complete audit trail of every vote and version is permanently recorded as a chain of CIDs, the organization can evolve its logic over time without requiring complex migrations.
|
||||
|
||||
*** 4.5.2. Decentralized Autonomous Organizations (DAOs)
|
||||
|
||||
- **Foundation Contracts:** DAOs are formalized as `Collective Personas` governed by a set of foundational `Contract Notes` that define membership, treasury management, and decision-making processes.
|
||||
- **Forks as Safety Valves:** Because Agora is permissionless, minorities can "fork" a Collective by creating a new Persona based on an earlier constitutional CID, ensuring protection against majority tyranny and preserving community intent.
|
||||
- **Transparent Operations:** All operational decisions, proposals, and expenditures within a DAO are conducted and recorded as signed Notes and Contracts, providing 100% transparency to participants.
|
||||
- *Foundation Contracts:* DAOs are formalized as `Collective Personas` governed by a set of foundational `Contract Notes` that define membership, treasury management, and decision-making processes.
|
||||
- *Forks as Safety Valves:* Because Agora is permissionless, minorities can "fork" a Collective by creating a new Persona based on an earlier constitutional CID, ensuring protection against majority tyranny and preserving community intent.
|
||||
- *Transparent Operations:* All operational decisions, proposals, and expenditures within a DAO are conducted and recorded as signed Notes and Contracts, providing 100% transparency to participants.
|
||||
|
||||
* 5. Conclusion: Towards a Self-Sovereign Digital Future
|
||||
|
||||
@@ -255,24 +255,24 @@ Reduce "empty feed" problem by immediately showing relevant content based on use
|
||||
Scaling a decentralized network requires shifting from "Hand-holding" to "Protocol Incentives." Agora follows a strictly defined orders-of-magnitude growth strategy:
|
||||
|
||||
*** Order 1: The First 1,000 (The "Founders")
|
||||
- **Target:** Technical enthusiasts, privacy advocates, and niche professional guilds (e.g., decentralized AI devs).
|
||||
- **Tactics:** Manual onboarding. We seed the first Arbitration Guilds.
|
||||
- **Success Metric:** First successful civil contract signed and settled via HODL invoice.
|
||||
- *Target:* Technical enthusiasts, privacy advocates, and niche professional guilds (e.g., decentralized AI devs).
|
||||
- *Tactics:* Manual onboarding. We seed the first Arbitration Guilds.
|
||||
- *Success Metric:* First successful civil contract signed and settled via HODL invoice.
|
||||
|
||||
*** Order 2: The 10,000 (The "Communities")
|
||||
- **Target:** Small NGOs, local trade groups, and content creator "Swarms."
|
||||
- **Tactics:** Launch the Community PDS templates. Enable "One-Click Hub" setup so a leader can host their entire group.
|
||||
- **Success Metric:** The emergence of "Community Algorithms"—feeds curated by these 10k users that provide unique value.
|
||||
- *Target:* Small NGOs, local trade groups, and content creator "Swarms."
|
||||
- *Tactics:* Launch the Community PDS templates. Enable "One-Click Hub" setup so a leader can host their entire group.
|
||||
- *Success Metric:* The emergence of "Community Algorithms"—feeds curated by these 10k users that provide unique value.
|
||||
|
||||
*** Order 3: The 100,000 (The "Marketplace")
|
||||
- **Target:** Freelancers, gig workers, and "Etsy-style" digital sellers in regions with weak rule of law.
|
||||
- **Tactics:** Focus on Mobile UX. The app must feel "normal." Introduce Automated Key Rotation so non-tech users don't fear losing their phones.
|
||||
- **Success Metric:** $1M+ in peer-to-peer transaction volume via SCAL contracts.
|
||||
- *Target:* Freelancers, gig workers, and "Etsy-style" digital sellers in regions with weak rule of law.
|
||||
- *Tactics:* Focus on Mobile UX. The app must feel "normal." Introduce Automated Key Rotation so non-tech users don't fear losing their phones.
|
||||
- *Success Metric:* $1M+ in peer-to-peer transaction volume via SCAL contracts.
|
||||
|
||||
*** Order 4: The 1M+ (The "Ecosystem")
|
||||
- **Target:** The general public.
|
||||
- **Tactics:** The Algorithm Marketplace becomes the draw. People join because "The Scientific Lens" or "The Family Lens" on Agora provides a better mental health experience than the addictive AI of centralized apps.
|
||||
- **Success Metric:** Total P2P bandwidth (Seeding) exceeds the capacity of a mid-sized centralized CDN.
|
||||
- *Target:* The general public.
|
||||
- *Tactics:* The Algorithm Marketplace becomes the draw. People join because "The Scientific Lens" or "The Family Lens" on Agora provides a better mental health experience than the addictive AI of centralized apps.
|
||||
- *Success Metric:* Total P2P bandwidth (Seeding) exceeds the capacity of a mid-sized centralized CDN.
|
||||
|
||||
** Progressive Decentralization Phases
|
||||
|
||||
|
||||
Reference in New Issue
Block a user