How it works

The whole thing, plainly.

Raidflag is a board and an escrow contract. The board shows raids and proofs. The contract holds the money and decides where it can go.

The content rule

Raidflag pays for content people make. Never for likes, follows, retweets, reposts, replies, comments, views, upvotes or any other bought engagement. No bots, no spam in other people's groups, nothing illegal, nothing that defaces or damages anything.

How we apply it:

  • Every raid's title, task and proof rules are checked when it's written. Asking for engagement is refused before any money moves.
  • The community confirms the raid pays for original content only.
  • Raids that break the rule anyway are taken off the board by the arbiter. Money already locked still settles by the contract's rules.
  • Proofs that are reposts of someone else's work, bought engagement, or don't match the task can be disputed and rejected.

New missions: X + live or AI

Every new mission requires an original public post on X with the participant’s raid code, plus the media file. The funding community chooses live, AI or both. Existing raids retain the brief they were funded with.

  • Live: record through Raidflag within the selected location radius, download the video and publish it on X before submitting the file and post link.
  • AI: use the real background reference supplied by the funding community. Keep the location recognizable and explicitly disclose AI use on X. Upload the finished image or video; no physical presence is claimed.
  • Review: check the X post is public, belongs to the participant, includes the code and matches the uploaded file. For AI, compare it against the reference and check the disclosure. These are manual checks, not automated X verification.

The current escrow does not inspect X posts or verify physical presence. It still permits finalization after 48 hours without a dispute, even without explicit approval. Communities must review and dispute invalid submissions within that window. Post availability after payment is not guaranteed.

Step by step

1. A community starts a raid

It names the coin, writes the task, picks the kinds of content, says what counts as proof, and sets the reward per raider, how many raiders get paid (up to 100), the deadline (up to 60 days) and how long a raider has to deliver after taking a slot. Then it locks (reward + 2% fee) × slots in the escrow.

2. Raiders take slots

One slot per wallet per raid. The creator can't take their own raid. A raider who doesn't deliver within their time (or by the deadline) loses the slot, and it opens again for someone else.

3. The raider delivers the proof

For new missions: the X post first, the uploaded media second and the real background reference third for AI entries, plus a short note. The proof's hash is written on-chain, so it can't be swapped later, and the proof shows on the raid page.

4. Review: 48 hours

  • Approve: the raider is paid immediately.
  • Dispute: the proof goes to the arbiter.
  • Silence: after 48 hours anyone can finalize, and the raider is paid. A community can't stall forever.

5. Disputes

Each raid keeps the arbiter wallet it was funded with. The arbiter compares the proof with the task and pays the raider or rejects the proof; a rejected slot opens again (or goes back to the community after the deadline). If the arbiter doesn't decide within 30 days, the slot goes back to the community. The arbiter is a different wallet from the contract owner and from the fee wallet.

6. Refunds

After the deadline, every slot nobody holds goes back to the community with its fee. Anyone can trigger it and our keeper runs it every day. A community can also stop a raid early: free slots come back right away and raiders already working keep their slot.

Money

  • Reward: 5 to 1,000 USDG per raider; at most 10,000 USDG per raid. These caps are written in the contract.
  • Fee: 2% on top of each paid reward, only when a raider is paid. Raiders keep 100% of the reward. The contract can never charge more than 3%.
  • Gas: a fraction of a cent on Robinhood Chain, paid by whoever sends the transaction.
  • If a transfer fails (for example the stablecoin issuer froze a wallet) the amount waits in the escrow and can be withdrawn later from the profile page.

Who can do what

  • Community: start, stop, approve, dispute.
  • Raider: take a slot, deliver, give the slot back.
  • Arbiter: decide disputes; take rule-breaking raids off the board.
  • Owner: pause new raids, rotate the arbiter or fee wallet for future raids, lower limits. It can't touch funded raids.
  • Anyone: finalize after 48 h, release lapsed slots, refund after the deadline.

Testnet

Raidflag runs on Robinhood Chain testnet for now, with tUSDG, a test token worth nothing. Connect a wallet (or create a test wallet in your browser) and use the faucet button to get test ETH and 1,000 tUSDG.

Escrow contract: … · Test token: …