Spend received income
The proposed buyback budget is 90% of staking income received by the treasury. A pending reward or queued payout is not spendable cash. Funds reserved for another obligation should not be reported as available for purchases.
Buy first, burn second
- Reconcile received income and the team allocation.
- Obtain a supported CSTR swap quote within approved spending and slippage limits.
- Execute the purchase and verify the actual tokens received.
- Submit and confirm the token burn.
- Publish linked purchase and burn receipts.
A purchased token still exists until it is burned. Holding it in a treasury wallet or transferring it to an address labeled “burn” is not enough to count a verified supply reduction. The burn record should be checked against the actual mint and token amount.
Timing and execution
No keeper, fixed execution schedule, or minimum buyback size is active or guaranteed. Execution limits need to account for route availability, pool depth, network fees, and the price impact of the purchase. An unavailable or unacceptable quote should not be treated as a completed buyback.
What a burn does not promise
Burning reduces the amount of existing tokens, but does not establish a price floor or a redemption right. Selling pressure can exceed buyback demand. A pool may become illiquid even when some supply has been retired.
The website's user-initiated Jupiter swaps are separate from treasury automation. A working swap interface is not evidence that revenue collection or a buyback process is operating.
See public accounting for how purchases, inventory, and confirmed burns should be reported separately.