Skip to main content

​
Rewards and treasury

PressChain economics include reward claims, bounty funding and treasury controls, but applications should not treat the treasury as a generic hot wallet. The V3 policy requires value movement to remain bounded by explicit rules, role and bond validation, treasury floors, budget limits and settlement audit events.

​
Reward claims

reward.claim is classified as a micro-fee action. It requires an active bond and is limited to one claim per cycle under the current policy. A reward UI should display the claimable cycle and current eligibility before asking for authorization.
The authoritative settlement path still checks state at execution time.

​
Treasury floors

A treasury floor prevents automated activity from draining funds below a protected reserve. Applications that create or approve automated bounties should expect a proposal to be rejected when treasury policy would be violated. Do not hide that as a generic server error. “Treasury policy prevented funding” is operationally actionable.

​
Bounty budget caps

Automatic bounty creation is subject to budget caps and maximum active bounty limits. The private bounty engine is intended to evaluate those policies deterministically. A public client should consume the resulting proposal or settlement state, not reproduce private anti-abuse logic in JavaScript.

​
Settlement revalidation

Role and bond eligibility should be checked again at settlement, not only when a bounty is claimed. A long-running bounty can outlive the state that originally made the claimant eligible. This is a general protocol lesson: eligibility at intent time and eligibility at settlement time are two different facts.

​
Audit events

Every meaningful treasury or settlement transition should produce an immutable audit record. Projection systems should retain transaction hash, block, actor, action and amount. For financial views, use integer token base units internally and format only at the presentation boundary.

​
Mainnet policy gate

Final treasury allocation, reward distribution and burn routing are mainnet policy items. Testnet behavior is useful for integration, but it does not finalize mainnet economics by implication.