# The MetaLife Web3.0 Metaverse

In web2.0, users profiles, content, data and their activities are all stored on the cloud in servers; applications are running in servers owned by the operators.  User identity is given and authenticated by operators as well.  As a user, you basically own nothing and the operator can wipe you out or lock you down, deny your access to the content you created.

In terms of privacy, peers are not connected to each other directly as they communicate; rather, operator is the intermediary that convey your message.

![A Centralized Web 2.0](/files/GZNuVKweVrrNooHV9JiG)

The emerging of blockchain technology brought about web2.5 where decentralization was made possible.  But in general, decentralization is mostly limited to introduction of token in the rewarding system and identity provided by wallet address; most social networks continue to rely on servers for its core functionality and content storage. &#x20;

As seen in recent humanity crisis around the world, no one digital application, centralized or decentralized can remain functional when internet is taken out.  Freedom of speech and a democratic social media can’t exist if social network continue to rely on servers and internet.

![Web 2.5 with Decentralized tokenomics and identity ](/files/J1FSIzxKSCZeMFnd320T)

**MetaLife Web3.0 Social Network Protocol removes server totally**.  Instead, application, storage, authentication, signing of messages are all done at the mobile device which host a micro-chain with complete merkel tree, providing ultimate security and privacy. &#x20;

![The MetaLife Web 3.0 Protocol](/files/ipwGqodD68XAyMhVvH51)

Within the MetaLife Web3.0 social network, users are connected directly with each other, cryptographically signed data is replicated peer-to-peer without any intermediary.

MetaLife is building the truly liberated Web 3.0 social network that can operate with or without internet.


---

# 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://docs.metalife.social/metalife/understanding-metalife/the-metalife-web3.0-metaverse.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.
