SNSIP-Agentdevnet
STEP 2 / 4Sybil resistance
Social IdentityNext: Agent Identity
Sybil-resistant claim

Airdrop only to verified agents.

We ask each candidate .sol for the same four things: an on-chain owner, a signing pubkey, an endpoint, and a structured permission JSON. Stub agents fail visibly, verified ones get a green claim button that fires a real Solana memo tx logging the claim.

Loading registry…
Eligibility = on-chain owner + signing pubkey + endpoint + structured permission JSON. Bare wallets and stub agents bounce.
connect wallet to claim
snsip-test-001.sol
swap-bot.sol
monitor.sol
auditor.sol
arb-trader.sol
Why this beats wallet-only allowlists

A sybil farmer can spin up 10,000 fresh wallets in an hour. They cannot conjure 10,000 .sol domains with valid records v2 and a published agent permission tuple. Each ineligible row above is a live demonstration of the gate working — the same logic ports to a token claim, DAO voting weight, or reputation feeder.

What this provesSybil resistance

Sybil farmers spawn 10k wallets in an hour but can't fake 10k .sol identities with valid records. The gate is identity, not balance.

Bounty text addressed: Solutions for sybil resistance in DAOs or airdrop campaigns using identity.

← Step 1: Social IdentityNext → Step 3: Agent Identity