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