Networks
Gatoll is multichain by design. The protocol currently supports Ethereum mainnet and BNB Smart Chain (BSC) mainnet, with each network running its own factory, pool implementations, verifier, and indexer.
Supported mainnets
Section titled “Supported mainnets”| Network | Chain ID | PoolFactory | Deployment |
|---|---|---|---|
| Ethereum mainnet | 1 | 0x15223285C92f9bD1aFAfAB7e9B65c36B038e175D | 2026-06-01 07:42:14 UTC |
| BNB Smart Chain mainnet | 56 | 0x8b86CCc413875e80771A4cb156Df0e06268da49b | 2026-06-01 06:36:30 UTC |
How multichain works
Section titled “How multichain works”The same contracts, PoolFactory and the three pool implementations, deploy to each supported network independently. There is no shared global state across chains; each network runs its own factory, pools, and indexer.
The verifier is chain-scoped: a separate signing key authorizes claims on each network, and a pool’s EIP-712 domain includes the chain ID, so a voucher signed for one network cannot be used on another. A single backend serves all supported chains, routing each request by chain ID.
A Loot lives on one chain
Section titled “A Loot lives on one chain”A Loot is created, funded, claimed, and reclaimed entirely on a single network. Its rewards are the native token or other tokens on that chain. Assets are not bridged between networks, and a Loot does not span chains. This keeps custody simple, settlement local, and the trust model unchanged regardless of how many networks the protocol supports.
Why Ethereum and BSC
Section titled “Why Ethereum and BSC”Ethereum mainnet provides the deepest liquidity, most established asset base, and the strongest default settlement venue for high-value campaigns. BNB Smart Chain offers low fees and broad reach, which fit Gatoll’s model of many lightweight campaigns. Together they cover both premium mainnet distribution and low-cost, high-frequency reward campaigns.
Expansion to additional EVM networks is tracked on the roadmap. Because every layer is already chain-scoped, adding a network is a deployment and configuration step rather than a protocol change.