Proposal: Canton Transaction Debugger#297
Open
infrasingularity wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Development Fund Proposal Submission
Proposal file:
/proposals/canton-transaction-debugger.mdSummary
A Canton-native Transaction Debugger that turns failed Ledger API submissions into human-readable diagnoses and shareable, privacy-aware debug bundles. It extends the existing Canton developer toolchain (Ledger API rejection payloads, correlation IDs, structured logs) rather than replacing any component, and reduces time-to-root-cause for privacy- and authorization-heavy failures from hours to minutes.
Checklist
/proposals/Notes for Reviewers
Label:
daml-toolingThis proposal is a single-objective debugger build. Scoped localnet replay is included as a small, bounded follow-on (Milestone 6) and does not gate MVP value or compete with the debugger objective. Funding is broken out per milestone with deliverables and acceptance criteria tied to ecosystem value (adoption, time-to-diagnosis, support load), not artifact delivery.
The team (InfraSingularity) ships Daml-based projects and operates production Canton validator infrastructure. Relevant SIGs: Daml Language & Developer Tooling, Canton APIs, dApp Integration.
Champion: TBD
Total funding request: 1,430,000 CC across 6 milestones (14 weeks).