The Echosystem Foundation — Founding Charter
Status: Draft v0.1 for review by Gabriel Marciel. This is not a legal document, has not been adopted, and is not an offer to sell any token or investment.
Date: 21 November 2026 (America/Los_Angeles)
Legal review required. This draft should be reviewed by qualified counsel before it is adopted, before any legal entity is formed, and before any token is issued. Nothing here is legal, tax, or financial advice.
Preamble
The Echosystem Foundation is the planned sovereign organization behind Echo (echoworld.app) and EchoBot. It is meant to be a free, independent entity with no corporate shareholders: a DAO on the Internet Computer (ICP) that runs Echo's daily operations lean, keeps ad and sales revenue inside the Echosystem, and puts users first.
Echo will have ads. That is intentional. Ads, marketplace activity, and other revenue are how the network pays for itself. The point is not to avoid ads. The point is to keep that revenue in the Echosystem, and to give people a fair, optional way to share in the value of their own data.
This charter records what has already been decided, marks what is still open, and gives the Foundation a written foundation to build on.
1. Mission
The Foundation exists to steward a user-first social network and the tools around it — including Echo and EchoBot — so that:
- a person's account, voice, and audience cannot be switched off by a single company;
- we never sell a person's data without their permission;
- the people who create the value receive a real share of it;
- the network is governed in the open, on the Internet Computer, rather than by corporate shareholders.
The long-term aim is a better, user-first social network: one that is owned and directed by the community that uses it. The Foundation should stay lean, spend carefully, and measure success by whether people are actually better off — not by how long it can hold their attention.
2. Principles
2.1 Sovereignty
The Foundation is a sovereign entity. It has no corporate shareholders. Its important records, treasury, and (once launched) its governance live on the Internet Computer, a public network run by independent node providers. No single company should hold an off switch over Echo or over the Foundation itself.
2.2 Transparency
Money movement is public. Sales, payouts, and treasury activity are to be recorded on-chain so they can be checked. Personal data stays private and is never published on-chain. Moderation and policy changes should be visible. Transparency is a theme of the whole Echosystem, not a slogan.
2.3 User ownership
Your account, your posts, and your data belong to you. Privacy is the default. The Foundation and the apps it stewards never sell your data without your permission. If you later choose to opt in to the Data Dividend, you pick what is shared, you can change your mind, and you receive the majority of the profit from those sales.
2.4 Lean operations
The Foundation should run daily operations with a small footprint: enough people and tools to keep Echo safe, solvent, and improving, and no more. Revenue is first a way to sustain the network and return value to users, not a way to grow a large central organization.
3. Structure
3.1 A DAO on the Internet Computer
The Foundation is planned as a decentralized autonomous organization (DAO) on ICP. Until that DAO exists, day-to-day direction sits with the founder, and funds for the Echosystem are held in a designated treasury account (see §5).
3.2 SNS or a custom DAO
There are two realistic ways to put the Foundation on-chain:
Service Nervous System (SNS). This is the Internet Computer's built-in framework for a community-owned app. Token holders vote on upgrades, treasury spending, and governance. A decentralization swap can distribute tokens, and ICP raised in that swap can fund the treasury. An SNS launch requires an approved proposal to the Network Nervous System (NNS). The tooling is public, documented, and already used by other ICP projects.
A custom DAO. The Foundation could instead write its own governance canisters. That would allow rules the SNS does not yet express well — for example, a more tailored Data Dividend, or a voting model that is not purely token-weighted. The cost is higher: more code to design, audit, and maintain, and a greater chance of error.
Recommendation. Launch the Foundation as an SNS, and add a small amount of custom canister code only where the SNS cannot support a decided feature (for example, Data Dividend accounting). A custom-only DAO should be chosen only if counsel and engineering agree that SNS cannot meet the Foundation's needs.
3.3 Legal wrapper (options only, not advice)
On-chain governance does not, by itself, answer every legal question: contracts, taxes, employment, intellectual property, and how the Foundation appears to the outside world. A legal wrapper will almost certainly be needed. Options that organizations sometimes consider include a Swiss foundation, a Cayman foundation company, and a Wyoming DUNA, among others. These are examples to discuss with qualified counsel, not a recommendation and not legal advice. No wrapper has been chosen.
Jurisdiction, tax treatment, and any money-transmission or securities analysis must be reviewed by counsel before adoption, before a token launch, and before any public offering of $ECHO.
4. The $ECHO token
$ECHO is the planned native token of the Echosystem. It does not exist yet. This charter does not promise a launch date, a price, a return, or a distribution.
4.1 Intended role
$ECHO is intended as both:
- a governance token, used to vote on Foundation proposals once the DAO exists; and
- a utility token, used inside the Echosystem (for example, participation in future product features such as Boost, Premium, or other tools the community later approves).
Nothing in this paragraph is a commitment to issue the token, and nothing here is an offer to sell or a solicitation to buy any token or investment.
4.2 Design placeholders (TBD)
The following are left open for Gabriel and, later, for counsel and the DAO:
| Topic | Status |
|---|---|
| Total supply | TBD |
| Allocations (community, treasury, founder, contributors, any swap) | TBD |
| Vesting and lockups | TBD |
| Issuance method (SNS decentralization swap or another method) | TBD |
| What $ECHO can be used for at launch | TBD |
| Whether rewards or dividends are ever paid in $ECHO, a stablecoin, or both | TBD |
No supply numbers, valuations, or price targets may be published as if they were decided.
4.3 Moving $ECHO out of the Echosystem
If, in the future, $ECHO can be moved out of the Echosystem, any extra steps or delays must be designed and described as a security feature: a way to protect accounts and funds from theft, takeover, or mistake. This must never be framed, named, or designed as an "exit fee," and it must not be used as a way to discourage people from leaving.
5. Treasury and revenue
5.1 What the treasury is for
The Echosystem treasury holds and directs the Foundation's funds. Its purpose is to:
- keep Echo and EchoBot running (including network costs);
- return value to users through the Data Dividend and other approved programs;
- fund lean operations, including any approved compensation;
- improve the product.
Ad revenue stays in the Echosystem. Sales revenue stays in the Echosystem. The Foundation does not exist to extract that revenue for outside shareholders, because it has none.
5.2 Revenue sources (planned or already sketched)
The following sources have been discussed. Not all of them are live.
- Ads. Echo will have ads. Ad revenue is managed by the Foundation and stays in the Echosystem. Echo does not use third-party ad trackers or sell people to data brokers.
- Data sales (opt-in only). See §7. We never sell your data without your permission.
- Tip fee. A 2% Echosystem fee is added on top of each tip and paid by the sender. The creator receives the full tip. For example, a $1 tip costs $1.02, plus any network fee. (Example only.)
- Market fees. The Market is meant to be mostly free, in the spirit of a classic classifieds board, with fees on vehicles, real estate, and jobs.
- Other product revenue, as later approved: fees, Boost, Premium, pro tools, and robot jobs.
- Treasury management, including careful holding of assets the DAO later approves.
- HydroBit is a separate project of the founder and has been discussed as a possible source of support. The relationship and any contribution are TBD.
5.3 Interim treasury
Until the DAO exists, tip fees and other Echosystem funds go to the current treasury canister 5nkyi-eqaaa-aaaao-bbpsa-cai, using the subaccount "treasury". If a transfer to that account fails, the amount is recorded as owed. Control of this account, and the later transfer of funds into an SNS or other DAO treasury, are open questions (see §10).
No funds should be moved except as the founder has explicitly approved, and later as the DAO approves.
6. Governance
6.1 Until the DAO launches
The founder, Gabriel Marciel, directs the work: product, treasury policy, and this charter. That is a bootstrap arrangement, not the destination. Important actions should still be recorded plainly, and the principles in §2 already apply.
6.2 Proposals and voting (once the DAO exists)
Once an SNS (or, if necessary, a custom DAO) is live:
- changes to the apps, the treasury, and this charter should go through public proposals;
- token holders (and any additional voting rules the community later adopts) vote;
- results and treasury movements are visible on-chain.
Exact voting rules — including any departure from standard SNS token-weighted voting — are TBD.
6.3 Founder role and transition
Gabriel Marciel is the founder, and is proposed as CEO and Chief Architect during the bootstrap period and the early life of the Foundation.
A proposed annual salary of $300,000 USD, paid by the Foundation, has been discussed. This is a proposal only. It has not been adopted, no such salary has been paid under this charter, and it would need confirmation once a legal entity exists and, later, once the DAO can approve compensation.
The transition should be deliberate: the founder builds and stewards the system, then canister-control and treasury-control move to the DAO. Any reserved founder powers, and how long they last, are TBD. The aim is a real handoff, not a permanent exception.
6.4 Intended partnership with xAI
The Data Dividend contemplates that part of the remaining profit, after users are paid, could be split with xAI. No agreement with xAI exists. Echo is an independent project. Any relationship with xAI, X, or related companies should be described only as an intended or proposed partnership until a signed agreement says otherwise.
7. The Data Dividend
The Data Dividend is a planned, opt-in way for people to earn a share of the profit when they choose to allow a sale of selected data.
- Off by default. Privacy is the starting point. A person picks which categories to share and can switch any category off at any time.
- Permission is required. We never sell your data without your permission.
- Anonymized aggregates only. Buyers are meant to receive pooled insights — not names, messages, exact location, children's data, or health data.
- The split. 60–70% of data-sale profits go to participating users. The remaining 30–40% is planned to be split between xAI and The Echosystem Foundation. The exact percentages inside those ranges, and the split of the remainder, are TBD. The xAI share depends on a partnership that does not yet exist.
- On-chain money, private data. Every data sale and every payout is to be recorded on the Internet Computer so the money flow can be checked. Personal data itself is never published on-chain.
- Legal review first. The Data Dividend must be reviewed by counsel (including, as applicable, Swiss FADP, EU GDPR, and California CCPA/CPRA) before it launches. It is planned, not built.
8. Relationship with Echo apps
The Foundation is the steward, not a substitute, for the products:
- Echo (echoworld.app) is the user-first social network, including its Market and related surfaces.
- EchoBot is the assistant and bot layer around Echo (including community rooms, introductions, and the bot wallet).
- Other Echosystem apps may be added later under the same principles.
The Foundation is meant to manage ad and sales revenue, the treasury, policy, and (once the DAO is live) upgrades to these apps. The products should remain usable by people who never hold $ECHO and never opt in to the Data Dividend. Opting in is a choice, not a condition of belonging.
App-level rules (terms, privacy, and community rules) remain separate documents. They should stay consistent with this charter, and they also require legal review.
9. Adoption and amendment
This draft has no legal effect until it is adopted in a form counsel has reviewed, by the founder and, after launch, by the DAO.
Amendments should be public. After the DAO launches, amendments should go through the same proposal process as other constitutional changes.
If this charter and applicable law ever conflict, the law wins. The Foundation will still remove what the law requires it to remove. Transparency does not erase legal duties; it makes them visible.
10. Open questions for Gabriel
Please confirm, revise, or defer each of the following:
- Name and marks. Confirm the official name "The Echosystem Foundation," and whether Echo, Echosystem, and $ECHO are clear to use as trademarks in the markets you care about.
- Legal wrapper and home. Which wrapper and jurisdiction should counsel compare first (for example, a Swiss foundation, a Cayman foundation company, a Wyoming DUNA, or another option)? This list is not advice.
- Data Dividend percentages. What exact share within 60–70% goes to users, and how should the remaining 30–40% be divided between the Foundation and a possible xAI partnership?
- xAI. When, if at all, should that intended partnership be discussed with xAI, and on what terms? None exists today.
- $ECHO design. Supply, allocations, vesting, issuance method, and launch timing are all TBD. Which of these should be designed next, and which should wait for counsel?
- Voting. Is standard SNS token-weighted voting acceptable, or do you want a one-person-one-vote or reputation overlay?
- Handoff. When should control of the app canisters and the treasury move to the DAO? Should any founder powers be reserved, and if so, for how long?
- Compensation. Confirm, revise, or defer the proposed $300,000 USD annual salary for the CEO / Chief Architect.
- Interim treasury. Who are the current controllers of canister
5nkyi-eqaaa-aaaao-bbpsa-cai, and when should balances move into an SNS treasury? - Domain. Which domain should the Foundation use? No domain should be purchased until you explicitly approve the name and the spend.
- HydroBit. How should HydroBit relate to the Foundation, and what, if anything, may it contribute to the treasury?
- Market fees. Fees are planned for vehicles, real estate, and jobs, with the rest of the Market mostly free. Which rates, and which other categories, if any?
- Security for outbound $ECHO. If people can later move $ECHO out of the Echosystem, what security steps should exist? They must not be designed or described as an exit charge.
- Community rewards. Do you still want a later contribution reward or community dividend, in what asset, and only after legal review? No amounts are promised in this charter.
- Law and compliance. Which governing law and dispute venue should counsel assume as a starting point, and should a money-transmitter and securities analysis be commissioned before any token work?
End of draft. Prepared for Gabriel Marciel as a working charter for The Echosystem Foundation. Not legal advice. Not an offer to sell any token.