# Proudly crafting a TrustLess future

At the heart of Metanet is a commitment to "TrustLess" design principles, which prioritize five key pillars. These principles minimize the need for personal information, reduce vulnerabilities, and protect user autonomy, freedom, and rights.

#### Here’s a breakdown of Metanet’s five essential pillars: <a href="?path=%23heres-a-breakdown-of-corelas-five-essential-pillars" id="heres-a-breakdown-of-corelas-five-essential-pillars"></a>

1. **Decentralized Name Registry**
   * **Decentralized Identity**: Metanet supports Ethereum Name Service (ENS), Bitcoin Name Service (BNS), and Lens usernames, allowing users to verify ownership through unique names. For instance, a name like "ManojSi.eth" can be securely validated across applications, enhancing trust and security.
   * **Community Ownership Models**: Metanet is exploring systems akin to Substack, enabling community leaders to collect email addresses for seamless audience access.
   * **Flexible Login Options**: Users can log in using phone numbers or email and later enhance security with public/private web wallet keys. Metanet also allows linking multiple wallets, offering unified access to Ethereum and Bitcoin accounts for convenience.
2. **Decentralized Network**
   * **Matrix Integration**: Metanet is built on Matrix.org, an open network providing decentralized communication. Future integrations with technologies like XMTP and Farcaster are being considered to expand user options.
   * **Server Infrastructure**: Metanet currently operates on AWS for experimentation but is exploring decentralized hosting for greater user autonomy.
   * **Home Server Access**: Beta and enterprise users can host their data on personal servers for more control.
3. **Decentralized Storage**
   * **User Data Ownership**: Users retain ownership of their on-chain assets like cryptocurrencies, NFTs, and POAPs via assigned Ethereum wallet addresses.
   * **Beta and Enterprise Options**: Selected users can store their data on private servers.
   * **Chat Data Storage**: Chat data is managed through Matrix’s Synapse server, hosted on Hetzner, with an option for self-hosted storage.
   * **Future Community Activity**: Metanet is exploring a transition to Farcaster hubs for managing community activities.
4. **Open Source Commitment**
   * **Transparency and Collaboration**: Metanet embraces open source software to ensure a high-quality user experience.
   * **Source Code Release**: Plans for releasing Metanet source code are under review. Potential licensing options include the Business Source License (BSL) or a combination of MIT for the frontend and BSL for the backend.
5. **End-to-End Encryption (E2EE)**
   * **Secure Messaging**: E2EE is enabled for all private messages and groups.
   * **Encrypted Audio and Video**: Communications are secured using LiveKit’s encryption technology.

**Metanet's** **Progress and Vision** Some of these pillars are already in place, while others are in development as Metanet works towards a fully "TrustLess" environment.

We highly value feedback and welcome your questions or suggestions as we build this platform. Feel free to contact us at **<support@metanet.one>** to share your thoughts or learn more about our journey.


---

# 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://metanet.gitbook.io/metanet/how-to-use-metanet/proudly-crafting-a-trustless-future.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.