When a Dollar Budget Is Paid in a Volatile Token

A budget in dollars, a payout in ARB

On October 9, 2026, Arbitrum’s Operations Company (OpCo) published its third-quarter review of the Rewarding Active Delegates program, or RAD. This is a retrospective explanation of that decision, not a newly announced change. OpCo said the per-proposal category budgets would remain unchanged for Q4 2026, even though ARB had risen in price during the preceding weeks. Its stated reference was the three-month average ARB price, used to inform the review rather than to make the review follow only the recent price increase.

The review separates two ideas that are easy to conflate. RAD budgets are denominated in USD: the program expresses a category budget as a dollar amount. Rewards are settled in ARB: OpCo says dollar budgets are converted to ARB at payout. The category budget is therefore not a fixed number of ARB. At a lower token price, the same dollar amount corresponds to more ARB; at a higher price, it corresponds to fewer.

Consider a hypothetical $5,000 budget. At a hypothetical price of $0.10 per ARB, that amount corresponds to 50,000 ARB. At $0.20 per ARB, it corresponds to 25,000 ARB. These arithmetic examples assume full distribution and ignore fees, execution costs and any other adjustments. The prices are illustrative only: they are not current quotations, forecasts or recorded RAD transactions. The calculation shows how denomination and settlement interact; it does not establish the amount any delegate will receive.

Four choices behind a token payout

To understand a token-denominated payment, keep four accounting choices separate. Denomination is the unit used to state the obligation or budget, here USD. Settlement token is what is actually transferred, here ARB. The valuation date or time determines which token price translates one unit into the other. The averaging window is a period of observations used in a review or policy decision, here the three-month average cited by OpCo.

The averaging window is not the payout conversion rule. OpCo’s October post says USD budgets are converted to ARB at payout, and says the three-month average is a reference point for the quarterly review. It does not identify the exact pricing source or oracle, the time at which a payout price is fixed, the execution method, or slippage. Without program documentation establishing those details, readers should not assume that the three-month average determines an individual payout. Nor can this review alone tell a recipient the ARB amount they will receive.

A USD budget can make the program’s stated allocation easier to compare in dollar terms across changing token prices. It does not guarantee purchasing power at the time a recipient later uses or sells ARB. The value realized can differ with market price, timing, transaction costs and execution. A dollar label can keep the budget’s accounting unit steady while the quantity transferred and its later value vary.

What the Q4 table says

OpCo listed these per-proposal category budget and payout-cap pairs for Q4: on-chain constitutional quorum, $10,000 and $550; on-chain non-constitutional quorum, $5,000 and $400; off-chain decision-making, $5,000 and $400; off-chain election, $5,000 and $400; and a nonbinding off-chain temperature check, $3,000 and $250. These are category figures from the review, not a sum of all Q4 spending and not a report of actual payouts.

The table’s budget and payout cap are separate entries. The post supplies the amounts but does not explain in detail how eligibility is assessed or how a cap applies to an individual delegate in each case. It says the participation thresholds and rationale requirements introduced earlier remain unchanged. That statement does not, on its own, establish that every participant qualifies for a listed cap, that a category budget will be fully spent, or that one person will receive the category budget. The October post does not document actual Q4 disbursements.

So, read a category budget as a ceiling or planning amount associated with a type of proposal only to the extent the program’s rules define it that way; do not read it as a guaranteed payment. Likewise, the listed cap is not evidence of an earned reward without satisfying applicable rules. This review is useful for the announced budget structure, but it is not a complete payment manual.

The prior quarter provides context

The July 1, 2026 review described a preceding reduction in the per-proposal budgets, effective for proposals starting in July. It said proposals that began in June kept the old budgets even if they ended in July. That chronology matters: the July changes applied by proposal start date, while the October review said the resulting Q4 category budgets would remain unchanged.

In the July post, OpCo presented historical ARB spend estimates and comparisons with prices at that time. Those are OpCo’s reported estimates, not independently audited results and not present-day market data. This article does not use those historical price comparisons to claim a current token value, a verified treasury saving or a measured program outcome. The October decision itself says that, despite ARB’s recent rise, most of the rise had occurred in the last month and the three-month average had not caught up. That is OpCo’s explanation for its review approach, not independent evidence that the approach improved outcomes.

What the decision does not prove

OpCo’s stated rationale connects dollar-denominated rewards with predictability in dollar terms and says future reviews can adjust budgets if ARB moves materially. This describes the intended accounting and treasury-management rationale. The two quarterly review posts do not establish that the policy increased delegate participation, improved governance quality, stabilized the token price, or made treasury spending sustainable. They also do not establish actual Q4 payouts or how recipients ultimately valued the ARB they received.

A commenter responding to the July review argued that reducing incentives could weaken participation and governance. That is the commenter’s concern and should be treated as a position, not a measured finding. Neither that comment nor OpCo’s budget rationale supplies causal evidence about what the change did to participation. Establishing such effects would require outcome data and a credible comparison, with attention to other changes in delegate activity and proposal volume.

The practical lesson is narrower and more useful: ask which unit sets the budget, which asset is transferred, when its price is measured, and whether an average is a policy reference or an execution formula. Then ask what eligibility rules govern the payout and what costs intervene before the recipient realizes value. In RAD’s October review, the first two answers are explicit: USD budgets, ARB payouts. The three-month average is described as a review reference, while the precise conversion mechanics and actual Q4 outcomes are not established in that post.