Start from the reserve’s supported asset
Open the token in your wallet and find its token details or explorer link. Reveal the full contract address. Compare it with the corresponding BscScan entry in our supported-token directory or Flap’s asset page.
Check BNB Chain mainnet, chain ID 56. Switching the wallet’s selected network does not move a token from another chain. A balance on another network is not a BNB Chain balance available to this vault.
Match the whole address
For example, our verified asset configuration identifies TSLAon on BNB Chain as:
0x2494b603319d4D9F9715c9f4496d9E0364B59d93
Compare all 40 hexadecimal characters after 0x, not just the beginning and ending. Wallets may show the same address with different letter capitalization. Check the address itself alongside the network, rather than relying on a copied logo, token name or ticker.
If either differs from the supported entry, stop before approval. Adding a custom token to a wallet only makes that token visible; it does not turn it into the supported asset.
Keep the token and the spender separate
The stock-token contract identifies what you hold. The reserve contract is the buyer and the spender you authorize for a stock sale. MAG7X itself has a third, separate token contract. On the desk, choose Supply stocks, then Change to select a supported asset. There is no custom contract-address field.
Our reserve is this BscScan address:
0xEF95e8c5A858875c3AeE167237C37f89761a628F
An approval permits spending; it does not make a sale or pay you BNB.
Identity checked: what comes next?
Enter your quantity on the stock-sale desk; the preview updates automatically. This check establishes that your token matches the reserve’s supported asset, not an audit of its issuer. The quote then checks the intended amount against the vault’s current buying capacity.