A Token Catalog Entry Does Not Establish a Swap Route
A catalog helps identify or display assets. That is a different job from proving that a particular amount, pair, network and account has an available executable exchange route.
Read what a catalog actually supplies
An entry may contain a name, symbol, network, address and display metadata. These fields can help locate an asset, but they do not describe every liquidity pool, router or integration constraint. Metadata can also be stale or untrusted. Verify the contract against an authoritative issuer or network source when identity matters. A familiar symbol in a long list is not evidence of ownership, legitimacy or transferable value.
Separate four capability questions
Can the interface discover the asset? Can a read-only query obtain its balance? Can a provider return a coherent quote for the intended request? Can the full transaction path be validated and safely offered for signing? Each question needs different evidence. Passing the earlier questions does not answer the later ones. Nonstandard token behavior, unavailable routing, provider limits or application restrictions may prevent progress after discovery succeeds.
Apply the distinction to this interface
RunixCoin’s public form is fixed to Base WETH-to-USDC estimates and public swap execution remains unavailable. Broader catalog entries or network choices elsewhere in the wallet do not expand that form into every visible pair. An asset appearing in search should therefore not be interpreted as an advertisement for a transactional route. Native ETH is also not interchangeable with WETH merely because the two assets have related economic exposure.
Use a precise troubleshooting report
Describe the discovery action separately from the requested quote: selected chain, exact contracts, amount, visible route label and any error. If the form intentionally fixes its pair, record that limitation rather than attempting to force another route with an approval or signature. This page offers no new execution paths. Its purpose is to make capability claims testable and prevent catalog coverage from being confused with verified mainnet exchange functionality.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.