Architecture - NodeAsset

The engine and its API run at the venue and act only as the venue’s party. Register keepers, price sources and investors act on their own systems; see Who runs what.

The parts

Part	What it does	Runs where
Engine	The `/v1` API, four-eyes approvals, settlement, reconciliation, distributions, the event feed and webhooks	Your perimeter: one Java process
Engine database	What the engine decided and who decided it: the asset records, policies, holders, operations, approvals, holds, reconciliation runs and the event feed	Your PostgreSQL
PQS	Digital Asset’s participant query store: the ledger as the venue’s party sees it, projected into PostgreSQL. The engine reads the ledger here	Your perimeter, beside your Canton node
Canton node	Your Canton node. It hosts the venue’s party, and the engine writes through its Ledger API	Your perimeter, or your node provider
Your screens and systems	The screens the venue’s staff and its clients use, and the systems that call the engine: the bank’s own, or its systems integrator’s, built on the API	Yours
Identity provider	Signs in your staff, your systems and your investors (OIDC). The engine checks every token against its keys	Yours
DA Registry	Administers every asset: mints, burns, transfers and locks holdings under the token standard	DA’s Registry packages, on every Canton node that uses them
Other parties’ nodes	Each party’s own acts: accept, mint, burn, price, allocate, through its own wallet, registry tools or NAV system (Who runs what)	Each party’s own infrastructure

NodeAsset is the engine and its API. It ships no screens: the venue builds its own on the API, or has its systems integrator build them, and the demo shows a screen for each role.

The ledger is the source of truth. Every holding, reserve, subscription, credential and price is a contract on the parties’ Canton nodes, and the engine reads them back through PQS. Its own database holds only what it decided: the requests it took, who approved them, what it stopped, and what reconciliation found.

Every asset runs on the same Daml packages. Adding an asset records its configuration, under four eyes, and deploys no contract.

Who runs what

Each party above can be a firm of its own, or a desk of the venue’s own organization. Either way, each keeps its own party and its own key, so the same signatures and the same separation hold. Deployment patterns lists who can be internal or external, the rules every combination keeps, and five named patterns.

The parties and what each signs are on Parties and the DA Registry; how the API protects itself is on API security.

​The parts

​Who runs what

The parts

Who runs what