Bounty Collection

Bounties reward useful oracle work.

The goal is not to pay users for noise. The goal is to pay for accepted work that improves source quality, updates frozen sources, or catches bad evidence.

Work That Can Earn Bounties

Depending on the market version, bounty-eligible work may include:

• proposing a valid public source;
• supporting a source that survives challenge;
• submitting a correct opening print;
• submitting a correct live update;
• challenging an invalid source;
• challenging a bad update.

Work That Should Not Earn Bounties

Users should not be paid merely to repeat that a source is unchanged.

If a frozen source has not changed, its last accepted state carries forward.

Challenge Risk

Oracle submissions can be challenged.

If a user’s claim is wrong, stale, private, duplicated, or mapped to the wrong product bucket, the user can lose a bond or stake according to the active rules.

Collection Flow

A typical bounty flow is:

1. submit eligible work;
2. wait through the challenge window;
3. survive review or resolution;
4. finalize the accepted action;
5. collect the bounty if the market version provides one.

Exact payout timing and amounts should come from the active product page or CLI output.

Settlement Boundary

Bounties belong to oracle work. They are separate from option payouts.

The oracle finalizes accepted source work and computes the market movement. The trading contract uses that movement to settle contract holders.