Oracle interface and its NAV feed, is on Price source.
Choose the price source
The asset’s record names its price source, under four eyes (Set up an asset). A fund’s consent names the same party unless the proposal names another, and the fund’s register keeper and treasury sign it with that party in it, so the venue alone cannot change who prices. A consent that names the venue’s own party, or the fund’s own register keeper or treasury, is refused, by the engine and by the consent itself: the venue would price what it settles, and the issuer what it issues and pays for. A fund’s price source is its administrator, and a commodity’s its price provider. An asset at par, such as a tokenized deposit or a stablecoin, has none, and a backed instrument’s reserve reads each of its assets’ price sources.How a price reaches settlement
The order is recorded before its NAV is known, and the price source prices it once its dealing point has closed (forward pricing). Who signs each transaction, and who sees it, is on Price the asset, Subscriptions and Redemptions.What the engine and the ledger check
The engine refuses by name before it submits, and the ledger’s checks stand behind each refusal, so a transaction that reaches them with the wrong price fails and nothing moves.
The NAV feed at the venue
The administrator also sends its official NAV off the ledger, with an expiry and a kill switch, which a signature cannot carry. Each statement starts a reconciliation run, which holds the asset:- when the kill switch is pulled, as the statement arrives;
- when the NAV has expired, at the first run after its
expiresAt; - when the feed’s official NAV differs from the price source’s point of the same business date by more than the source’s tolerance.
instrument-held. A reserve that holds the asset refuses a point past its freshness window on the ledger. A fresh NAV, or the switch lowered, clears the finding but not the hold: risk asks for the release, and two approvers sign it. How the administrator sends the feed is on Price source.
Set it up
1
Name the price source
Record the asset with its price source, under four eyes. A fund paid on the ledger names the same party in its consent, which its issuer and treasury sign.
2
The price source's node vets the packages
From the release the venue runs: see Price source.
3
Name the template
PublishedNav is the default. For a template of the price source’s own, set venue.parties.oracle-template to its name as PQS knows it, and add the same name to PQS’s metadata filter.4
Connect the feed
Add a
nav source to venue.recon.external.sources, and give whoever posts the statements a client of its own at your identity provider, in the feed role.5
Check it
GET /v1/instruments/{instrumentId}/price answers the price now and the contract it comes from. GET /v1/instruments/{instrumentId}/nav-feed answers the feed’s state: live, halted with its reasons, or no-statement before any NAV arrives.Settings
Outside providers
The price source’s signature is the only price an order settles at. An outside provider adds an independent check, or carries the price source’s own NAV:
A provider’s NAV reaches the engine as a
nav source: a connector of the deployment’s own posts it as a statement with its own expiry, and the engine compares it with the price source’s point, as it does any feed. Set the source’s blocking: false to make its findings reports only. No provider’s figure prices an order, overrides the price source’s or is averaged into it. No NodeAsset transaction reads a provider’s contract, so a provider learns of no order. NodeAsset ships no provider connector.
Related: Price source · Price the asset · NAV feed and oracles · Pricing