> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sleuthintel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# The Belt: Sleuth Intel's Pre-Acceptance Intake Queue

> Submit wallet tags and intel through The Belt. Learn about submission slots, the $10 activation fee, and Fix, Confirm, and Flag actions.

The Belt is Sleuth Intel's public intake queue — the layer every submission passes through before it's accepted into the knowledge tree. Nothing enters the platform silently. Every piece of intel lands on The Belt first, where the community can act on it before verifiers grade it.

## Activating Your Contributor Account

Before you submit anything, you pay a **one-time \$10 SLEUTH activation fee**. You pay it once. It never recurs.

<Info>
  The activation fee is a sybil barrier, not an access wall. It ties your contributor identity to real economic accountability, which protects the integrity of every submission on the platform.
</Info>

## Submitting Intel

To submit a piece of intel, open the submission form and fill in:

* **Niche** — the domain your intel belongs to (e.g. DeFi wallets, CEX accounts, macro narratives)
* **Tag type** — wallet, account, trader, narrative, or market
* **Evidence** — on-chain links, transaction hashes, screenshots, or structured reasoning that supports your claim
* **Summary** — a concise description of what the intel asserts

Strong submissions are specific, evidence-backed, and cover territory that isn't already in the knowledge tree.

### Submission Slots

You start with **3 open submission slots** — meaning you can have up to 3 submissions in-flight at any time. As you build a track record of accepted, high-grade intel, that number scales toward approximately 25.

<Tip>
  Don't burn all your slots on marginal submissions. Your slot count reflects your track record, so prioritise quality over volume, especially early on.
</Tip>

## How The Belt Works

Once you submit, your intel goes live on The Belt — publicly visible to anyone on the platform. From there, one of two lanes processes it:

<Steps>
  <Step title="Machine Lane (instant)">
    On-chain-verifiable intel — wallet tags, contract labels, transaction-linked claims — is resolved instantly using automated verification. No waiting, no verifier draw.
  </Step>

  <Step title="Judgment Lane (5-day window)">
    Intel that requires human assessment enters the judgment lane. Three randomly drawn licensed verifiers independently review the submission and return blind verdicts. The median grade decides.
  </Step>
</Steps>

## Belt Actions

While a submission sits on The Belt, any platform participant can take one of three actions. These actions are **first-come, first-served** — only one confirm slot and one flag slot exist per submission.

<CardGroup cols={1}>
  <Card title="Fix a Tag" icon="wrench">
    If you believe a submission contains wrong intel, submit your own corrected version as a fix. If your fix materially changes the final grade, you earn **50% of the original submitter's grade payout**. You don't need a slot to fix — but you do need to be right.
  </Card>

  <Card title="Confirm a Tag" icon="circle-check">
    Stake your reputation on a submission being correct. If the submission is upheld, you earn $5**. If it's rejected, you're **slashed $**50** — the same stake as a verifier who passes bad intel. You get **3 free wrong confirms per 30-day window** before slashing applies.
  </Card>

  <Card title="Flag a Tag" icon="flag">
    Raise a concern about a submission before it graduates. If your flag is upheld, you earn **\$5 per tag**. If the flag is rejected, it counts against your **3 free wrong flags per 30-day window**. A standing flag stops the submission from graduating to the knowledge tree.
  </Card>
</CardGroup>

<Warning>
  Confirming or flagging carelessly is expensive. The \$50 slash for a wrong confirm matches the penalty a licensed verifier faces for a bad pass. The free-wrong windows exist, but they're limited — use belt actions when you have genuine signal, not as noise.
</Warning>

## Tips for Getting Intel Accepted

<Tip>
  **Lead with on-chain evidence.** Verifiable transactions and addresses get through the machine lane instantly and leave no room for grade dispute.
</Tip>

<Tip>
  **Be specific about niche.** Submissions tagged to a precise domain (e.g. "Perps front-running wallet, Arbitrum") are easier for verifiers to assess and tend to grade higher than vague, broad claims.
</Tip>

<Tip>
  **Surface unique signal.** Intel that cross-references multiple on-chain and off-chain sources — and predates public knowledge — consistently earns higher grades. If it's already on a block explorer dashboard, it's lower value.
</Tip>