Skip to content

Conversation

sgillespie
Copy link
Contributor

Description

This separates the Ledger State from Ledger Tables, and we carry them separately. This allows us to keep the smallest possible UTxO set when applying blocks to the ledger state.

Continuation of #1996

Checklist

  • Commit sequence broadly makes sense
  • Commits have useful messages
  • New tests are added if needed and existing tests are updated
  • Any changes are noted in the changelog
  • Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
  • Self-reviewed the diff

Migrations

  • The pr causes a breaking change of type a,b or c
  • If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
  • Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

This allows us to carry around ledger tables with a minimal UTxO
set, which reduces the amount of processing we have to do when
applying blocks to the ledger state
@sgillespie sgillespie mentioned this pull request Sep 2, 2025
9 tasks
@sgillespie sgillespie changed the title Feature/utxo integ Integrate UTxO-HD Sep 2, 2025
@kderme kderme mentioned this pull request Sep 4, 2025
9 tasks
@sgillespie
Copy link
Contributor Author

Superceded by #1999

@sgillespie sgillespie closed this Sep 11, 2025
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.

1 participant