What is Raidz?
Raidz is a market for digital reputation. It turns established social reach, content quality, and demonstrated reliability into discoverable creator work, while giving projects a structured way to buy original distribution with evidence and settlement controls.
It is not an engagement-exchange, paid-like network, automated shilling system, investment product, or promise that followers will convert. Campaigns pay for defined creator work or qualified outcomes—not manufactured metrics.
The problem
Creator work in Web3 is usually fragmented across private messages, spreadsheets, unverifiable screenshots, informal pricing, manual payments, and reputation that does not travel. Projects struggle to compare creators or prove delivery. Creators struggle to turn their actual capabilities and track record into repeatable demand.
Raidz joins five systems around one workflow:
- Identity — consented linking of X, Telegram, and an EVM wallet.
- Reputation — an explainable Raidz Score plus verified campaign history.
- Marketplace — open missions, direct creator services, and later performance work.
- Proof — multi-source verification with explicit accept, reject, and review outcomes.
- Settlement — project-funded escrow with immediate and retention releases.
The three markets
Raidz Missions
Projects publish fixed-scope work orders called Signals. A Signal defines the channel, deliverable, reward, minimum score, positions, deadline, policy, and proof requirements. Eligible creators claim a position and submit a content hash or canonical evidence reference.
Rent a Raidz
Creators publish fixed-price, fixed-output services such as original posts, research threads, product testing, Telegram features, video, AMAs, Spaces, memes, and community support. Projects select an individual creator based on fit, terms, price, and verified history.
Performance market
A later market attributes qualified outcomes such as registrations, activations, wallet connections, or defined onchain events. It depends on explicit measurement consent, deterministic deduplication, anti-fraud controls, and enough historical evidence to avoid rewarding vanity metrics.
Participants
| Participant | Primary responsibilities |
|---|---|
| Creator / KOL | Own linked identities; maintain profile; accept clear work; disclose compensation; submit original evidence; preserve deliverables through retention. |
| Project | Verify ownership; write truthful briefs; fund work; avoid prohibited metric incentives or financial claims; review outcomes. |
| Agency | Manage project campaigns within delegated authority; cannot bypass project verification or policy rules. |
| Policy engine | Evaluate channel, category, jurisdiction, compensation, and campaign copy against versioned rules. |
| Verifiers | Independently evaluate the same signed evidence payload; a 2-of-3 authorized quorum is required in the prototype. |
| Operator | Handle incidents, policy exceptions, manual review, configuration, and recovery without silently changing economic outcomes. |
| Escrow contracts | Reserve creator funds, enforce claim limits, consume signed attestations, release payments, and refund unused balances. |
Product loop
Connect
The user explicitly links each identity. Wallet linkage uses a one-time, domain-bound message and does not grant an approval or send a transaction. Social identifiers are pseudonymized in storage.
Score
Raidz calculates a versioned 0–1000 score from eleven normalized components. Early scores depend mostly on external account evidence; verified Raidz performance earns more weight as completed campaigns accumulate.
Raid
Creators claim eligible Signals or accept direct bookings. Projects move a draft through policy review and funding before it can become live.
Verify
The system evaluates ownership, timing, content integrity, required disclosures, campaign rules, and fraud indicators. Ambiguous evidence goes to review rather than settlement.
Earn
The prototype economics reserve 92% of gross campaign funding for creators after an 8% marketplace fee. Accepted creator rewards release 70% immediately and retain 30% until a follow-up verification window ends.
Rank
Completed work, conversion evidence, reliability, ratings, and verification history influence future reputation. Token holdings do not purchase reputation.
Design principles
- Work and proof come before token activity.
- Compensation buys a deliverable, never artificial engagement.
- Offchain data stays offchain unless a minimal hash or settlement fact must be anchored.
- Automated results must be explainable and versioned.
- Ambiguity fails closed or enters review.
- Public status distinguishes demonstrations from funded activity.
- Commercial outputs are pay-per-use; Raidz has no subscription or credit-pack model.

ATTENTION, WITH PROOF.