RaidzATTENTION, WITH PROOF.
Open app

Creator guide

This guide describes the intended creator journey and clearly marks the current pre-launch boundary.

1. Open the application

Use app.raidz.fun or a link from the official Telegram bot. Confirm the exact hostname before connecting a wallet. The regular Telegram bot only provides information, notifications, and HTTPS deep links; it is not a wallet or a crypto Mini App.

2. Create and connect a profile

The application can create a server-side session and an initial creator profile. You can edit display name, bio, locale, jurisdiction, languages, regions, narratives, availability, and public-profile visibility.

Connections are independent and revocable:

  • Wallet: sign a five-minute, one-time ownership message for Robinhood Chain 4663. The message explicitly says it does not authorize a transaction or token approval.
  • X: authorize read-only OAuth scopes used for identity and public profile evidence. The implementation requests users.read, tweet.read, and offline.access.
  • Telegram: approve Telegram Login data signed by the Raidz bot. The server rejects payloads outside a five-minute freshness window.

Read the purpose and data notice before authorizing. Disconnecting a provider removes or revokes its active link; settlement records may need longer retention for legal and operational reasons.

3. Receive and inspect a score

The production journey is intended to scan consented account evidence and produce a score with model version, component values, timestamps, confidence, and explanations. Today the score model and preview endpoint exist, but automated provider ingestion and a completed public-user scan are not claimed.

Do not treat a score as guaranteed reach or earnings. See Raidz Score.

4. Discover Signals

Radar will eventually show only campaigns that passed policy review and confirmed funding. Check:

  • project identity and campaign state;
  • exact deliverable and disclosure;
  • reward asset and amount;
  • score, jurisdiction, narrative, language, and channel eligibility;
  • deadline and retention period;
  • evidence requirements and rejection conditions.

The current mission cards are labeled demo data and are not funded opportunities. The API returns no live missions.

5. Claim and create

In the contract prototype, one wallet can claim one position per campaign while the deadline, creator limit, and remaining budget allow it. The creator then submits a non-zero deliverable hash.

Only accept work you can complete truthfully. Compensation should be disclosed where required. A campaign must never ask you to produce fake metrics, coordinated buys, guaranteed-return claims, or undisclosed market manipulation.

6. Verification and settlement

A verifier quorum evaluates the submission against its campaign rules. Accepted work is designed to release 70% of the fixed reward and retain 30% until the retention window ends. Rejected or ambiguous work should include a reason; ambiguous evidence enters review in the target model.

No live escrow or funded reward pool exists yet. Never sign a token approval or transaction based on a demo mission or support message.

7. Build reputation

Verified delivery, reliability, qualified outcomes, ratings, and preserved content progressively influence Raidz Score. Your wallet balance does not. Shareable cards should always state their score version and evidence freshness.

Safety checklist

  • Use only links from raidz.fun, app.raidz.fun, @Raidz_web3, or @Raidz_fun after checking the exact account.
  • A normal profile link requires a message signature, not a token approval.
  • No $RAIDZ contract address or purchase route is official today.
  • Never provide a seed phrase, private key, recovery code, or bot token.
  • Capture the campaign terms and proof rules before starting work.
  • Report conflicting states or suspicious requests through an unaffected official channel.