Capital calls where each LP sees only its own notice.

No. It runs on the Canton DevNet with test Canton Coin. Dollar figures are the business scenario, and the coin is what actually moves.

On LocalNet and on the HackCanton DevNet node, a scripted run had every party sign its own transactions with its own key. On DevNet the node’s operator allocated those parties for us from keys we generated, since teams can’t allocate them themselves. All five keys sat on the machine that ran the script, so it shows the ledger needs each party’s signature, not that separate people held the keys, and this live site doesn’t use those parties. An earlier version of this web app let each person make a key in the browser, and the current browser-key flow hasn’t run on LocalNet. On this live site DRAW’s backend login acts for the demo seats. An LP that signs in with its own HackCanton login acts for its own party from its own browser instead. The app says which mode you’re in.

On DevNet, yes, if your HackCanton login has a wallet on the HackCanton node. Sign in on the seat screen and join as an LP. Your notice also shows up in the node’s Canton Coin wallet as an allocation request, and pressing Accept there pays it. DRAW’s server never receives your login. Every recorded run so far signed in with the team’s own login as the LP. Actions on this demo need an access code from the DRAW team.

Canton gives each contract a fixed set of parties who can read it, and settles a token transfer and a state change in one transaction. Those two properties are what make a private notice and a provable funded status possible.

Every notice in its fund, the payments waiting against them, and two totals: deployable now and unresolved.

No. An LP’s ledger returns its own commitment and notices only. Opening another LP’s notice link shows nothing, because the ledger returns nothing.

The notice and the commitment are private. Only the fund’s party and that LP’s party can read them, plus the node that hosts them. On DevNet DRAW’s backend login reads for every demo seat. Per the Splice Scan API docs, the Canton Coin transfer that pays a notice appears in the network’s Scan service with its random reference and both party ids, whose hints such as draw-lpa are readable, while the notice and the commitment don’t. That comes from the docs, and DRAW hasn’t checked it against Scan. In production the fund would settle in a tokenized dollar through the same Token Standard allocation interface. The USDCx registry lists that interface, but DRAW hasn’t been run with USDCx.