> For the complete documentation index, see [llms.txt](https://npayme-reward.gitbook.io/npayme/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://npayme-reward.gitbook.io/npayme/businesses/rewarded-actions/on-chain-rewarded-actions.md). # On-chain Rewarded Actions We set out to support businesses in creating incentives for their users to interact with smart-contracts and invest in their tokens. ## Action Types ### Fungible (ERC20 & Native) ### Deposit Tokens This action rewards users for locking up their tokens in a smart contract that earns interest or yield. #### Supported Action Conditions: * The network where the transaction takes place * The contract address of the recipient pool/vault * The ERC20 address of the asset to deposit - 0x0 indicates the Native currency of the chain * The amount of tokens to be transferred * The minimum days the funds must stay in the pool ### Mint Tokens This action rewards users for creating new tokens that represent some value or utility. \ If your vault emits receipt-tokens this action can also be used to incentivise deposits in conjunction with the **Hodl Tokens** below. #### Supported Action Conditions * The network where the transaction takes place * The ERC20 address of the asset to mint * The amount of tokens to be minted ### Hodl Tokens This action rewards users for holding their tokens for a certain period of time without selling or transferring them. By holding tokens, users prove they believe in a project long-term and reduce the circulating supply increasing scarcity. #### Supported Action Conditions * The network where the transaction takes place * The ERC20 address of the asset to hodl - 0x0 indicates the Native currency of the chain * The amount of tokens to be hodled * The minimum days the funds must stay in the wallet ### Burn Tokens This action rewards users for destroying their tokens permanently, reducing the total supply and increasing the scarcity. #### Supported Action Conditions * The network where the transaction takes place * The ERC20 address of the asset to burn * The amount of tokens to be burned ### Purchase Tokens This action rewards users for buying tokens from a decentralized exchange (DEX) that allows peer-to-peer trading without intermediaries. By purchasing tokens from DEX, users can increase the liquidity and demand for the webapp’s tokens #### Supported Action Conditions * The network where the transaction takes place * The ERC20 address of the asset to buy * The amount of tokens to receive * The contract address from which tokens should be sent - this can be a DEX Pair or it's Router ### Sell Tokens This action rewards users for selling tokens to a decentralized exchange (DEX) that allows peer-to-peer trading without intermediaries. By selling tokens from DEX, users can realize their profits and free up their capital for other opportunities. #### Supported Action Conditions * The network where the transaction takes place * The ERC20 address of the asset to sell * The amount of tokens to transfer * The contract address to which tokens should be sent - this can be a DEX Pair or it's Router ### Swap Tokens This action rewards users for exchanging one token for another token on a decentralized exchange (DEX) that allows peer-to-peer trading without intermediaries. #### Supported Action Conditions * The network where the transaction takes place * The contract address of pool or exchange - can be a Pool or a Router * The ERC20 address of the asset to buy * The amount of tokens to receive * The ERC20 address of the asset to sell ### Non Fungible Tokens (ERC721) ### Mint NFT This action rewards users for creating unique digital assets that represent some form of art, collectible, or utility. #### Supported Action Conditions * The network where the transaction takes place * The contract address ### Hodl NFT This action rewards users for holding their NFTs for a certain period of time without selling or transferring them. #### Supported Action Conditions * The network where the contract is deployed * The contract address of the collection * The minimum amount of days to hodl the token for ### Burn NFT This action rewards users for destroying their NFTs permanently, reducing the total supply and increasing the scarcity. #### Supported Action Conditions * The network where the transaction takes place * The contract address ### Buy NFT This action rewards users for buying NFTs from a marketplace that allows peer-to-peer trading without intermediaries. By buying NFTs, users can increase the liquidity and demand for the NFTs. #### Supported Action Conditions * The network where the transaction takes place * The contract address ### Sell NFT This action rewards users for selling NFTs to a marketplace that allows peer-to-peer trading without intermediaries. By selling NFTs, users can realize their profits and free up their capital for other opportunities. #### Supported Action Conditions * The network where the transaction takes place * The contract address --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://npayme-reward.gitbook.io/npayme/businesses/rewarded-actions/on-chain-rewarded-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.