Introduction

The growth problem

Web3 projects live or die by their early communities, but the standard acquisition tools are blunt. Airdrops are farmed before real users arrive. “Engage to earn” campaigns often reward screenshots and promises that never settle on-chain. And too many campaigns ask newcomers to install an extension and safeguard a seed phrase before they can receive anything, creating the largest drop-off point in onboarding.

The result is familiar: budgets evaporate, dashboards fill with bots, and the users a project actually wanted never convert.

Three things a reward campaign actually needs

1. Verifiable payout. Participants should be able to see that the reward exists and that the rules are enforced by code, not by a promise.
2. Meaningful participation. The creator should decide who qualifies, whether that means followers, group members, or an allowlist, so the reward reaches the intended audience instead of anyone with a script.
3. Zero-friction claiming. A participant arriving from a social link should be able to claim in seconds, on a phone, without installing anything.

What Gatoll is

Gatoll packages these requirements into one primitive: the Loot. A creator escrows rewards in a smart contract, attaches Gates that define who can participate, and shares a single link. A participant opens the link, passes the Gates, and claims on-chain through a built-in wallet.

A Loot is the whole campaign in one object: the reward, the rules, and the page where the community gathers. Creators get a verifiable, gated distribution channel; participants get a real reward with minimal friction; and every value-moving step is auditable on-chain.

The rest of this paper explains how the protocol delivers those guarantees: the Loot primitive and its lifecycle, the architecture that separates trustless settlement from flexible eligibility, and the contracts, claims, and Gates that make the system work.