Resolves the target chain's runtime (drives per-chain address validation).
The max number of each instrument kind that a given entity type can have at any time.
If undefined, it defaults to infinity.
Protected ReadonlycacheStaticinstanceThe process default: no per-entity cap, as every app configures it.
An operator's edit, whoever owns the row: skips only the entity capability check. A new address or chain re-runs every create-time check, including a fresh Nominis screen, and drops the old address's verdict.
Also clears payment-instrument.text. Every writer busts by customer alone,
which reaches no field tag, yet each write may change the text a cached
transaction q page matched on.
ProtectedsearchTags for a page: the scope its query searched (each customer's membership
tag, else the collection tag), so an empty page is bustable too, plus the
records it projects and the fields that chose or ordered its rows.
The consumer-writable slice. The Nominis screening verdict is deliberately
absent — it is partner-produced and lands via
PaymentInstrumentAdminService.update.
The wallet that sent a deposit, as a WALLET instrument of the receiving
ledger account's owner (origin: "DEPOSIT_SENDER", sending off); the live one
when the owner already holds it. Publishes nothing. A screen that cannot be
started comes back as screenFailure, and the next call starts it.
A self-custody blockchain wallet