The flow
Nothing is signed: every report is a read of the ledger as the venue’s party sees it, pinned to one point (an offset), so every figure in it agrees and the same read can be repeated later.Portfolio values
GET /v1/holders/{holderId}/portfolio values each holding in units of the instrument itself: a par or a rebasing unit is one. An accumulating unit has no price there, and so no value: its reserve’s price is on GET /v1/reserves/{reserveId}. Each line, and each instrument’s total, carries:
Values in different instruments are never added.
Movements
GET /v1/holders/{holderId}/movements and GET /v1/instruments/{instrumentId}/movements list each change of the Registry’s units, oldest first: one line per transaction, instrument and account, with the units it moved and the account’s balance after it. A holder’s list includes its predecessors’ accounts, so a successor reads one history. The instrument’s list spans its register, the Registrar’s own accounts among them.
Each line says what moved the units (kind), read off the venue’s record of the same transaction, and names that record in references:
Each line carries its ledger time, offset and update id, so it posts to a ledger as one entry and traces to its transaction.
Open orders
GET /v1/open-orders sums the primary market’s open orders per instrument: the subscriptions awaiting their NAV or their delivery, and the unsettled redemptions, in all and by the day each was claimed (byClaimDate). For a fund paid on the ledger, paymentsDue says what they owe in each payment asset its consents take, one entry per asset:
Worked example
One investor’s month after a 1,000-unit subscription, a 400-unit redemption and the period’s distribution. The demo ends with the first of these reads (chapter 11): the auditor exports the cap table as CSV.Controls
- Each investor reads only its own holdings, orders, statements and tax statements. The cap table and the plans are the venue’s and the auditor’s.
- Every read names the ledger point it was read at, and can be repeated at that point later.
- Nothing rewrites the record: no route edits a past operation, and the auditor can read everything and write nothing.
- NodeAsset computes the figures in the ledger’s own arithmetic, so a system that shows them never recomputes them.