What happened
A NanoGPT cost receipt used a decimal representation longer than our original parser allowed. The analysis worked, but the cost needed an accounting fix.
What changed
The parser accepts bounded decimal strings and converts them to integer microdollars with upward rounding. It avoids floating-point arithmetic. Invalid receipts retain a conservative hold without blocking other receipts.
How we checked
Backend regressions cover decimal parsing and billing behavior. The local reconciliation record confirms that the recorded provider operations and model probe were accounted for.
The limit
This is backend accounting evidence. It does not establish production prices, real token settlement or an automatic on-chain burn service.
Local billing regressions and reconciliation
Open the local verification recordEngineering record from 28 September 2026. Simulated balances and wallets; no production settlement or independent security audit.