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