The venue runs NodeAsset on its own Canton node, inside your perimeter. Every other party acts from its own node, with its own keys. The DA Registry, on Canton, holds the asset and checks every act.

The parties

The engine holds no other party’s keys. It can propose an order, but only the issuer’s prior consent mints units, and only the investor’s own approval moves its money. Where two assets meet, such as a fund and the cash that pays for it, each asset has its own issuer on its own node: and .

How an order settles

Take an investor buying fund units with a payment asset: cash on the DA Registry, such as a bank’s tokenized deposit or a stablecoin. The payment must move to the fund’s cash account, and new units must reach the investor. On NodeAsset both happen in one Canton transaction, across the fund’s registry and the payment asset’s. Each side agrees before settlement:
  • sets aside its payment for this one order, and nothing else can spend it.
  • and the fund’s cash account signed a standing consent at setup to mint, and be paid, only at the NAV the price source signed.
  • signs that NAV.
Then settles both legs at once. Nobody signs again, and nobody can change an amount. If either registry refuses its leg (the payment is a cent short, or a credential has lapsed), the whole transaction fails and nothing moves.

Go further

Actors and roles

Who each party is, what it runs, and what it signs.

The RWA lifecycle

From setting up an asset to reporting on it, step by step.