Skip to content
CCPEDIAby Unity Nodes
Discussions/App Development/Raposza: Tools for Canton developmentForum ↗

Raposza: Tools for Canton development

App Development1 posts8 viewsLast activity 3h ago
RA
raposzaOP
3h ago

tools = AS $you CREATE Raposza:Tools WITH { "user": "$you" };
AS $you EXERCISE ON $tools DevSpeed WITH { "warp": "on" };

What if you could start a database, a complete Canton LocalNet without Docker (because Docker isn’t allowed inside the walls), PQS and an OIDC-compliant server to handle all things auth, restore a stored snapshot and be ready to test in under 5 minutes on your own workstation?
All from one integrated UI, on Windows or Linux (no Mac support yet). And it all works right out of the tin.

And what if you could access all three participants on LocalNet - or any other Canton participant - using something that looks a bit like DBeaver?
Browse users, parties, templates, contracts and contract history? Query contracts with a slightly strange dialect of SQL? Create new users, parties and contracts, exercise choices and filter contracts?

Set up test data, save a snapshot, restore it in 2–3 minutes and run your tests again?

Raposza Tools — Public Beta Release

  • Raposza Sandbox — Single Participant + LocalNetND (No Docker)
  • Raposza Workbench — “DBeaver for Canton”
  • CaQL — Like SQL, but for Canton

First installation instructions

Or download tools_skill.md and let Qwlaude do the thinking (pre-beta, not extensively tested).

Workbench in particular is still rudimentary, and the feature set is limited. But what is there works.

Supportive comments, constructive criticism, feature requests, bug reports and PRs are very welcome.

If you like it, tell everyone. If you don’t, tell me.

PS

Claude insisted that I add this:

  1. “Under 5 minutes … right out of the tin.” The first run downloads DPM, about 1.2 GiB, which took 4 m 43 s through the proxy (A-77). It also needs get.digitalasset.com to be reachable, which machines “inside the walls” often can’t reach. Say “once installed”, or mention Install from file… Also, the idiom is “out of the box”; “out of the tin” is a mix of two idioms.

  2. “OIDC-compliant server to handle all things auth.” It is a mock. It mints a token for any subject if asked, and it publishes its own private keys. The last conformance run was 32 PASSED and 3 REVIEW. Readers at regulated organisations will take “handles all things auth” literally. Something like “a local mock OpenID Provider, so authenticated ledgers work from the start” is safer.

  3. “Any other Canton ledger.” It works only with a pasted JWT, and the connection is read-only by default. There is no sign-in flow: workbench_corporate_oidc.md is preparation, not a build. Ledger API v1 has been measured on 2.9.6 only.

  4. “Create … contracts, exercise choices and filter contracts.”
    Writing works through CaQL only. There are no forms (“Explore only; there is no Act pane”).
    WHERE filters in the Workbench, over at most 1000 contracts read.
    Next to “looks a bit like DBeaver”, readers will expect forms and server-side filtering.

  5. Save snapshot runs on EDT and freezes the UI while saving: A-83 is postponed. The skill doc warns about it; the post doesn’t.

I hope you have not been promised too much now :slight_smile:

← Back to Discussions