What WOULD represents
would (WOULD) is available in network-specific native or token forms. would belongs to the token category and must be verified through its network-specific native label or contract representation.
would (WOULD)
Review WOULD network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
would (WOULD)
Type
token
Available networks
2
Native networks
Contract token
Route support
Not currently available
What you need to know
WOULD contract-token identity
would belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Solana, Hyperliquid L1; network gas remains a separate native balance.
WOULD network-by-network inventory
Solana (contract), Hyperliquid L1 (contract)
Receiving WOULD without a network mismatch
Confirm the WOULD network, contract or native label, and receiving address before using a route. Do not identify WOULD solely by ticker; verify the asset and network representation. WOULD can use different contracts on different networks.
WOULD route-support boundary
Sasquatch does not currently list a transaction route for would. Asset metadata is not proof of a live provider route.
WOULD privacy and wallet linking
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
Related routes
would (WOULD) FAQs
Which contracts identify WOULD?
WOULD is contract-based on Solana, Hyperliquid L1. Use the exact route representation rather than the ticker alone.
Does WOULD have a native gas balance?
No native origin is recorded in this registry. Network gas is paid with each chain's native asset, not automatically with WOULD.
Which receiving networks are recorded for WOULD?
Solana, Hyperliquid L1
Can I use a live WOULD route now?
Sasquatch does not currently list a transaction route for would.
What is the safest WOULD receiving check?
Confirm the WOULD network, contract or native label, and receiving address before using a route. Do not identify WOULD solely by ticker; verify the asset and network representation.