> For the complete documentation index, see [llms.txt](https://docs.wallid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wallid.io/config-dashboard/data-verification/blockchains/lukso.md).

# LUKSO

You can customise verification conditions based on users' ownership of <mark style="color:purple;">`LUKSO`</mark> tokens. This section serves as a guide to help you to setup those configs.&#x20;

### Select type of token

To get started, select <mark style="color:purple;">`LUKSO`</mark> Assets in WalliD dashboard. You'll have to choose from <mark style="color:purple;">`Fungible tokens`</mark> (LSP4, LSP7) or <mark style="color:purple;">`NFTs`</mark> (LSP8). You can mix token types and bundle as many tokens as you wish in the same config.

<figure><img src="https://862418018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb6AQcBnq7Bisre4oTTm9%2Fuploads%2FRaZvGF5e6R37X4AV1jjs%2FSign%20up.png?alt=media&amp;token=980e69bd-3109-4087-b67e-eab378bd3a2d" alt=""><figcaption></figcaption></figure>

### Fungible token configs

**Token type** - Choose from<mark style="color:purple;">`LSP4, LSP7`</mark> or <mark style="color:purple;">`LSP8`</mark> (LYXe token).

**Smart contract address** - Paste the <mark style="color:purple;">`smart contract address`</mark> of the token you wish to add to your verification config. If you've selected native, this field will automatically be filled.

**Minimum amount held** - Define the value for the <mark style="color:purple;">`Minimum amount`</mark>t of tokens held by the user for a successful verification.

**Max amount held** - Define the value for the <mark style="color:purple;">`Max amount`</mark> of tokens held by the user for a successful verification.

A**dd another level** - Add more values to the <mark style="color:purple;">`Max amount`</mark> held and <mark style="color:purple;">`Minimum amount`</mark> held to create different levels of verification based on token ownership.

<figure><img src="https://862418018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb6AQcBnq7Bisre4oTTm9%2Fuploads%2FzTJvaWJUshgLFU8wkDrg%2FSign%20up%202.png?alt=media&amp;token=1b34d857-0221-4dfc-a40e-da18dc5bdb52" alt=""><figcaption></figcaption></figure>

### NFT configs

**Token type** - Choose <mark style="color:purple;">`LSP8`</mark> token type.

**Smart contract address** - Paste the smart contract address of the token you wish to add to your verification config.

**Minimum amount held** - Define the value for the <mark style="color:purple;">`Minimum amount`</mark> of tokens held by the user for a successful verification. The verification will ignore any specificities of the tokens and their IDs.

**Max amount held** - Define the value for the <mark style="color:purple;">`Max amount`</mark> of tokens held by the user for a successful verification. The verification will ignore any specificities of the tokens and their IDs.

**Unique ID -** Provide the <mark style="color:purple;">`#ID`</mark> of a specific NFT you wish to verify ownership of. If the NFT is hosted on an <mark style="color:purple;">`LSP8`</mark>contract, you can also define a <mark style="color:purple;">`Minimum amount`</mark> and <mark style="color:purple;">`Max amount`</mark> of tokens held by the user for a successful verification.

**Add another level** - Add more values to the <mark style="color:purple;">`Max amount`</mark> held and<mark style="color:purple;">`Minimum amount`</mark> held to create different levels of verification based on token ownership.

<figure><img src="https://862418018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb6AQcBnq7Bisre4oTTm9%2Fuploads%2F4z6tsfLYvAfp1n6QmLyM%2FSign%20up%203.png?alt=media&amp;token=f13510f3-3a13-4408-aebe-1fcba9adc865" alt=""><figcaption></figcaption></figure>
