What FLUID represents
Fluid (FLUID) is available in network-specific native or token forms. Fluid belongs to the token category and must be verified through its network-specific native label or contract representation.
Review FLUID network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Fluid (FLUID)
Type
token
Available networks
6
Native networks
Contract token
Route support
Not currently available
Fluid (FLUID) is available in network-specific native or token forms. Fluid belongs to the token category and must be verified through its network-specific native label or contract representation.
Fluid belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Ethereum, Plasma, Solana, Base, Polygon zkEVM, Arbitrum; network gas remains a separate native balance.
Ethereum (contract), Plasma (contract), Solana (contract), Base (contract), Polygon zkEVM (contract), Arbitrum (contract)
Confirm the FLUID network, contract or native label, and receiving address before using a route. Do not identify FLUID solely by ticker; verify the asset and network representation. FLUID can use different contracts on different networks.
Sasquatch does not currently list a transaction route for Fluid. Asset metadata is not proof of a live provider route.
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
FLUID is contract-based on Ethereum, Plasma, Solana, Base, Polygon zkEVM, Arbitrum. Use the exact route representation rather than the ticker alone.
No native origin is recorded in this registry. Network gas is paid with each chain's native asset, not automatically with FLUID.
Ethereum, Plasma, Solana, Base, Polygon zkEVM, Arbitrum
Sasquatch does not currently list a transaction route for Fluid.
Confirm the FLUID network, contract or native label, and receiving address before using a route. Do not identify FLUID solely by ticker; verify the asset and network representation.