assets — a fixed-asset register with derived postings
Depreciation schedules held as state, charges derived from the schedule and the chain height, and no custody of any asset.
A general ledger takes the amount from its caller, so it cannot tell a double-booked month from a correct one. This realm never takes an amount: it keeps a per-asset high-water mark, so a charge can be neither repeated nor skipped. That is the whole product, and it proves arithmetic — not truth. Nothing here ties a cost figure to a real holding.
State
- registers opened: 1
- chain height: 830560
The chart is two accounts and is fixed
| code | name | kind | normal |
|---|---|---|---|
5500 |
Depreciation expense | expense | debit |
1590 |
Accumulated depreciation | asset (contra) | debit |
Every entry is a debit to 5500 against an equal credit to 1590. There is no way to open a third account, and the cost basis never reaches the book — booking it would need a liability or an equity plug asserting how the asset was funded, which this realm does not know.
1590 is an asset account, so its normal balance reads negative. The positive figure is AccumulatedCredit.
Bounds
| bound | value |
|---|---|
| assets per register | 64 |
| entries per register | 8192 |
| label length | 64 |
| shortest period | 100 blocks |
One asset is booked per call: the schedule loop's bound is unpriced upstream, so a bulk entrypoint would multiply an unpriced cost by the asset count.
Reading a register
/r/g1ut6uspuh73e02yauxpmyt8g3wwddaq8utagvm3/assets:<address>