5. Set reward tiers
What you’ll do: Define which GitHub labels map to which USDC amounts, so labeling an issue sets its reward automatically.
A reward tier is just a (label, amount) pair stored on the repo. Label an issue with that label and TOSS reserves that amount. The dashboard ships three defaults — low, medium, high — and every part of that is editable.
The two ways to price a bounty
| Approach | How | When to use |
|---|---|---|
| Tier label | Pre-configure low/medium/high (or your own) with an amount, then just add the label to an issue. | Repeatable, consistent pricing across many issues. |
| Manual | Label rewarded + manual, then comment @trustless-oss <amount>. | One-off amounts that don’t fit a tier. |
This page is about tiers. Manual pricing is covered in Create a bounty.
Open the reward tiers panel
Open the repository
From the dashboard, click the repo. Reward tiers live on the repo page, below the escrow balance.
Review the three defaults
low, medium, high are listed with their current USDC amounts. New repos start with placeholder amounts you’ll want to set.
Edit a tier
Click Edit on a tier
Change the USDC amount, or change which GitHub label the tier maps to.
Save
The new amount applies to every bounty you label after saving. Bounties already locked on-chain keep their original amount.
Editing a tier changes it for future bounties only. Changing a reward never rewrites a bounty whose milestone is already locked on-chain — that would desync the database from the escrow contract, so it’s refused by design.
Add a tier from an existing GitHub label
If your repo already uses labels like bug, enhancement, or priority:high, you can map any of them to an amount — no need to invent new labels.
Click “Add tier”
The dashboard fetches your repo’s existing GitHub labels so you can pick one from the list.
Pick a label and set an amount
Choose an existing label, or type a new tier name. Enter the USDC amount.
Save
If the tier name is new, TOSS creates that label on GitHub for you, so it’s ready to apply to issues immediately.
Why fetch existing labels? So your TOSS tiers line up with the labels your project already triages by. A tier is only meaningful if the label exists on GitHub — mapping to a label you already use avoids duplicate, near-identical labels.
Delete a tier
Click Delete on a tier
You’ll be asked whether to also delete the matching label from GitHub.
Choose what to remove
- Remove the tier only — the GitHub label stays on your repo and on any issues already using it. It just no longer maps to an amount.
- Also delete the GitHub label — TOSS removes the label from the repo entirely.
Deleting the GitHub label is permanent. It removes the label from the repository and from every issue currently using it. The tier mapping is easy to recreate; the label and its history on issues are not. Leave “also delete GitHub label” unchecked unless you’re sure.
Done when
Your tiers list the labels and USDC amounts you want. Labeling an issue with a tier label now reserves that amount from the escrow balance automatically.
Next: Create a bounty · Stuck? Troubleshooting