Skip to content

Proposal: Transaction Profiler DPM Component#379

Open
shanu12joshi wants to merge 2 commits into
canton-foundation:mainfrom
shanu12joshi:Transaction_Profiler_DPM_Component
Open

Proposal: Transaction Profiler DPM Component#379
shanu12joshi wants to merge 2 commits into
canton-foundation:mainfrom
shanu12joshi:Transaction_Profiler_DPM_Component

Conversation

@shanu12joshi

Copy link
Copy Markdown

Development Fund Proposal Submission

Proposal file:
/proposals/transaction-profiler-dpm.md


Summary

We are building a DPM Component, Canton Pre-Flight Transaction Profiler that estimates sequencer traffic cost and checks validator readiness before a transaction is submitted to the Canton network, built for validator, operators and multi-party workflow developers. Similar to how Tenderly works on EVM. The component estimates what a transaction will cost and whether it will succeed before it is submitted.

Total request: 130,000 CC across four milestones over one months.


Checklist

  • Proposal file added under /proposals/
  • Milestones and funding amounts defined
  • Acceptance criteria included
  • Alignment with Canton priorities described

@github-actions

Copy link
Copy Markdown

@shanu12joshi, 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:

  • attestor-pools-daos-multisig
  • canton-apis
  • canton-protocol-multi-synchronizer
  • daml-tooling
  • dapp-integration
  • dar-app-management
  • defi-liquidity
  • defi-protocols
  • financial-workflows-composability
  • global-synchronizer-scaling
  • node-deployment-operations
  • onchain-governance
  • party-portability-data-resilience
  • regulatory-compliance
  • token-asset-standards
  • tokenomics
  • wallet-apps

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".

@github-actions

Copy link
Copy Markdown

@shanu12joshi, 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:

  1. Identify a Tech & Ops Committee member organization willing to champion your proposal
  2. Update the Champion field with their name
  3. Reopen this PR

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.

@github-actions github-actions Bot closed this May 27, 2026
@github-project-automation github-project-automation Bot moved this from Incoming to Declined in Dev Fund Incoming May 27, 2026
@shanu12joshi

Copy link
Copy Markdown
Author

@Jatinp26 Can you please review the PR? Your review would be really appreciated!

@shanu12joshi

shanu12joshi commented Jun 23, 2026

Copy link
Copy Markdown
Author

Hey @hrischuk-da , I have found a champion for this PR, Would it be possible to get this marked as ready to champion?


## Abstract

This proposal outlines a grant proposal to build Canton Pre-Flight Transaction Profiler, The Transaction Profiler is a DPM component that estimates sequencer traffic cost and checks validator readiness before a transaction is submitted to the Canton network, built for validator, operators and multi-party workflow developers. Similar to how Tenderly works on EVM. The component estimates what a transaction will cost and whether it will succeed before it is submitted.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand the problem this is trying to solve. However, I think this proposal is too narrow to be really helpful since it is using the tx prepare statement and doing a CC conversion. I expect most validators will have an auto-top up enabled so they won't run out of traffic. The validator will be moving to party based traffic costs so this approach will become obsolete shortly.

I do think a tool around traffic has merit but it would need to be much more functional in that it is tailored to help the developer design for minimizing traffic cost.

@Jatinp26 Jatinp26 reopened this Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Declined

Development

Successfully merging this pull request may close these issues.

3 participants