> For the complete documentation index, see [llms.txt](https://redefined.gitbook.io/connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://redefined.gitbook.io/connect/user-starter-guide/how-does-it-work.md).

# How does it work ?

Through the redefined [dApp](https://app.redefined.org/), you can register your Web3 Smart Profile to manage all your identities. Whether you are an individual, community, gamer, or professional, you can now leverage the power of redefined: Profiles to Share, Demo, Send, Receive, Verify, and more.\
\
Link all your identities, addresses, or any of the [supported](/connect/integerate-redefined/supported-providers.md) Social IDs, Domains, or Name services to your profile. Even though the SCs "smart contracts" for Registration and Managing records are currently deployed on the Arbitrum One network, we leveraged the Axelar Network through our Squid router integration, allowing the registration, managing, and all interactions of your profile to be from any evm chain at all times.\
\
To achieve a genuinely Cross-chain experience, you shouldn't care about the underlying blockchain for universal usage anymore.

The redefined: Smart Profiles enable users to register their preferred username or email address as a unified identifier for the entire Web3 ecosystem. This simplifies the complexity of fragmented identifiers and allows for seamless sending and receiving of crypto assets across multiple blockchains.

The redefined dApp is compatible with Metamask Wallet and WalletConnect.\
Here is a [list](https://explorer.walletconnect.com/?type=wallet) of all supported wallets by WalletConnect.

\
If you don't have a wallet yet, Here is a [Guide](https://support.metamask.io/hc/en-us/articles/360015489531-Getting-started-with-MetaMask) to Creating your first.<br>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><p>How to Send?</p><p></p></td><td></td><td><a href="/pages/7E4uZbpNVeGhDIVJohoT">/pages/7E4uZbpNVeGhDIVJohoT</a></td></tr><tr><td></td><td>How to register a Username?</td><td></td><td><a href="/pages/QZyLypzmuyW0wK1fii0w">/pages/QZyLypzmuyW0wK1fii0w</a></td></tr><tr><td></td><td>How to register an Email?</td><td></td><td><a href="/pages/oTuioMRYexdvBtDMsfou">/pages/oTuioMRYexdvBtDMsfou</a></td></tr></tbody></table>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://redefined.gitbook.io/connect/user-starter-guide/how-does-it-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.