Demo walkthrough

The demo runs one story on the product: a money-market fund, FUND, priced each day by its administrator, is bought and sold with a bank’s tokenized deposit, TD. The fund’s units and the deposit sit on two registries, and every order settles across both in one transaction. One screen shows every party in a box of its own, above the ledger strip. Each button signs a real transaction as its box’s party, on that party’s own node, and the box that acts next lights up. Open the live demo. We run it on a local network of its own, for the demo only: every visitor shares that network, and Reset restores it from its snapshot. A deployment of yours runs on DevNet, TestNet or MainNet.

The screen

The page scrolls. The controls stay at the top of the window and the ledger strip at the bottom, with the boxes between them.

Control	What it does
Next step	Highlights the box and the button that act next; pressing it again presses that button. Any button a box offers can be pressed too
Chapter and Autoplay	Jump to the start of a chapter, or play on to the end at a readable pace
Reset	Restores the network from its snapshot and starts the engine afresh, in a minute or two
Payment	Shows whether the current order is paid on the ledger, in the deposit, or off the ledger, by bank transfer
Layout	Switches between the 4×2 grid and six boxes for a narrower screen. On a phone the boxes stack
Each box	Shows what waits for its party now, with the next button highlighted, and its holdings. Below them, its own history scrolls, newest first: a line for each act it took or transaction its node saw, with the chapter, the Tx number and the time. A refused act shows in red with its code. Click a line to light its transaction
The ledger strip	Shows the network, the synchronizer, the ledger end, the record time, the count of transactions and the explorer link. Each transaction is a card, the newest on the right, with the Tx number of its workflow page. Hover a card to light the boxes that saw it and dim the rest; click it to see it as each party’s node received it
The explorer	Opens the local network’s own explorer, read-only. An explorer shows network-level data. The fund’s and the deposit’s transactions are private to their parties, so the cards are their evidence

The cast

Each box names the node that hosts its party.

Box	Who	Signs
operations and approver	The venue’s maker and its approver: four eyes on every change	Through the engine: records, offers, orders and settlements
	The fund’s transfer agent, with the fund’s treasury	Mints, burns, the fund’s consent and each distribution line
	The fund’s administrator	The day’s NAV and each order’s price
	The bank that issues the tokenized deposit, on its own registry	The deposit’s mints and burns
A and B	Two investors, each through its custodian	Their acceptances and payments
	Audit, reading through the engine	Nothing

The chapters

Chapter	What you see	Read more
1. The parties and the asset	FUND is recorded under four eyes: the maker’s own approval is refused, and a second person approves. Its policy then requires a verified residency and investor type. The issuer’s box shows the consent it signed once, on its own node. Last, FUND’s registry is made to check DA’s block list, so every settlement after it runs with the list on.	Set up an asset
2. Onboarding	Investor A’s verified claims are recorded under four eyes, and it accepts FUND’s offer. Investor B, with nothing verified, is refused before anything reaches the ledger; once verified, it is admitted the same way.	Onboard investors
3. Cash for the investor (on the ledger)	Investor A asks the bank for deposit, and the bank mints it on its own registry.	The on-ledger payment leg
4. The day’s price	The price source signs the day’s NAV. The venue reads it and cannot set one.	Price the asset
5. A subscription, paid on the ledger	Investor A orders 1,000 units before the NAV is known, and the price source prices the order. The investor approves its payment once, and one transaction on both registries mints the units and pays for them. Investor B sees none of it.	Subscriptions
6. A subscription, paid off the ledger	500 units, the cash wired by bank transfer and shown dashed. The issuer mints once its bank confirms the cash, and the venue delivers the order against that mint.	Subscriptions
7. A redemption	400 units burned and paid from the fund’s treasury in one transaction, the payout rounded down.	Redemptions
8. A dealing cycle	Investor B subscribes and Investor A redeems at one NAV, settled in one transaction. The treasury moves only the net, and each investor sees only its own legs.	Dealing cycles
9. A freeze	Investor B is frozen, and the issuer’s block list names it: its order is refused by the venue and its transfer by the registry. Two approvers lift the freeze.	Holds, freezes and issuer powers
10. A limit loosened	Raising the holder limit takes two approvers and a day’s notice. Lowering it again applies at once, and the raise never does.	Set up an asset
11. Period end and reconciliation	The month-end NAV, and the distribution under four eyes, each line paid in units, accepted and booked. Reconciliation runs clean, and the auditor exports the cap table as CSV.	Distributions and period end · Reconciliation · Reporting

What to watch for

Nobody signs at settlement. Each side authorized its own leg in advance: the investor once per order, the fund’s issuer and treasury once, in the fund’s consent.
The venue never sets a price: every order settles at the price the price source signed for it.
Every change has a maker and an approver. The maker’s own approval is refused in chapter 1, and two approvers are needed in chapters 9 and 10.
Each party sees only its own: hover the settlement in chapter 5, and Investor B’s box stays dark. Investor B’s history has no line for Investor A’s orders.

NodeAsset

Capabilities

Comparison with EVM/SVM

Evaluate

The screen

The cast

The chapters

What to watch for

​The screen

​The cast

​The chapters

​What to watch for

The screen

The cast

The chapters

What to watch for