Gates

A Gate is a requirement for participating in a Loot. A creator attaches Gates to decide who qualifies; passing the Gates is what makes a participant valid and eligible to receive a voucher and claim. Gates are how rewards reach the intended audience instead of anyone with a script.

What Gates are for

Gates turn a Loot from an open faucet into a targeted campaign. A creator can require participants to follow them, belong to a group, or appear on an allowlist, aligning the reward with a real action or relationship. The point is positive, not defensive: a Gate defines who the campaign is for, and passing it is the participant’s proof that they belong.

The Gate framework

Gatoll models eligibility as a small, composable system:

• Rules. A Loot or group carries a set of Gate rules, each a typed condition with its own parameters. Multiple rules combine; a participant must satisfy every enabled rule.
• Checks. A participant’s status against a rule is recorded as a check: requested, passed, or rejected. Checks can attach to a user or directly to a wallet address.
• Slots. A passed check reserves a seat; the system tracks consumption so a participant cannot turn one qualification into many claims.
• Modes. A rule is either persistent (the check is stored once it passes) or live (re-evaluated in real time, so revoking the underlying condition revokes eligibility immediately).

Available Gates

Gates available today include:

• Allowlist — a manual allowlist with three modes: open access, request-to-join, and invite-only. Custom-style allocations can be attached here.
• X follow — the participant follows a target X account and attests it; the system records the qualifying profile snapshot.
• Platform follow — the participant follows a target creator inside Gatoll; this is evaluated live, so unfollowing revokes eligibility.

All Gates sit on top of a one wallet, one claim baseline and rate limiting, so a single qualification yields a single claim.

On the roadmap

Further Gate types are planned but not yet available: human verification, on-chain holdings (ERC-20 / ERC-721 ownership), additional X actions (repost / like / reply), quests, and webhook-based attestation. They will fit into the same rules-and-checks framework as they ship. See the roadmap.

Because Gates live off-chain in the verifier while settlement stays on-chain, eligibility logic can evolve quickly without touching custody. See the architecture.