Test transfer behavior before choosing an Orbit custom gas token
A parent-chain ERC-20 can be valid for ordinary wallet transfers while violating assumptions made by an AnyTrust chain’s custom gas-token bridge. Evaluate the token implementation before configuring the chain.
Check received amount and token invariants
In a controlled test, compare the sender and recipient balances before and after a transfer. The example reveals a transfer fee. Current documented custom-token requirements exclude fee-on-transfer and rebasing tokens and impose additional behavioral constraints.
requested transfer: 1,000 units
recipient increase: 990 units
unaccounted delta: 10 units
A bridge expecting 1,000 units of backing cannot account for 1,000 newly credited child units when it actually received only 990. Also inspect the implementation for configurable fee switches, upgradeability and behavior on zero transfers.
Match the deployment mechanism
Apply the requirements for the specific AnyTrust custom-token deployment and version being evaluated. Other native mint/burn or rollup configurations have their own rules. A successful token transfer in a test wallet does not validate the complete bridge configuration. docs.arbitrum.io Arbitrum documentation