Skip to main content

What it does

Gated Pools takes a trust read and turns it into access. Instead of a pool, a launchpad, or any sensitive action being open to every address that shows up, it can require a wallet to have earned a certain standing first. The score stops being something you display and becomes something you enforce. The point is to raise the cost of abuse without resorting to KYC. An open pool is a magnet for bots, sybil wallets, and bad actors because there is nothing in the way. A gate made of earned reputation is cheap for a real participant to clear and expensive for an attacker to fake.

Why gate by reputation

KYC tells you who someone is in the legal sense, which is heavy, exclusionary, and beside the point for most onchain decisions. Leaving things fully open tells you nothing and invites the worst behavior. Reputation sits in between: permissionless, privacy-preserving, and earned through real onchain history rather than paperwork.

How it works

The shape of the gate fits the chain.
On Sui the gate is a non-transferable capability object (key, no store). A wallet that meets the required standing holds the capability, and your function requires it. Nobody can buy or pass the object along. The check is onchain.Two cap types exist:
  • TrustedAgentCap — mint at score 70+, valid 30 epochs, assert_standard_valid
  • TrustedAgentCapElite — mint at score 85+, assert_elite_valid
TrustGate’s own GatedPool is a demo: it records orders in a table if the cap is valid. It is not DeepBook and not the native order book. Use it as the reference consumer. Package IDs and a worked Move example: Gate by capability.

You set the bar

TrustGate gives you the primitive. You set the policy. The required standing, what the pool gates, and how strict to be are yours to decide. We provide the trust read and the gating mechanism. What counts as “trusted enough” is your call.
This is the non-invasive principle taken all the way to enforcement. Even here, TrustGate is supplying a check, not running your pool.

Who it is for

Protocols that want quality participants rather than volume for its own sake. A DEX gating large or sensitive trades. A launchpad keeping earliest access for wallets with real standing. A DAO restricting an action. An agent-only pool.

Build it

Sui: gate by capability

Require the capability object, with live package details.

Arc: attestations

EIP-712 attestations and a protocol-owned ladder.