Proposal Canton Launchpad #375
Conversation
Addresses the 'Network Topology Visualizer' gap named explicitly in the official Canton Network DevEx Survey (Jan-Feb 2026). Visual LocalNet control plane with topology canvas, snapshot/restore, and error decoder. Live PoC: https://canton-launchpad.vercel.app
|
@cvijandj, your proposal is missing a Special Interest Group (SIG) label. Adding the right SIG label ensures the relevant domain experts can find and review your proposal, Check more about SIGs. Please add one of the following labels to this PR:
Not sure which one fits? Pick the closest match to your proposal's domain. You can add a label from the right sidebar under "Labels". |
|
@cvijandj, thank you for your interest in the Canton Development Fund! Your proposal needs a valid Tech & Ops Committee champion organization. The champion field is either empty, contains placeholder text, or names an organization that is not a current Tech & Ops Committee member. Per CIP-0100, all external proposals require a Tech & Ops Committee champion. Next steps:
If you need help finding a champion, reach out to SIGs or any Tech & Ops Committee member. This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed. |
|
Hi, I'm the author of this proposal and I'm looking for a Tech & Ops Committee champion to reopen it, also bot closed it before I added reviewers so I can not add you guys now, so I will add you in cc of this comment. This directly implements the "Network Topology Visualizer" the Canton Foundation's own DevEx survey named as a missing tool. The PoC (with mocked data) is already live before the grant - https://canton-launchpad.vercel.app/ (90s walkthrough: https://www.loom.com/share/65c99675b83d4d0693931e8a9c380207) - and the companion canton-error-glossary is already published on GitHub with 12 documented Canton errors under Apache-2.0. If anyone is willing to champion or can point me to the right person, I'd really appreciate it. cc @tkatrichenko @hythloda @stas-sbi @waynecollier-da @isegall-da |
Replaced "under 30 seconds" with "under 3 minutes" in both the deliverable description and acceptance criteria for Milestone 2. The snapshot approach (pg_dump + Docker volume restore) requires stopping and restarting Canton containers, making 30s unrealistic. 3 minutes is an honest upper bound that still demonstrates clear value over the 8-10 minute cold start baseline.
|
Milestone 2 update - snapshot/restore timing Updated the time claim from "under 30 seconds" to "under 3 minutes" after reviewing against real-world behavior. The restore process needs to synchronize state and restart the nodes, so 2–4 minutes is the honest number. Still a meaningful improvement over the 8–10 minute cold start baseline, just wanted the proposal to reflect what's actually tested. |
Development Fund Proposal Submission
Proposal file: proposals/canton-launchpad.md
Summary
Canton Launchpad is a visual LocalNet control plane for Canton - a one-click desktop app that shows real-time synchronizer connection state on a React Flow topology canvas, decodes JVM/gRPC exceptions into plain-English diagnostics, and reduces sandbox iteration time from ~10 minutes to seconds via snapshot/restore. It directly implements the "Network Topology Visualizer" the Canton Foundation's own DevEx Survey named as a missing tool.
Checklist
/proposals/Notes for Reviewers
canton-error-glossaryresource is already live on GitHub with 12 documented errors under Apache-2.0: https://github.com/cvijandj/canton-error-glossary