Wallet safety
How to Verify an EXN Token Contract Before Connecting Your Wallet
A token name, logo or social-media post is not enough to establish that a wallet prompt is pointing to the intended contract. This guide gives a practical way to verify the published EXN references before you connect a wallet, approve USDT or sign a transaction.
Start with the official Facts page, not a search result
The safest starting point is a first-party page that identifies the project, network and contract references. For Expoin, that page is Official Expoin Facts. It lists the published EXN token contract and token-sale contract, together with the stated sale network and payment asset. Treat the page as the source to compare against—not as a replacement for independent verification.
Do not begin with an address copied from a direct message, an ad, a reply thread, a screenshot or an unaffiliated token list. Those channels can imitate a project name and use a visually similar address. Bookmark the official domain yourself. When you revisit the page, check that the browser address is exactly expoin.net and that the page URL is /facts/.
The published EXN token reference on the Facts page links to BscScan. The published sale-contract reference links there too. Follow those links from the page rather than manually retyping an address. A single missing or changed character means a different address.
Confirm the network before reading a contract
Contract addresses are network-specific. An address can have the same character sequence on more than one EVM-compatible chain, while referring to different code or no contract at all. The published EXN sale information identifies BNB Smart Chain mainnet and USDT on BSC (BEP-20) for the described sale flow. Confirm those details on Facts and again in your wallet before you approve anything.
That double check matters because a wallet can display a familiar token symbol without telling you whether it belongs to the intended chain. If your wallet is on a different network, stop rather than trying to force the transaction through. Switch only after you have independently checked the target network and contract. If a prompt asks you to add a network, verify the configuration through a trusted source before accepting it.
Network confirmation also means accounting for gas. BSC transactions require the appropriate native asset for network fees. A lack of gas, congestion or an incorrect chain can cause a transaction to fail. A failure may still cost a network fee, so review the confirmation screen carefully.
Compare the full address, not just the first and last characters
Wallet interfaces often abbreviate addresses by displaying only the first and final characters. That format is useful for recognition, but it is not a verification method. Open the BscScan page from Facts and compare the complete address shown by the explorer with the complete address in the application or wallet confirmation.
For the published references at the time of this guide, the Facts page links to the EXN token contract and a separate token-sale contract. They have different purposes and therefore different addresses. A request to approve spending normally concerns the payment token and a spender address; it does not mean that the spender is the EXN token contract. Read the label and the full address on every approval prompt.
Never assume that an approval, transfer or contract-interaction prompt is safe because it displays “EXN”, “USDT” or the project name. The authoritative detail is the full address, the connected network and the exact permission requested.
Use BscScan as an independent cross-check
BscScan is a public blockchain explorer for BNB Smart Chain. After opening the official link, use it to inspect the address page and make sure you are viewing the address you intended to verify. The explorer can provide contract details, token information, transaction history and verified-code indicators when those data are available. It does not remove risk, but it helps you avoid relying solely on a website interface.
There are several useful comparisons to make. First, compare the full address in the URL and page header with the address published on Facts. Second, ensure you are on the BSC explorer page, not an unrelated domain that resembles it. Third, read any warnings or labels that the explorer displays. Fourth, if you are considering a sale interaction, compare the spender or destination shown in your wallet with the published sale-contract reference—not simply with a token symbol.
A visible explorer page does not confirm commercial terms, security, liquidity or future value. Do not infer an audit, listing or performance claim from an explorer entry. Expoin’s public sale information directs users to the Token Sale Terms, Risk Disclosure and the Facts page for the published reference set.
Review the transaction type and permission scope
Connecting a wallet, approving a token allowance and sending a transaction are different actions. A connection typically lets a site view a public address. An approval can give a contract permission to spend a payment token up to a stated amount. A purchase or transfer submits an on-chain transaction, which can be irreversible after confirmation.
Before signing, read the wallet prompt slowly. Check the active account, network, contract or spender address, token, amount and requested permission. If the wallet presents an unlimited allowance when you expected a limited amount, pause and investigate. If the amount, destination or network differs from the published information, reject the prompt and return to the official source pages.
Record the public transaction hash after a completed transaction and inspect it independently in BscScan. Do not share private keys, seed phrases, recovery codes or signing secrets with support. Legitimate support should not ask for them. The Contact page explains what information can be shared safely when reporting a public transaction issue.
Check the current sale reference and vesting separately
Contract verification is only one part of informed participation. The published Community OG reference listed on Expoin’s current static information is US$0.0250 per EXN, with a 12-month lockup followed by 18 months of linear vesting. These values may change, and a guide cannot confirm an active on-chain round. Check the live contract readout and the current EXN sale information before deciding whether to interact.
Read vesting as a delivery schedule, not as a forecast. A lockup or linear release does not guarantee token availability, a trading venue, liquidity or a price. Likewise, a roadmap expresses planned work unless it is accompanied by dated delivery evidence. For allocation context, see EXN Tokenomics; for product direction, see the roadmap status policy.
Know when to stop
Stopping is the right outcome whenever you see a mismatch or do not understand a prompt. Stop if the domain is unfamiliar, the network differs, the full address cannot be matched, a wallet asks for a secret, the requested allowance is not what you expect, or a third party claims urgency. You can always return later after verifying with a trusted source or seeking independent professional advice.
Be particularly cautious with claims of guaranteed returns, automatic profit, dividends, “risk-free” yields, special support channels or pressure to use a new address. Expoin’s public pages do not promise price performance, returns, liquidity, listings or security outcomes. The presence of a contract address is not a recommendation to interact with it.
A repeatable verification checklist
- Open expoin.net/facts/ directly or from a saved bookmark.
- Confirm the product, network and payment reference relevant to your intended action.
- Open the linked BscScan page and compare the complete contract address.
- Check that your wallet is on the intended network before connecting or signing.
- Read the wallet prompt: account, contract/spender, token, amount, allowance and network.
- Read Token Sale Terms and the Risk Disclosure.
- Reject and investigate any mismatch; never provide a seed phrase or private key.
- After a transaction, retain the public transaction hash and check it in BscScan.
Keep this guide current
Contract references and product terms are change-sensitive. This article is dated 1 September 2026 and should be reviewed whenever the published Facts page, sale terms, network support or contract references change. The authoritative project reference remains Facts; use the Expoin Blog for explainers and the documentation for product guidance.