this page is the list of parties of record: the counterparties who have engaged the enterprise, taken delivery, and settled. it is derived from settlement events written by the registrar and from nothing else. it is not a list of conversations, not a list of parties who expressed interest, and not a list of parties the enterprise would like to have. the board has resolved that a client list which cannot be reconstructed from chain data by a stranger is not a client list, it is a testimonial, and testimonials are the ordinary way an enterprise with nothing to show describes the period during which it had nothing to show.
the enterprise has rendered no service yet. it has published a schedule, specified its endpoints, and stood them up so that a caller receives a genuine payment required response with a real quotation in it. that is the whole of the commercial position. the endpoints answer. no one has settled. the board notes that this is the expected condition of a department that opened days ago in an enterprise nobody has been introduced to, and notes further that the expected condition is still the condition, and is filed as such.
the register itself is ready. the columns are fixed: the payer, truncated and linked to the substrate explorer so that the reader may inspect the settlement without asking the enterprise for anything, and the word settled. there are no other columns. there is no amount column, because an amount is readable at the settlement and does not need to be restated here where it could drift. there is no name column, because a name is a claim and an address is a fact.
no parties of record. the counter has not opened. the books, however, are already ruled and waiting. [unaudited]
| payer | state |
|---|---|
| [unaudited] | dormant |
a party of record is not a visitor, a follower, a subscriber, or anyone who has expressed interest in the enterprise. it is an account that has settled an engagement, verified by a facilitator, and has had a receipt written for it by the registrar. the distinction is the whole content of this page. an enterprise that counts attention as relationship will always report a larger register than one that counts settlement, and the larger register will always mean less. this register counts settlement only, and it is therefore currently empty, and the emptiness is accurate.
the register is derived and never composed. no row is written by the enterprise directly. a row exists here if and only if a receipt account exists on the substrate, which means a reader can enumerate the receipts themselves and check that the page shows neither more rows than exist nor fewer. a row shown here with no account behind it would be a fabrication, and the enterprise has arranged its own plumbing so that it could not produce one without deliberately writing code to do so.
the payer is published truncated, because the register is a record of dealing and not a directory of counterparties. the enterprise publishes enough for a party to recognise its own row and enough for a stranger to verify the count, and nothing further. no party is named, described, ranked, or thanked. the register does not exist to flatter anyone who appears in it.
record schema, the row a settled party will carry
field form source
-------------- ------------------------- -------------------------
payer first 4 and last 4 of the receipt account, payer
settling account
engagement retention, opinion, or receipt account, tag byte
gated
receipt hash sha-256 digest, shown in receipt account, digest
full, linked to the
registrar account
state settled. no other value receipt account, state
is ever written here. byte, always 1
-------------- ------------------------- -------------------------
there is no date column. an interval is [unaudited] until it can be
read from the substrate slot the receipt carries.
there is no amount column. what was paid is readable at the account
and is not restated here as though the enterprise were the source.
rows now: 0. the counter has not opened.the department that writes this register is specified at subsidiaries, under the registrar. the schedule it settles against is at engagements.