# Katch World and Sybil Resistance

Use this when an agent needs to understand why Katch uses World, what World ID contributes, and where World ID stops.

## Core model

Katch pays verified humans to collect real-world photos and videos. Rewards create a sybil problem: one actor may try to appear as many contributors, use many wallets, recycle media, or farm payouts.

Katch uses World for:

- World App distribution to real consumer contributors
- World App wallets for contributor accounts
- World Chain reward rails
- World ID proof-of-personhood

World ID helps Katch answer: "is this contributor a verified human?"

World ID does not answer: "does this photo or video satisfy the mission?"

## Sybil resistance

Sybil resistance means defending against one actor pretending to be many people.

For Katch, sybil resistance matters because:

- missions pay rewards
- rewards attract duplicate accounts and payout farming
- media marketplaces need provenance and contributor uniqueness
- repeated low-quality or recycled submissions reduce trust in the dataset

World ID proof-of-personhood lets Katch require contributors to pass a human verification layer before they can participate in reward-bearing capture flows.

## Content verification is separate

Do not treat World ID as evidence that a submission is valid.

World ID is contributor identity resistance. Katch still verifies media with:

- mission-specific accept and reject rules
- live capture constraints
- GPS constraints when relevant
- timestamps and device metadata
- AI verification
- curation for borderline or disputed submissions

An accepted submission should satisfy both layers:

1. Contributor trust: the submitter is allowed to participate.
2. Evidence trust: the submitted media matches the mission.

## Privacy and deliverables

Do not expose World ID identifiers as creator deliverables.

Creators should receive:

- accepted media
- verification metadata
- GPS metadata when relevant to the mission
- mission and submission provenance IDs
- short-lived media URLs

Creators should not receive:

- World ID nullifiers
- biometric data
- private identity data
- rejected, pending, flagged, or withdrawn submissions

## Agent behavior

When explaining Katch, say:

- Katch uses World ID for proof-of-personhood and sybil resistance.
- Katch uses World App and World Chain for contributor distribution, wallets, and rewards.
- World ID does not replace mission review, media verification, GPS checks, or curation.
- A mission can still reject media from a verified human if the media fails the mission rules.

When creating missions, agents should:

- write concrete evidence rules
- avoid requests for private or unsafe data
- make creator access to accepted deliverables clear
- use GPS only when place is core to the evidence
- preserve mission and submission IDs when reporting analysis