# Evrylife Protocol Architecture

Evrylife is a **fully decentralized social explorer** built so users truly own their identity, connections, content, and data. There are no ads, no central company holding keys, and no fixed profits — everything is governed by the DAO and funded by community participation.

The platform is structured around **9 core pillars** (high-level layers). Each pillar combines specific technologies and integrations to make the app work securely and privately.

#### The 9 Pillars – What They Do

1. **Wallet & Chain Layer** Lets users connect any wallet and use the app across different blockchains.
   * Web3Modal v3 (connects MetaMask, Phantom, Sui Wallet, Near Wallet, etc.)
   * Wagmi, viem, ethers.js (handles Ethereum-compatible chains)
   * Hyperlane (main cross-chain bridge and messaging)
   * LI.FI (automatic backup routing)
   * Uses native gas fees only (no extra platform token)
2. **Authentication & Identity** Gives every user a secure, self-owned digital ID they control completely.
   * Ceramic DIDs (decentralized identity)
   * Chain-agnostic sign-in (SIWE for Ethereum, SIWS for Solana, SIWN for Near, etc.)
   * Evrylife Main Protocol (1-click login + automatic setup)
   * Unique @username (enforced, linked to your ID)
   * Display Name (can be anything, duplicates allowed)
3. **Decentralized Data Layer** Stores all your profile, channel, and connection data so no company can control or delete it.
   * Ceramic Network (TileDocument + ComposeDB)
   * Web3 Meta Tree (DAO-managed categories and tags)
   * Social graph (your follows, connections, channels)
4. **Content Storage** Holds all your images, videos, text, PDFs, etc. securely and permanently.
   * IPFS (distributed file storage)
   * Automatic pinning to 3+ providers (Pinata, Storacha/Filecoin, Walrus, AIOZ, Arweave, Storj)
   * DAO Free Tier: 1 GB included (no api key needed)
   * Optional personal api keys for extra or private storage
   * Lit Protocol (adds encryption and access rules)
5. **Communication Layer** Enables private and group messaging without any central server.
   * XMTP (decentralized 1:1, group, and channel messages)
6. **Privacy & Zero-Knowledge Layer** Protects your private content and ensures fair, anonymous moderation.
   * Lit Protocol (zero-knowledge encryption and access control)
   * Semaphore (anonymous random selection for moderators, eligibility proofs)
7. **Governance, Token & Economics Layer** Lets the community vote, earn rewards, and manage shared funds fairly.
   * Snapshot (off-chain voting and proposals)
   * zkrPOGO (hybrid on-chain/off-chain execution and random moderation tasks)
   * EVRY token (ERC-20, upgradeable by DAO)
   * 9 DAO treasuries (see allocation table below)
   * Prorated rewards (no fixed APY, no locks, rolling 10–30 year periods)
8. **Discovery & Meta Layer** Helps users find content, people, and topics using smart, community-curated categories.
   * Web3 Meta Tree (Ceramic + IPFS)
   * ComposeDB (smart queries across data)
   * Hugging Face models (DAO fine-tuned for tag suggestions and search)
9. **AI Agents & Intents Layer** Adds helpful AI tools that users and the DAO can control and expand.
   * User Intents (personal automation toggles stored privately on Ceramic)
   * DAO Intents (structured tasks the community can govern)
   * Multi-AI pre-check (safety layer)
   * zkrPOGO execution (community approves AI actions)

**How It All Connects**

* You log in with any wallet → get a Ceramic ID and unique @username.
* Your content saves to IPFS (pinned securely) and metadata to Ceramic.
* Private messages go through XMTP.
* Moderation tasks are randomly assigned via Semaphore (zkrPOGO).
* Community votes on Snapshot, executes via zkrPOGO.
* Rewards come prorated from the right treasury buckets.
* Everything updates live in the Heartbeat dashboard via Ceramic streams.

This architecture is **100% decentralized**, user-sovereign, and governed by the DAO — no central team, no ads, no custodians. The DAO can propose and vote on changes to any pillar at any time.

{% content-ref url="/pages/js36lzvn6zlcsUvLOeuo" %}
[Subscribe to project updates!](/evrylife-foundation-wiki-docs/docs-and-resources/subscribe-to-project-updates.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://evrylife-web-3-explorer.gitbook.io/evrylife-foundation-wiki-docs/evrylife-application/evrylife-protocol-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.