How to Import a Custom Token by Contract Address on STON.fi
STON.fi lets users import tokens absent from standard search. Importing a token does not mean STON.fi recommends, verifies, or guarantees it.
1. Get the correct contract address
Obtain the token’s smart-contract address from an official source, such as the project’s website. Do not rely only on a name, ticker, logo, or social post, because malicious tokens can imitate legitimate assets. The contract address identifies the token.
2. Open token search or import
Open STON.fi’s Swap interface and token selector. Use the search or custom-token import option to enter the contract address.
3. Paste and verify
Paste the complete address into the search field. STON.fi can display metadata such as the token name, symbol, and decimals. Compare these details with official project information. A familiar logo or ticker should never replace contract-address verification.
4. Review warnings
Before confirming, check warnings, labels, or restrictions shown by STON.fi. These signals provide context, but they are not a security audit.
Most importantly, manual import is not a safety endorsement. Importing an asset only makes it accessible through the interface. It does not prove that the token is legitimate, secure, or suitable for trading. Research the token independently before use.
5. Check liquidity before swapping
After importing the token, check available liquidity and expected swap conditions. Low liquidity can increase price impact, slippage, and poor execution, especially for large trades. Review pool depth, trade size, quoted output, and price impact before approving a transaction.
The careful workflow is simple: verify the address, import it, confirm metadata, review warnings, research the token, and check liquidity before swapping.
In DeFi, accessibility is not trust. STON.fi provides the interface, while users must verify the asset and understand the risks before signing.
$BTC #BNBChain#
STON.fi lets users import tokens absent from standard search. Importing a token does not mean STON.fi recommends, verifies, or guarantees it.
1. Get the correct contract address
Obtain the token’s smart-contract address from an official source, such as the project’s website. Do not rely only on a name, ticker, logo, or social post, because malicious tokens can imitate legitimate assets. The contract address identifies the token.
2. Open token search or import
Open STON.fi’s Swap interface and token selector. Use the search or custom-token import option to enter the contract address.
3. Paste and verify
Paste the complete address into the search field. STON.fi can display metadata such as the token name, symbol, and decimals. Compare these details with official project information. A familiar logo or ticker should never replace contract-address verification.
4. Review warnings
Before confirming, check warnings, labels, or restrictions shown by STON.fi. These signals provide context, but they are not a security audit.
Most importantly, manual import is not a safety endorsement. Importing an asset only makes it accessible through the interface. It does not prove that the token is legitimate, secure, or suitable for trading. Research the token independently before use.
5. Check liquidity before swapping
After importing the token, check available liquidity and expected swap conditions. Low liquidity can increase price impact, slippage, and poor execution, especially for large trades. Review pool depth, trade size, quoted output, and price impact before approving a transaction.
The careful workflow is simple: verify the address, import it, confirm metadata, review warnings, research the token, and check liquidity before swapping.
In DeFi, accessibility is not trust. STON.fi provides the interface, while users must verify the asset and understand the risks before signing.
$BTC #BNBChain#
