Implementation - NodeAsset

Two kinds of work bring NodeAsset into production: configuration, set in NodeAsset itself, and integration, connecting NodeAsset to the systems you already run. A new asset is configuration; a new system is integration.

Configuration

You configure NodeAsset through its API, under four eyes where it matters, without changing code.

Area	What you set
A new asset	Its record, how it is valued, its price source, what backs it, its payment asset and the issuer’s consent
Its policy	Holding limits, fund size, daily limits, lock-ups, dealing and transfer windows, countries, investor types
Eligibility	Whose credential the asset requires, the claims an admission needs, and the KYC issuers whose credentials count; for the register keeper’s credential, the register keeper accepts these terms into its admission consent
People	Who holds each role, in your identity provider
Prices	The NAV feed’s expiry and tolerance
Reconciliation	Its schedule, and the outside sources it compares against
Notifications	The webhook receivers, and the events each takes
Retention	How long each kind of history is kept

Integration

Your systems connect through NodeAsset’s API, its event feed and webhooks, and the standards each party already uses.

Your system	What it exchanges with NodeAsset	Through
Core banking and cash	Cash confirmations for orders paid off the ledger; the asset’s cash account	The API; the issuer’s own wallet
KYC and screening	Verified claims, their expiry, and screening hits	Webhooks and the API
Fund administration	The daily NAV and the distribution list	The NAV feed, by API or file
The register	The transfer agent’s statement of holdings	Statements, by file or API
Investors’ custodians	Payment requests and their answers	Standard Canton token wallets (CIP-56, CIP-112)
Identity	Staff and investor sign-in	Your OIDC provider
Your screens	Your staff’s work, and your investors’ orders, holdings and statements, in your own apps	The API and its OpenAPI document; the screens are yours
Monitoring	Health, control events and the reconciliation verdict	The event feed and signed webhooks
Canton and the DA Registry	Your node, and the registries your assets live on	Install

NodeAsset is the engine and its API. The screens your staff use, and the channels your investors use, are your own, built by you or your systems integrator against the API; the demo shows a screen for each role.

A typical project

Install and connect your Canton node, NodeAsset, your identity provider and monitoring, on DevNet or TestNet first. See the Engine tab.
Configure the first asset, its policy and its price source.
Integrate KYC, the NAV feed, the register’s statements and cash.
Build the screens your staff use and the channels your investors use.
Rehearse on DevNet or TestNet, run the control matrix tests, then go live on MainNet.

Who	Does
Your IT	The nodes, the identity provider, monitoring and backups
Your systems integrator	The integrations, the screens and the channels
Your compliance team	Policies, eligibility rules and the control matrix
The NodeAsset team	The engine, its releases, and configuration support

Related: Integrations at a glance · Developers · FAQ