# Problems

### <mark style="color:green;">**Tedious Interaction Experience across Multi-Dapps**</mark>

In 2014, Ethereum revolutionized the blockchain industry by introducing smart contracts, empowering developers to create a multitude of innovative DApps.&#x20;

However, ordinary users are often faced with complex and tedious interactions, having to navigate multiple DApps to achieve their desired goals. While developers and scientists can easily streamline these processes through coding and deploying smart contracts, the lack of coding abilities hinders ordinary users from enjoying seamless and efficient interactions. Unless developers have the resources and capabilities to package these functionalities into user-friendly DApps for widespread adoption and profitability, they may lack the incentive to share these simplified features with the general user base.

{% tabs %}
{% tab title="Complex Interaction" %}
*Example of a user with USDC on Arbitrum wants to mint and sell 3 NFTs (one per address) on ZKsync Era:*

<figure><img src="/files/4mqLQEQaQtHf230K1eu4" alt=""><figcaption><p>Complex Interaction Example</p></figcaption></figure>
{% endtab %}
{% endtabs %}

### <mark style="color:green;">Inequality in Smart Contract Adoption Between Ordinary Users and Developers</mark>

Some scientists may develop some bots and deploy smart contracts with unique functionalities like flash loans, copy trading, launch sniping, etc., granting them a competitive edge over ordinary users.

This disparity in access to advanced smart contract features acts as an obstacle to the widespread advantage of Ethereum to a more general user base.


---

# 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://a3sprotocolcontact.gitbook.io/a3s-protocol/about-a3s-protocol/problems.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.