Your account
A wallet instead of a password
- What it is
- A wallet is a key that only you hold. You prove who you are by signing with it, the way you would sign a document. No company stores a password for you.
- Why it matters
- On ordinary platforms your account is a row in a company's database. The company can lock it, sell access to it, or lose it in a breach. If the account is a key you hold, nobody can take it away or pretend to be you.
- How Evrylife does it
- You sign in with your Web3 wallet. Your identity is a decentralized identifier you control — no password and no email required. Private messages are encrypted end to end with keys derived from your wallet; no plaintext mode exists.
Your data
Open networks instead of company servers
- What it is
- Instead of sitting on one company's servers, data is stored on shared public networks and copied between many independent computers. Each piece is addressed by a fingerprint of its content, so it cannot be silently changed.
- Why it matters
- Whoever holds the only copy of your posts, followers and messages controls them. When copies live on an open network, no single party can delete them, ransom them, or switch the service off.
- How Evrylife does it
- Profiles, content, the social graph, votes and messages are OrbitDB documents on IPFS and libp2p, replicated peer to peer. Pinning keeps them durable across Filecoin, Arweave and Storacha. You can export and leave at any time.
The rulebook
A public specification instead of hidden product decisions
- What it is
- A written, public description of everything the software is allowed to do: every feature, setting, automation and policy.
- Why it matters
- Most platforms change their rules in private and you find out afterwards. A public rulebook lets anyone check what the software does, and makes every change visible.
- How Evrylife does it
- The Evrylife Control Plane (ECP) is that rulebook: 33 registries covering 387 features, 135 automations and 214 governed settings. Nothing ships that is not in the ECP, and the app is checked against it.
Decisions
Community consensus instead of an admin
- What it is
- A DAO is a community that makes decisions by an agreed, public process rather than through a boss or a board. Anyone can propose; the group decides.
- Why it matters
- If one person or company can change the rules, the rules protect nobody. Spreading decisions across many independent people makes capture, favouritism and quiet rule changes much harder.
- How Evrylife does it
- Every change enters one of two ways: a member reports a problem, or a member files an improvement proposal (EAIP). Evrylife's consensus system, zkr-POGO, then assigns randomly selected eligible reviewers — you cannot pick your reviewer and identities are stripped from the review. Only an approved outcome becomes a build task, and the finished build is verified by the community again. The agreement needed to pass is itself a governed setting (currently 66.67%, adjustable only within 50–95%).
Ownership
Anti-greed: nobody gets a head start
- What it is
- A token is a unit recorded on a public ledger. Who receives tokens at the start, and whether more can be created later, decides who really owns a network.
- Why it matters
- Many projects reserve a large share for founders and investors, who can later sell to the community that did the work. Others keep the power to create more tokens. Both quietly move value from users to insiders.
- How Evrylife does it
- The supply is capped at 24B EVRY and the cap is immutable: no minting beyond it and no upgradeable proxy. There is zero allocation to founders, investors or a team. The whole supply sits in 9 treasury pools, every one directed by the community. No ads, no data sales.
The treasury
Slow, rule-based release instead of a spending account
- What it is
- A treasury is the shared fund a community uses to pay for its own upkeep and reward the people who contribute.
- Why it matters
- A fund that can be spent all at once will eventually be spent all at once — or drained by whoever gains control. A slow, formula-driven release makes the commons last and leaves nothing worth seizing.
- How Evrylife does it
- Pools release on a rolling declining-balance formula: each month a fixed fraction of what remains, so the fund never runs dry by design. A governed safety cap limits any single month's release (currently 5%, adjustable only within 1–15%). Rewards for reviewing and building are a share of that month's release, weighted by difficulty — never a fixed payout.
Smart contracts
Code that enforces the promises
- What it is
- A smart contract is a small program on a public blockchain. Once deployed, it runs exactly as written and anyone can read it.
- Why it matters
- A promise in a blog post can be broken. A promise written into a contract that nobody can alter cannot.
- How Evrylife does it
- 10 contracts are listed in the ECP — the protocol's own plus the external ones it relies on. The token contract is immutable by design. Evrylife's own contracts deploy at token launch; until then the settlement features that depend on them stay switched off rather than faked.
AI agents
AI advises, people decide
- What it is
- AI agents are programs that can read, classify, draft and build. They are fast and tireless, and they can also be wrong.
- Why it matters
- An AI that decides on its own is just another unaccountable admin. Kept as an adviser under human review, it speeds up the work without taking the authority.
- How Evrylife does it
- The ECP lists 10 DAO agents. They classify, recommend and build; human consensus decides. Each agent can be switched on or off by the community and is trained on the same public knowledgebase you can read here.
The Foundation
Build it, then let it go
- What it is
- Decentralization is not a launch-day switch. Someone has to build the first version; the test is whether they then give up control.
- Why it matters
- A project that never hands over is just a company with extra steps.
- How Evrylife does it
- The Evrylife Foundation bootstraps the protocol and then gets out of the way. There is no admin entrance — the founder uses the platform as an ordinary member — and at hand-off every remaining bootstrap key rotates to community control.
Source: KB047 (About Evrylife & Platform Features), KB039 (Constitution), KB008 (rolling release) in the Evrylife Control Plane knowledgebase — DAO-governed documents, amendable only through zkr-POGO consensus.
Where this comes from: every figure on this page is generated at build time from the Evrylife protocol’s public control plane — ECP v7.7.294, 33 registries, 1,830 rows — read from a committed snapshot of the protocol's control-plane export. evrylife.org is an independent Foundation site that relays public protocol data: it is not a DAO-governed artifact and holds no protocol state of its own. Explanatory text is quoted from the public knowledgebase.
