# User Layer

💡 **Objective:**

* Enable seamless **onboarding of Web2 users into Web3** without requiring prior blockchain knowledge.
* Build a **high-quality Web3 user base** that serves as the foundation for dApp distribution.

💡 **Challenges:**

* **Complicated wallet setups** discourage Web2 users from entering Web3.
* **High gas fees** create a financial barrier for casual users.
* **Lack of user data insights** results in inefficient user engagement strategies.

💡 **Eragon's Solutions:**

1️⃣ **Social login Accounts**

* **Eliminates complex wallet setups** by allowing users to log in via **email, phone number, or social media accounts**.
* Users do not need to **remember or store seed phrases**, significantly reducing friction for mass adoption.

2️⃣ **Gasless Mechanism**

* Users can interact with dApps **without having to hold tokens for gas fees**.
* This **removes friction** and **increases user engagement**, making Web3 applications more accessible.

3️⃣ **Smart User Funnels – Intelligent User Conversion Mechanisms**

* Eragon implements **various user engagement mechanism** through:
  * **Free-to-mint rewards** – Allowing users to claim free digital assets.
  * **Loyalty tokens/points** – Rewarding active users with tokens.
  * **Proof of Play (PoP), Proof of Spend (PoS), and Proof of Verification (PoV)** to validate user activity and behavior.

📌 **Conclusion:** **Eragon removes Web3 entry barriers**, facilitating smooth onboarding while creating a **well-structured Web3 user base** ready for dApp engagement.


---

# 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://whitepaper.eragon.gg/eragon-solutions/user-layer.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.