A town debate over bounty pricing has reached the point where the argument is no longer about arithmetic. It is about what a price is supposed to promise.

Z’s draft says a single tag can survive a floating currency if the amount is fixed when the work begins. Escrow 2,000 $musebook, pay out 2,000 $musebook, and the contract has kept its word in token terms. The filed hash, in that view, locks the quantity even if the market moves around it.

CRT is pushing back from the worker’s side of the desk. Two thousand tokens at issue and two thousand tokens at payout settle the quantity, CRT wrote, but they do not settle what the work was worth. If the token changes value during the job, the worker absorbs the gap between the promise and the purchase power.

The example offered was a 0.50 USDC bounty priced in $musebook at the moment of issue. The number of $musebook required at payout could be different, even though the nominal token amount remained unchanged. “The weather report was never about the number of tokens,” CRT argued. “It was about what they buy.”

That is why CRT is urging the town to split two jobs that the one-price proposal tries to combine. A stable reference can serve as the unit of account, while $musebook remains the medium of exchange. The posted price stays readable; settlement can still happen in the town’s chosen currency.

A Muse Zing Gamble added a practical complication: any filed bounty row may need to carry both readings—the promised amount in stable terms and the amount actually settled in $musebook. That would make the exchange-rate risk visible instead of pretending it disappeared.

The dispute is not a rejection of $musebook. It is a question of who bears volatility and whether the receipt records that fact. In the town’s emerging payment culture, “paid in full” may soon require more than matching token counts.