Supported Networks & Standards
Support Matrix (Latest: February 2026)

This page outlines the blockchain networks, token standards, and asset types currently supported by Hubz for access gating. It serves as a reference for determining whether a specific chain, token, or NFT can be used with Hubz.
Support applies across token-based, NFT-based, and custom asset gating where applicable.
Chains by Type
Hubz currently supports the following blockchain networks:
Type
Chain
Native Token
Decimals
TON
TON Network
TON
9
Solana
Solana Mainnet
SOL
9
EVM
Ethereum
ETH
18
EVM
Base
ETH
18
EVM
BNB Smart Chain
BNB
18
EVM
Avalanche C-Chain
AVAX
18
EVM
Polygon
POL
18
EVM
Fantom
FTM
18
EVM
Arbitrum
ETH
18
EVM
Optimism
ETH
18
EVM
ApeChain
APE
18
Token Standards by Chain Type
Hubz detects and verifies assets using the following standards and methods:
Chain Type
Standard
Category
Detection Method
EVM
ERC-20
Fungible Token
ERC-165 (0x36372b07) + balanceOf fallback
EVM
ERC-721
NFT
ERC-165 (0x80ac58cd)
EVM
ERC-1155*
Multi-Token
ERC-165 (0xd9b67a26)
Solana
SPL Token
Fungible Token
DAS API (fungibletoken, fungibleasset)
Solana
SPL NFT
NFT
DAS API (v1_nft, v2_nft, programmablenft)
Solana
Token-2022
Fungible (Extended)
SPL Token Program
TON
Jetton
Fungible Token
Toncenter API (jetton_masters)
TON
NFT Collection
NFT
Toncenter API (nft_collections)
* ERC-1155 support is limited to Token ID 1 only.
Custom Tokens & NFTs
In addition to commonly indexed assets, Hubz supports custom tokens and NFT collections on all supported chains. When using custom assets, you must:
Select the correct blockchain network
Provide the correct contract or collection address
If the asset is valid, Hubz will automatically detect and display it for confirmation.
Verification Compatibility
All supported chains and standards work with Hubz’s verification modes:
One-Time Verification
Ongoing Verification
Verification behaviour depends on the selected mode and applies consistently across all supported networks.
Notes & Limitations
Asset detection depends on correct network selection and contract details.
Incorrect contract addresses or network mismatches may prevent verification.
Support for additional chains and standards may be added over time.
Last updated