Evrylife Foundation

KB009 · architecture reference

No server holds your data

Evrylife is a fully decentralized social application. No centralized server holds user data or controls access. The architecture is defined by the ECP, which specifies 39 modules across 4 tiers.

The data layer

All member data lives in OrbitDB stores on IPFS + libp2p. Each ECP domain maps to an OrbitDB store (document or event-log). Identity is a wallet did:pkh → did:key; the wallet signs writes, so the member — not a company — controls their data.

  1. A member acts in the frontend.
  2. dataService writes to the domain's OrbitDB store, signed by the wallet's did:key.
  3. The write replicates peer-to-peer over IPFS/libp2p; a community indexer aggregates stores for global feeds and the explorer.
  4. Media is pinned to IPFS for durability — Storacha, Filecoin, or Arweave; member key first, DAO free tier as fallback.
  5. Lit Protocol encrypts private content client-side before storage.
Governing principle: build on durable protocol primitives (IPFS, libp2p, EVM, Arweave) — never company products that pivot. The database engine stays swappable behind dataService.

The integration stack

ProtocolPurposeECP reference
OrbitDB on IPFS + libp2pMutable data layerAll modules
IPFSContent-addressed storageE004
FilecoinLong-term persistenceE004
ArweavePermanent storageE004
StorachaFast pinningE004
Lit ProtocolEncryption + access controlE011
SemaphoreZero-knowledge proofsE011
OrbitDB / libp2p (ECIES)Encrypted messagingE017
HyperlaneCross-chain bridgingE001, SC005–006
ENSName resolutionE005

Module tiers

Core protocol

The foundation layer.

E001 Token contract moduleE002 Onboarding & auth moduleE003 Web3 meta treeE004 Decentralized storage moduleE005 Profile moduleE006 Zkrpogo moderation moduleE007 Content management moduleE009 App security moduleE010 Communications moduleE011 Zero knowledge moduleE012 Channel moduleE014 Follow moduleE015 Ai and intents moduleE017 Messaging moduleE019 Earn moduleE020 Tagging moduleE021 Search bar moduleE022 User quality moduleE023 Events moduleE024 Dao dev task moduleE026 Share content module

Content type modules

What members create, publish, and sell.

E025 Translation moduleE027 Directory moduleE028 Products & services moduleE029 Subscription moduleE030 App operations moduleE032 Q&a moduleE033 Affiliate moduleE034 External embeds moduleE035 Nft & digital collectibles moduleE037 Quest moduleE038 Apps moduleE039 Ai-agents module

Infrastructure

Governance plumbing and member signals.

E008 Eaip moduleE013 Account dashboard moduleE016 Frontend ui moduleE018 Alerts & notifications module

Optional / gated

Community-gated modules.

E031 Causes moduleE036 Vr module

The Web3 Meta Tree

The classification system organizing all content, locations, topics, and breakdowns — a DAO-governed taxonomy of 31,152 nodes across 4 pillars, counted live from the protocol's taxonomy registry:

PillarNodesMax depth
Topics19,82914
Locations6,7455
Content Types3,78110
Breakdowns7977

All meta tree changes are zkr-POGO-gated and require an EAIP after bootstrap.

The AI layer

The ai_agents_registry lists 10 agents: task agents handle automated advisory work, and a guardian agent enforces the immutable floor.

AAG-001 dao-maintenance-agentAAG-002 meta-tree-agentAAG-003 content-moderation-agentAAG-004 translation-agentAAG-005 rewards-calculation-agentAAG-006 user-intent-agentAAG-007 quiz-regeneration-agentAAG-008 dao-builder-agentAAG-009 dao-guardian-agentAAG-010 platform-support-agent

All AI models run on decentralized infrastructure — Akash, Bittensor, Gensyn, or local nodes. No centralized AI APIs. Agents advise; consensus decides.

Join the waitlist → Constitution, Articles III & VI
Source: KB009 (Architecture Reference), KB039 (Constitution, Articles III and VI), KB047 in the Evrylife Control Plane knowledgebase — DAO-governed documents, amendable only through zkr-POGO consensus. The meta tree node count is taken from KB047/KB048 (~31,000 and growing); KB009's per-pillar counts predate it and are omitted here rather than published stale.