# About PoPwallet

{% hint style="danger" %}
**This is `alpha`, WorldApp login should be in**[ **staging mode**](https://simulator.worldcoin.org/)
{% endhint %}

{% hint style="warning" %}
Currently, we support **Ethereum mainnet only** (will support more chain soon**)**
{% endhint %}

## Overview

<figure><img src="/files/7pRnxIvNd7VmS4YUb5O0" alt="" width="188"><figcaption><p>PoPwallet</p></figcaption></figure>

With [**worldapp**](https://worldcoin.org/) authentication, an on-chain user can "**link**" one address per chain in the **PoPwallet** to authenticate that the linked address is the only one in that chain.&#x20;

In the existing crypto ecosystem, there is an invisible war going on between **multi-accounters** and **foundations**. There are a lot of battles going on to stop sybil attacks. For example, [**Paraswap**](https://www.paraswap.io/) has effectively defended against it by using wallet tracing. ([**ref.**](https://decrypt.co/86509/paraswap-just-rewrote-the-rules-on-airdops)*)*&#x20;

<figure><img src="/files/jhD1tg973grOg4U12FPz" alt=""><figcaption><p>Transaction map of metasleuth</p></figcaption></figure>

In response, **multi-accounters** are referring to tools like [**metasleuth**](https://metasleuth.io/) to bypass it, and even checking transaction paths to hide the origin of tokens by sending Ethereum from different **CEX**. As this battle continues, the labor and computing resource drain of increasingly complex transactions will increase. For now, the best way to prevent it is not captcha, not a bunch of web-2 authentication, but [**Worldapp**](https://worldcoin.org/).&#x20;

<figure><img src="/files/t0c3Io7kSJFFxJCbmmi4" alt=""><figcaption><p>Worldcoin ORB</p></figcaption></figure>

A worldapp is an **unique**, biometrically authenticated proof of personhood that can't be easily replicated.&#x20;

<figure><img src="/files/E30QQsKHXZIPcnhLqIzw" alt=""><figcaption><p>PoPwallet dapp</p></figcaption></figure>

**We can simplify authentication between dapps and on-chain users**. Users don't need to authenticate through the app every time they access another dapp, and the dapp only needs to verify that the address is authenticated using our API **without any transactions**. It's incredibly **simple & fast** protocol for providers and users alike.

The difference between our project and POAP is that it cannot be traded and cannot be migrated. **Users can assign an address to each chainid** permanentl&#x79;**.** (with a wallet connection, of course!!) This should be linked very **carefully** and in most cases **irreversibly** (unlinking it for reasons like lost mnemonics would be a huge effort).

\
\&#xNAN;*`In other words`**`, PoPwallet is anti-multi-wallet protocol!`***

## Quick links

{% content-ref url="/pages/uyzgFdLx8VInqAj419hE" %}
[Listup](/popwallet/api/listup.md)
{% endcontent-ref %}

{% content-ref url="/pages/zwfZY4ArLurEQBfdmz4E" %}
[API Common Guide](/popwallet/api/api-common-guide.md)
{% endcontent-ref %}


---

# 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://popwallet-api.gitbook.io/popwallet/about-popwallet.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.