VBTD-104
Protocol launch bounty
Base launchProof: Researcher source links + remediation memo
5 proof fieldsHigh priorityCapped reward pool
REVIEWTighten proof
Crypto protocol bounty market · audit-core separate
Bounty trust desk for protocol campaigns.Protocol bounty market + evidence trust desk.
Private queue for protocol bounties: proof rules, decision labels, and one trust packet before launch.
Reviewable proof onlyNo token endorsementPrivate packet
Mobile desk feed
Bounty trust queue
REVIEW · Protocol launch bounty · proof rules incomplete
ALLOW · Creator evidence sprint · public links + disclosure
BLOCK · Wallet interaction quest · unsafe signing request
Packet digest
Proof rules, owner, escalation path, and ALLOW / REVIEW / BLOCK decision in one private memo.
Live queue
3 campaign rows
Proof packet
ALLOW / REVIEW / BLOCK
Audit boundary
No token endorsement
Protocol bounty market
Evidence rows before launch
Evidence first
VBTD-097
Creator evidence sprint
X / DiscordProof: Public post link + disclosure tag
4 proof fieldsMedium priorityFixed creator task
ALLOWPublish with rules
VBTD-088
Wallet interaction quest
Quest boardProof: Unsafe signing request
Blocked actionEscalationBlocked task
BLOCKRemove action
What gets reviewed
Campaign mechanics create trust debt when nobody owns the proof.
The desk makes the task sheet reviewable before launch: evidence requirements, reviewer ownership, blocked actions, and escalation paths are visible in the same packet.
Fake-proof risk
Flags fake screenshots, recycled proof, bot farms, and unverifiable attestations before launch.
Unsafe task wording
Catches hidden promotion, certainty claims, wallet-risk actions, credential asks, and buyer-behavior prompts.
Reward-abuse / farming risk
Reviews spam, sybil loops, duplicate submissions, low-quality engagement, and moderation overload.
Proof flow
Defines required evidence, storage location, reviewer ownership, and visible uncertainty.
Operator rules
Converts tasks into ALLOW / REVIEW / BLOCK rules moderators can enforce.
Audit-core separation
Keeps campaign review private and separate from scans, reports, Trust Index signals, and serious audit findings.
Proof flow
From rough task draft to desk packet.
The flow is intentionally private. Campaign review helps founders and operators clean the task design before a bounty, quest, launch push, or creator brief goes live.
- 01
Intake
Founder submits target links, platform, task draft, reward mechanics, proof rules, and moderation constraints.
- 02
Policy review
VegaSec checks wording against blocked promotion, proof, safety, and abuse patterns.
- 03
Desk packet
Private task sheet with risk notes, allowed proof, blocked actions, labels, and next-step questions.
- 04
Operator triage
Operators approve clean submissions, request evidence, or block unsafe and unverifiable tasks.
Operator rules
Allowed tasks are reviewable. Blocked tasks create trust risk.
- Every task needs an allowed proof shape, a blocked-action list, an owner, and an escalation rule.
- No buy instructions, hidden shilling, fake audit claims, dangerous stunts, seed phrases, or wallet credential collection.
- Campaign review results stay private by default and do not create public reports for bounty requests.
- Bounty work never upgrades, suppresses, or rewrites serious audit findings, report limitations, or Trust Index signals.
Private intake
Request review before the task sheet goes live.
Send the campaign target, platform, draft task wording, proof rules, and moderation constraints. The campaign lane stays private and does not create a public report.