Skip to content
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

Move a couple of mempool operations to work on ledgerstates instead #1384

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

jasagredo
Copy link
Contributor

@jasagredo jasagredo commented Feb 7, 2025

Description

10.2
image

UTxO-HD before this:
image

UTxO-HD after this:
image

The changes are in line with what is described in #1383. There are still some more operations that could be lifted to ledger states.

@jasagredo jasagredo marked this pull request as ready for review February 7, 2025 16:35
@jasagredo jasagredo self-assigned this Feb 7, 2025
Copy link
Contributor

@nfrisby nfrisby left a comment

Choose a reason for hiding this comment

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

Very economical diff! I just think there needs to be some more comments. Maybe a link to Issue #1383 would discharge some of the heavy lifting.

@jasagredo jasagredo force-pushed the js/some-mempool-ops-on-lstates branch from 83d30fc to 48847e8 Compare February 10, 2025 10:58
@jasagredo jasagredo force-pushed the js/some-mempool-ops-on-lstates branch from 48847e8 to 333efad Compare February 10, 2025 11:00
Base automatically changed from js/tails-caf to utxo-hd-main February 10, 2025 12:41
@jasagredo jasagredo force-pushed the js/some-mempool-ops-on-lstates branch from 333efad to 12439b3 Compare February 10, 2025 12:42
@jasagredo jasagredo merged commit d5232aa into utxo-hd-main Feb 10, 2025
4 of 5 checks passed
@jasagredo jasagredo deleted the js/some-mempool-ops-on-lstates branch February 10, 2025 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants