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