Saltar a contenido

Vision

The Digital Ecosystem Challenge

In a world of fragmented digital experiences, every new application forces users to create yet another account, manage yet another set of credentials, and surrender yet more personal data to yet another silo. Developers face the same challenge from the other side: every new app means rebuilding authentication, permissions, data sync, and caching from scratch.

CyberEco exists to break this cycle.

What We're Building

CyberEco is a human-centered digital ecosystem — an operating system for life — where interconnected applications solve real needs while sharing a common foundation of identity, data, and trust.

The CyberEco Hub Data Layer is that foundation. It is the backbone that enables 30+ applications across finance, governance, sustainability, education, health, and community to share:

  • Identity — One user, one profile, recognized everywhere
  • Permissions — Granular access control that follows the user across apps
  • Financial data — Transactions, budgets, and settlements visible wherever relevant
  • Groups — Family, friends, and organizations that persist across contexts
  • Activities — Events and actions that span multiple applications
  • Notifications — A unified channel, not 30 separate ones

Why Modular Packages

The data layer was born inside a monorepo — tightly coupled to Firebase, to specific apps, to a particular project structure. That worked for three apps. It won't work for thirty.

By extracting the data layer into four independent npm packages (@cyber-eco/types, @cyber-eco/firebase, @cyber-eco/auth, @cyber-eco/services), we achieve:

  1. Any app, anywhere — A new CyberEco app can install the packages and have full data layer access in minutes, whether it lives in the monorepo or in a completely separate repository.

  2. Storage independence — The StorageAdapter interface means services never know or care whether data lives in Firebase, IPFS, PostgreSQL, or a blockchain. We can migrate the entire ecosystem's storage backend without changing a single line of business logic.

  3. Community contribution — External developers can build CyberEco-compatible apps by consuming published packages, without needing access to the monorepo.

The Long View

2024-2025: Foundation

Hub, JustSplit, and Website running on Firebase. Data layer extracted into four independent packages (@cyber-eco/types, @cyber-eco/firebase, @cyber-eco/auth, @cyber-eco/services). StorageAdapter abstraction established. MCP server exposes the data layer to AI assistants.

2025-2027: Growth & Encryption

Somos, Demos, and Plantopia join the ecosystem. Each consumes the data layer packages from day one. Client-side encryption at rest (AES-256-GCM) protects sensitive fields. TransportAdapter interface designed alongside StorageAdapter. EncryptedStorageAdapter wraps existing adapters transparently.

2027-2029: P2P & Tokenomics

CYE token testnet launches. WiFi Direct and Bluetooth mesh transports enable local peer-to-peer data sync. TEE-based permission evaluation deployed on compatible hardware. CRDTs provide conflict-free merge for offline-first operation. Data hosting rewards begin incentivizing distributed storage.

2029-2031: Multi-Network Mesh

libp2p internet transport joins the mesh. LoRa transport enables long-range, low-power connectivity for rural and disaster scenarios. MultiTransportManager routes data across all available networks automatically. CYE mainnet goes live with full fee structure and governance.

2031-2035: Full Decentralization

P2PStorageAdapter and BlockchainStorageAdapter replace FirebaseStorageAdapter. User data moves to self-sovereign, content-addressed storage. FHE enables batch analytics on encrypted data. MPC powers private group computations (expense splitting without data exposure, secret ballot voting). The CYE token sustains ecosystem governance and infrastructure. Business logic in @cyber-eco/services continues unchanged — it never knew about Firebase, and it doesn't know about IPFS or LoRa either.

Guiding Question

Every design decision in this repository should answer: "Does this bring us closer to a world where users own their digital lives and developers can build on a shared, open foundation?"

If the answer is no, we don't build it.