> For the complete documentation index, see [llms.txt](https://docs.4everland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.4everland.org/get-started/quick-start-guide/login-options.md).

# Login options

4EVERLAND currently supports three types of login, wallet login, Github account login and Telegram account login.&#x20;

<figure><img src="/files/PFd6YipNJl04PgICIh5w" alt=""><figcaption></figcaption></figure>

## Wallet login

1. To use Web3 Wallet, select your usual wallet on the [following page](https://dashboard.4everland.org/login) and wait for the wallet to respond.
2. Select 'Sign' in the pop-up box to authorize.

<figure><img src="/files/BiEF6Xwst3UCe1GfyjQh" alt=""><figcaption></figcaption></figure>

3. Please visit the following sub-pages to find more information about the wallets.

{% content-ref url="/pages/lfbQ7oAwpfRMGcc7eEn6" %}
[MetaMask](/get-started/quick-start-guide/login-options/metamask.md)
{% endcontent-ref %}

{% content-ref url="/pages/BpZHE1OPQvQ7oaBt2GrX" %}
[Phantom](/get-started/quick-start-guide/login-options/phantom.md)
{% endcontent-ref %}

{% content-ref url="/pages/Bnq3SatuzFDniB7Bvh8s" %}
[Binance Web3 Wallet](/get-started/quick-start-guide/login-options/binance-web3-wallet.md)
{% endcontent-ref %}

{% content-ref url="/pages/lVxf45uqw2C3fwxltlp9" %}
[Bitget Wallet](/get-started/quick-start-guide/login-options/bitget-wallet.md)
{% endcontent-ref %}

{% content-ref url="/pages/1Lx4S1Pr5xxnMWlmXCkW" %}
[Lilico](/get-started/quick-start-guide/login-options/lilico.md)
{% endcontent-ref %}

{% content-ref url="/pages/M7oxsSODYeqXxANeneIX" %}
[Petra](/get-started/quick-start-guide/login-options/petra.md)
{% endcontent-ref %}

{% content-ref url="/pages/7uV00W0ktBrJlwNz56jb" %}
[OKX Wallet](/get-started/quick-start-guide/login-options/okx-wallet.md)
{% endcontent-ref %}

## Github login

Github registration for new users is not currently supported. If you are an early registered member, please link your Github account to 4EVRLAND by doing the following:

Click to 'Continue with Github'.

<figure><img src="/files/q77X55vZhn6kIdW2sAPw" alt=""><figcaption></figcaption></figure>

Sign in to your Github account on the pop-up page.

<figure><img src="/files/7VbvYBbiTN5Rufqrf5oI" alt=""><figcaption></figcaption></figure>

## Telegram login

When users log in with Telegram, 4EVERLAND will first attempt to connect to your Telegram account. Click 'Continue with Telegram' and then select 'Log in as UID' in the pop-up window.

<figure><img src="/files/JUaMbbBA5Afpmb4I2Sar" alt=""><figcaption></figcaption></figure>

Now you have successfully logged into 4EVERLAND, and you will be redirected to the Dashboard page, please read the '[Usage Introduction](/get-started/quick-start-guide/usage-introduction.md)' page to find out how the Dashboard works.

{% hint style="info" %}
For more on InfoSec, please check out the page [Security](/more/security.md).
{% endhint %}


---

# 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://docs.4everland.org/get-started/quick-start-guide/login-options.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.
