On this page
Kalshi liquidity rewards are incentives for qualifying resting orders in selected programs. A reward is separate from a contract payout and from the trading result of an order that fills. This guide explains the reference-price calculation with an original depth example, then separates provisional estimates from completed credits.
Sources checked November 9, 2026: Kalshi’s program guide and its rewards-location guide. The examples below are hypothetical, not live order books or earnings estimates.
Find the exact market’s rewards program
Kalshi’s rewards-location guide points to Menu → Rewards or the incentives page. Event totals can combine several market pools. Inspect the exact market’s badge for its own period, pool, Target Size and Discount Factor. Live estimates can change; Current month and Lifetime totals show paid credits. Account → Activity → Credits contains completed payments.
| Record | Question to answer |
|---|---|
| Event total | Does it combine more than one market? |
| Individual program | Which market, period and parameters apply? |
| Live estimate | At what time was this provisional value observed? |
| Paid credit | Which completed payment can I reconcile? |
How the reference price differs from the best bid
Kalshi’s program guide locates the Reference Price where cumulative bid depth first reaches one fifth of Target Size. Qualifying orders are weighted by size and distance; those at or above the reference get full weight, while lower prices use Discount Factor raised to tick distance. Both sides must reach Target Size for a snapshot to count.
In this fictional snapshot, Target Size is 1,000 contracts, so the reference-depth threshold is 200. Assume one-cent ticks, a Discount Factor of 0.8, and that the opposite side also has sufficient qualifying depth. The following bids are on one side only:
| Bid price | Contracts at level | Cumulative contracts | Distance below reference | Weight | Raw score |
|---|---|---|---|---|---|
| 52¢ | 50 | 50 | Above reference | 1 | 50 |
| 51¢ | 150 | 200 | 0 ticks | 1 | 150 |
| 50¢ | 300 | 500 | 1 tick | 0.8 | 240 |
| 49¢ | 500 | 1,000 | 2 ticks | 0.64 | 320 |
The reference is 51¢, not the best bid of 52¢: the first level contains only 50 contracts, while the second brings the running total to 200. The raw scores sum to 760. If one participant owns the entire 50¢ level and none of the other orders, that participant’s share of this side’s raw score is 240 /760 ≈31.58%.
That 31.58% is a side-specific share for one invented snapshot. It is not the participant’s final program share. We have not supplied the participant’s opposite-side orders, other snapshots or the complete scoring record. Putting this number directly into a final-reward calculation would silently assume information we do not have.
Notice that the 500 contracts at 49¢ produce a score of 320, while 300 contracts at 50¢ produce 240. Quantity and distance interact. Neither “closest order always earns most” nor “twice the quantity always earns twice the final reward” follows from the example.
What if the visible book changes?
Keep the same fictional Target Size, but change the 52¢ level from 50 to 250 contracts. The running total now crosses 200 at 52¢, so the reference moves to 52¢. A separate 100-contract order at 50¢ would now be two ticks below the reference: its raw score would be 100 ×0.8² =64, compared with 80 when the reference was 51¢. Its quantity and price did not change; the surrounding book did.
This comparison isolates one order’s raw score. Its normalized share would also depend on all qualifying orders. It does not calculate whether an actual order qualifies at a boundary or predict what happens after a fill.
Calculate a reward from an assumed final share
The program guide applies final score share to the pool and the non-excluded snapshot fraction, floors the result to cents, and applies a $1 minimum to each individual program. Use the liquidity rewards scenario calculator for assumed final shares.
For an independent example, assume a $250 pool, a 12% final share and 75% non-excluded snapshots. The result is $250 ×0.12 ×0.75 =$22.50. At a 6% share it becomes $11.25. These final-share assumptions are separate from the one-side depth exercise above.
For a minimum-payment example, suppose two separate programs each produce a calculated reward of $0.80. Neither reaches $1. Their combined $1.60 does not turn either individual program into a payable reward. The calculator treats each scenario as one program; it does not combine account history or verify eligibility.
Why Kalshi rewards can still show zero
The rewards-location guide distinguishes pending estimates from paid totals. A program can disappear from the active list before payment appears. A live blue or gray order indicator is guidance, not the final reward record; final scoring uses the whole program. A below-minimum result is another possible reason no credit arrives.
Before investigating a missing amount, save the exact market, program period, estimate and observation time. Then look for the completed credit matching that program. Do not compare a current event-wide total with an earlier individual-market estimate as if they were the same record.
Rewards do not establish trading profit
Imagine the $22.50 reward accompanies $30 of trading losses and $2 of fees for the same accounting period. The combined result is −$9.50. A positive incentive did not make that fictional activity profitable.
Keep trading gains or losses, fees and paid incentives in separate ledger columns, avoiding double-counted costs. Open positions need a separate valuation. Use the order-book guide, fee guide and portfolio guide to distinguish the records involved.
A program-review checklist
- Identify the exact market and incentive period.
- Record Target Size, Discount Factor and the pool separately.
- Distinguish a single snapshot’s score from a final program share.
- Keep provisional estimates and paid credits in separate records.
- Check eligibility and current governing terms at Kalshi’s notices.
- Compare paid rewards with the complete trading result.
For event proposals and designated status, see creating a Kalshi market versus market making. Those processes should not be inferred from a reward estimate. Alphascope’s research tools can support event research; they do not certify program eligibility or future earnings.