Transfer filters
Intro
Sometimes your users will make mistakes in their deposits. For example, users can send a token to the AppAgent that doesn't support this particular token. Such cases lead to the loss of tokens [for users] or to the need to make manual interventions and to send those tokens back [for companies]. Transfer filters are designed to solve this issue by allowing you to predetermine what fungible tokens and NFT Collections you want to receive from users.
Transfer filters for Fungible tokens
You can configure which fungible tokens can be deposited to Transactional addresses of your AppAgent. The options for configuration are:
AllowAll
: Allow deposits of all fungible tokens;AllowedFungibleTokens
: Allow the deposits only with the explicitly listed tokens. This mode allows to set minimum / maximum deposit amount for each listed token individually;DisallowedFungibleTokens
: Ban deposits of listed tokens and allow deposits of all other tokens;
Transfer filters for NFTs
You can configure which NFTs can be deposited to Transactional addresses of your AppAgent. The options for configuration are:
AllowAll
: Allow deposits of NFTs from all NFT collections;AllowedNftCollections
: Allow the deposits only with the explicitly listed NFT collections;DisallowedNftCollections
: Ban deposits of listed NFT collections and allow deposits of all other NFTs;
Transfer filters for TRAIT Token
You can allow / disallow deposits of TRAIT token. Also you can set min / max deposit amount.
Blocks of transactional addresses
Transfer filters allows certain TAs to be blocked from receiving deposits. Whenever a transaction involves a blocked address, the transaction is stopped.
Default configuration
The default configuration of transfer filters for a newly created AppAgent allows deposits of fungible tokens and NFT collections owned by the AppAgent and prohibs deposits of all other tokens. Also it allows deposits of TRAIT token.
AppAgent Owner can change this configuration.
Last updated