Fund channel challenges with viewer points

Turn on Bounties and Points

Both switches must be on for Bounties navigation and work.

The feature cards save those switch changes immediately.

A channel owner or permitted moderator creates and settles bounties. A participant needs a Twitch chat identity and enough available BlokeBot points to pledge.

1. Select the channel.
2. Open Channel setup.
3. Turn on Points and Bounties under Chat tools.
4. Open Bounties.
5. If you need the dashboard summary, use the Page help (?) button.

• Open a clear challenge.
• Let viewers reserve points toward it.
• Settle each outcome.
• Show who contributed.

Create a proposal and open funding

The bounty lifecycle ends with one terminal outcome. Reject is a distinct audited action. It stores a Cancelled outcome.

Proposed is a draft and cannot receive pledges.

1. Enter the public title and description.
2. Enter the funding target.
3. Enter the UTC expiry.
4. Enter an optional fixed pool for completion bonuses.
5. Select Public or Private visibility.
6. Select what a Failed outcome does with pledges.
7. Select Equal or Proportional distribution for completion bonuses.
8. Put staff-only context in Private moderator note.
9. Select Create proposed bounty.
10. Review the selected channel and values.
11. Add a Private audit reason.
12. Select Open funding.

• Non-terminal bounty state: Proposed.
• Non-terminal bounty state: Funding.
• Non-terminal bounty state: Accepted.
• Terminal bounty outcome: Completed.
• Terminal bounty outcome: Failed.
• Terminal bounty outcome: Expired.
• Terminal bounty outcome: Cancelled.

Pledge and follow progress

• The public board is /bounties/{channel}. Replace the value in braces with the channel login.
• Public bounties show the title and the description.
• Public bounties show the state and the funding total.
• Public bounties show the target and the deadline.
• Public bounties show the bonus and terminal history.
• Public bounties show recorded contributors.
• A signed-in participant enters Pledge points on the board, or uses chat. BlokeBot reserves the accepted amount from that channel's available point balance.
• BlokeBot caps a pledge request above the required amount to the target remainder. It does not overfund the bounty. A repeated delivery records the pledge only once.
• Owners and moderators can select Accept while the state is Funding. They can do this before or after contributions reach the target. When contributions reach the target, BlokeBot does not accept the challenge automatically.

!bounties
!bounty <bounty-id>
!bountypledge <bounty-id> <points>

Moderate deadlines and outcomes

If another moderator changed the bounty, reload before you act. BlokeBot rejects a stale transition and keeps the newer state.

• You can extend Funding and Accepted bounties before they become terminal. Either state can expire. Check the UTC expiry before you extend it.
• An Accepted bounty can move to Completed.
• An Accepted bounty can move to Failed.
• An Accepted bounty can move to Cancelled.
• Every bounty action records the authenticated actor.
• Every bounty action records the time.
• Every bounty action records the action.
• Every bounty action records the private audit reason.
• Completed consumes all reserved pledges. BlokeBot splits its fixed bonus pool across contributor logins with the selected Equal or Proportional rule. It cannot grant twice.
• Reject refunds every reserved pledge.
• Cancel refunds every reserved pledge.
• Expire refunds every reserved pledge.
• Fail applies the bounty's chosen Refund pledges or Spend pledges policy exactly once.

Identity and privacy

• A Public bounty exposes each recorded normalized Twitch login and its total pledge amount. A Private bounty publishes no bounty data.
• BlokeBot groups contributors by that host-scoped recorded login.
• Point debits use that host-scoped recorded login.
• Point refunds use that host-scoped recorded login.
• Point bonuses use that host-scoped recorded login.
• A later Twitch rename does not move the balance or combine historical logins.
• The public board and chat summary never contain private moderator notes and audit reasons.
• The public board and chat summary never contain raw provider data and internal identifiers.

Recover without double settlement

• If Points is off, turn it on in Channel setup. Saved bounty work remains unchanged while the dependency is unavailable.
• If BlokeBot rejects a pledge, correct the visible cause of rejection.
• Possible pledge rejection cause: the balance.
• Possible pledge rejection cause: the state.
• Possible pledge rejection cause: the expiry.
• Possible pledge rejection cause: validation.
• Submit once.
• If a pledge or transition is visible, reload.
• Do not repeat it.
• If Bounties is off, BlokeBot hides navigation.
• If Bounties is off, BlokeBot hides commands.
• If Bounties is off, BlokeBot hides public data.
• If Bounties is off, BlokeBot stops pledges.
• If Bounties is off, BlokeBot stops moderation.
• If Bounties is off, BlokeBot stops expiry work.
• If Bounties is off, BlokeBot stops ledger changes.
• If Bounties is off, BlokeBot stops emitted events.
• If Bounties is off, BlokeBot keeps saved bounties.
• If Bounties is off, BlokeBot keeps saved pledges.
• If Bounties is off, BlokeBot keeps saved history.
• Re-enable Bounties and Points to continue from retained current state.
• BlokeBot does not replay suppressed commands from the disabled period.
• BlokeBot does not replay suppressed expiries from the disabled period.
• BlokeBot does not replay suppressed events from the disabled period.
• BlokeBot does not replay suppressed other work from the disabled period.