Skip to content

TxSubmission Logic: integration #1522

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

TxSubmission Logic: integration #1522

wants to merge 4 commits into from

Conversation

coot
Copy link
Contributor

@coot coot commented May 26, 2025

Description

  • Added txWireSize method to TxLimits class
  • Integrate new tx submission protocol
  • MempoolSize: added mxExUnits{Memory,Steps}
  • updated changelog

crocodile-dentist and others added 4 commits May 20, 2025 10:14
The new method leverages a corresponding method recently exposed by
ledger side to provide encoded transaction sizes to eg. diffusion layer.
Co-Author: Armando Santos <[email protected]>
Co-Author: Marcin Szamotulski <[email protected]>
Co-Author: Marcin Wójtowicz <[email protected]>
@coot coot force-pushed the coot/tx-submission-10.5 branch from 15846cd to b8dd378 Compare May 26, 2025 15:22
Comment on lines +97 to +100
, msExUnitsMemory :: !Natural
-- ^ The execution memory units of all the transactions in the mempool.
, msExUnitsSteps :: !Natural
-- ^ The execution steps of all the transactions in the mempool.
Copy link
Member

Choose a reason for hiding this comment

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

This MempoolSize is part of the abstract Cardano-agnostic Consensus layer, so it is a bit weird for it to directly mention Cardano-specific implementation details like script memory/steps (also see #1523). In particular, is it intentional that reference script size is missing here?

I think the more principled thing to do here would be to add TxMeasure as a field (which in particular contains the byte size, so that can also be removed).


Also, is this change actually related to the new TxSubmission logic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants