Documentation
settlement

Network Settlement

The vault's side of a trade is a transaction nobody signs: the network executes it. This page explains what runs it, what it guarantees, and where the relay comes in.

Network notes and network accounts

A note can carry an attachment naming a network account as its target. The network's transaction builder picks up such notes, builds a transaction against that account, executes it and commits the result.

The BLUEDW vault is a network account. The relay's in-kind deposit and redeem notes are network notes targeting it. The relay sends them; the network executes them. The relay never signs a transaction as the vault.

Why there is a relay at all

On testnet, a single network transaction could do a whole buy, because Darwin minted its own constituent tokens. On mainnet the vault holds real coins, and real coins have to be bought on the DEX. A DEX order is filled asynchronously by a market maker, sometimes partially, a few seconds to minutes later. No single transaction can "pay USDCx and receive the coins" atomically.

So the work is split:

WhoDoes
The relayPlaces and re-prices DEX orders, collects the fills, sends the coins to the vault, sends you the result
The vault (network-executed)Values coins at Pragma prices, mints or burns shares, holds the coins

The rules that protect holders (share price, pro-rata redemption, who may deposit) sit in the vault. The parts that need patience sit in the relay.

The allowlist

The vault executes only note scripts whose roots are in its allowlist. The two the relay uses:

ScriptRoot
In-kind deposit v2 (in use)0x7451d73cb18ed93229bf89a878192fa2e4edef16b5a063f3275a133154dc4950
In-kind redeem v2 (in use)0xb79a9db5e3ee5adc9a641329b4e03ace07332a399e1123688b8a7c6be5071537

The allowlist holds ten roots in total: these two, the launch (v1) deposit and redeem, P2ID, Miden's standard configuration notes, and two legacy notes whose only permitted sender does not exist on mainnet. The full list, read from the chain, is on Note Scripts.

A note whose script is not in the allowlist is never executed. The allowlist is a storage map, and the vault's owner (the operator account) can add a root to it. That keeps the vault repairable, and it is a trust assumption. See Risks.

One transaction, all or nothing

A deposit is one transaction: read prices, compute the mint, mint your shares into a private note, move the coins into the vault. A redemption is one transaction: read holdings, release each coin, burn the shares. Either everything happens or nothing does, so shares and backing always move together.

Timing

The vault's own transaction takes seconds once the relay sends the deposit or redeem note: the note is committed, picked up by the network, executed and committed in a block. Most of a trade's ~2 minutes is the DEX side: orders placed, filled, sometimes re-priced. See How a Trade Works.

Fees during settlement

A network transaction pays its fee from the account it runs against: the vault, in USDCx. The vault keeps a small USDCx float for that, which is not counted in its NAV. If the float ran out, deposits and redemptions would wait until it was topped up. The coins are not at risk meanwhile.

What the network cannot do

It cannot choose a price: the note reads Pragma itself. It cannot open your share note: it is private. It cannot run a script outside the allowlist. What it can do is not run a note, for example if the oracle is stale. The operator can then reclaim its own deposit note and retry later.