Receive Link FAQ
Can the recipient only receive tokens through the KEYRING Email Wallet?
Yes, to receive tokens sent via email, the recipient must use the KEYRING Email Wallet, which means the email address must be used to create a KEYRING Email Wallet account.
What happens if I send tokens to an email that does not have a KEYRING Email Wallet account?
No need to worry. If the recipient's email address does not have a KEYRING Email Wallet account, clicking the login link in the email will redirect them to a page where they can create or log into their account.
The recipient can then register using that email address and receive the tokens. Please note that the email used to create the KEYRING Email Wallet account must match the email to which the tokens were sent.
How many emails can I send tokens to at most?
The Receive Link feature allows you to send tokens to a single email by entering the recipient's email address. Additionally, you can send tokens to multiple emails at once by using a CSV file that contains a list of email addresses and the amount of tokens to be sent.
For sending tokens to multiple emails, the maximum number of email addresses you can include in a single batch is 200. If you need to send tokens to more than 200 emails, you will need to split the list into multiple batches.
What happens to the tokens sent if the recipient does not claim them?
Once tokens have been sent, they cannot be retrieved due to the blockchain contract. Once the transaction is complete and recorded on the blockchain, it cannot be undone.
If the recipient does not claim the tokens from the email, the tokens will remain in the email until the recipient creates a KEYRING Email Wallet account and claims them.
Therefore, it is crucial for the sender to carefully check the email list before sending to avoid errors or sending tokens to emails with low open rates. Unfortunately, we cannot assist with retrieving tokens once they have been sent.
Is there a fee to create a Receive Link?
Yes, there are fees associated with creating a Receive Link. The sender will incur two types of fees:
Gas Fee for Transactions
In the current blockchain environment, all on-chain activities require a gas fee. The amount of this fee depends on the blockchain used.
When creating a Receive Link to send tokens to emails, the sender will need to pay the gas fee for these transactions. This fee is variable and depends on the blockchain and the transaction load.
Note that the sender must have the native token of the chosen blockchain to cover the gas fee.
Service Fee
The Receive Link is a new and innovative feature of KEYRING Email Wallet. We charge a small service fee for providing this feature:
This is a fixed fee, and its value will not change unless we notify you of an update.
The fee is based on the number of emails receiving the Receive Link. (For example, if the service fee is $0.20 and you send 10 emails, the total fee will be $0.20 x 10 = $2.)
The service fee varies depending on the blockchain chosen by the sender. Currently, we support two blockchains: Polygon (MATIC) and Avalanche (AVAX). We will update this list as we add support for additional blockchains.
MATIC: $0.2
AVAX: $0.4
BNB: updating
OP: updating
ARB: updating
Through which chains can tokens be sent?
Currently, we support the following two blockchains for senders:
MATIC
AVAX
In the future, we will add support for the following additional blockchains:
BNB
OP
ARB
How can I send tokens if the token I want to send is not on the list?
Don’t worry if the token you want to send is not on the list; you can add it by importing the token:
Click on the token icon you want to send to open the "Select a Token" interface.
Switch to the "Import Token" tab.
Enter the correct token contract address of the token you want to send.
Once the correct token contract is entered, token information will be displayed. Double-check the details.
If the information is correct, click "Next."
Click "Add" to include the token for sending.
What is a token contract address?
A token contract address is a unique identifier on a blockchain (like Ethereum) that points to a specific smart contract managing a token.
It’s like an account number for that token, handling how tokens are created, distributed, and transferred. You need this address to use or interact with the token in various apps and services.
What is Token Standard?
A token standard is a set of rules and guidelines that a token must follow on a blockchain. These standards ensure that tokens can be easily created, managed, and used within the blockchain ecosystem.
All tokens created on a blockchain must conform to a specific token standard. For KEYRING Email Wallet, we support the following three token standards:
ERC-20: a popular token standard on the blockchain. This standard makes it easy for developers to create tokens that can work seamlessly with wallets, exchanges, and other smart contracts.
ERC-721: a token standard for creating unique, non-fungible tokens (NFTs). Unlike ERC-20 tokens, each ERC-721 token is distinct and used for items like digital art and collectibles.
ERC-1155: a token standard that allows for the creation of both fungible (interchangeable) and non-fungible (unique) tokens within a single contract. This means you can manage multiple types of tokens, like digital art and in-game items, with one smart contract, making it more efficient and flexible.
Why are there differences in the way the three types of token standards are sent?
The differences arise from the inherent characteristics of the three token standards, which affect the options available when creating a Receive Link:
ERC-20
This token standard is used for creating various cryptocurrencies. ERC-20 tokens are identical, meaning they hold the same value and can be exchanged with one another.
As a result, when creating a Receive Link, the sender can send different quantities of ERC-20 tokens to multiple email addresses simultaneously.
ERC-721
This token standard is used for NFTs (Non-Fungible Tokens). NFTs cannot be exchanged on a one-to-one basis because each NFT is unique.
Therefore, when creating a Receive Link for ERC-721 tokens, the sender can only send one NFT per email address at a time. The ERC-721 tab does not support sending multiple emails using a CSV file.
ERC-1155
This standard combines aspects of both ERC-20 and ERC-721. Initially, ERC-1155 tokens are similar to ERC-20 tokens in that they are interchangeable and have the same value. However, under certain conditions, they can become non-interchangeable, similar to ERC-721 tokens.
For example, concert tickets are equivalent and exchangeable before the event, but once the event begins, they are unique to their holders. Due to this feature, ERC-1155 tokens can be sent in bulk to multiple email addresses, similar to ERC-20 tokens, and supports sending multiple tokens to different emails using a list.
Is the token claiming process the same across the three token standards?
es, while there are differences in the sending process between the three token standards, the claiming process is the same for all three.
You can view the process here:
How to claim tokenHow can I check for the NFT contract and the NFT ID?
There are several ways for users to check an NFT contract and NFT ID. However, for convenience and ease of use, we recommend using the KEYRING NFT Viewer. This tool is incredibly useful, as it allows users to quickly find the NFT contract address and NFT ID without requiring them to log in or connect a wallet.
Visit the KEYRING NFT Viewer website.
Enter the wallet address containing the NFT you want to view and click "search."
Select the chain containing the NFT.
Select the NFT you want to check, and you will see the necessary information.
Last updated
