What REUSD represents
Re Protocol reUSD (REUSD) is available in network-specific native or token forms. Re Protocol reUSD belongs to the token category and must be verified through its network-specific native label or contract representation.
Review REUSD network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Re Protocol reUSD (REUSD)
Type
token
Available networks
7
Native networks
Contract token
Route support
Not currently available
Re Protocol reUSD (REUSD) is available in network-specific native or token forms. Re Protocol reUSD belongs to the token category and must be verified through its network-specific native label or contract representation.
Re Protocol reUSD belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Ethereum, Solana, Arbitrum, Base, Ink, BNB Chain, Avalanche; network gas remains a separate native balance.
Ethereum (contract), Solana (contract), Arbitrum (contract), Base (contract), Ink (contract), BNB Chain (contract), Avalanche (contract)
Confirm the REUSD network, contract or native label, and receiving address before using a route. Do not identify REUSD solely by ticker; verify the asset and network representation. REUSD can use different contracts on different networks.
Sasquatch does not currently list a transaction route for Re Protocol reUSD. 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.
REUSD is contract-based on Ethereum, Solana, Arbitrum, Base, Ink, BNB Chain, Avalanche. 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 REUSD.
Ethereum, Solana, Arbitrum, Base, Ink, BNB Chain, Avalanche
Sasquatch does not currently list a transaction route for Re Protocol reUSD.
Confirm the REUSD network, contract or native label, and receiving address before using a route. Do not identify REUSD solely by ticker; verify the asset and network representation.