Researchers who reported issues to us. The bug-bounty pool is 3% of revenue; payouts flow once revenue exists.
Program status: designed, not yet activated. The policy, payout tiers, response SLAs and safe-harbor terms are published in full at /docs/bounty/. The funding is pending: the revenue source has no live payment keys yet, so there is no revenue, no 3% allocation and no pool balance. Reports are still accepted and still fixed — only the payout is pending. Full detail and the activation checklist: /docs/bounty/.
| Severity | Description | Payout (USD) |
|---|---|---|
| Critical | Remote code execution, persistent auth bypass, full account takeover | $500 |
| High | Significant data exposure, privilege escalation to Pro without payment | $200 |
| Medium | Cross-origin data leakage, denial-of-service affecting other users | $75 |
| Low | Information disclosure that doesn't compromise other users | $25 |
| Info | A non-exploitable finding that still helps us improve | $10 |
— Current pool balance: $0 (no revenue yet; pool activates when revenue exists).
The pool accrues at 3% of net revenue until spent. Net revenue is gross collected minus refunds, chargebacks, taxes and payment-processor fees; 3% of that accrues at the close of the following month and unspent balance carries forward. The exact calculation, the ledger format, and the allocation rules are specified in /docs/bounty/ §4.
The ledger will live in our xkg-payments repo at state/bounty-pool/ledger.jsonl and we publish the total here monthly once the revenue pipeline is live. The critic-agent (configurable daily review at 07:55) generates internal "researcher" findings that go into the same pool accounting for transparency.