Skip to content

[WIP] SUBLEDGER implementation#5544

Draft
teodanciu wants to merge 4 commits intomasterfrom
td/sub-ledger-implementation
Draft

[WIP] SUBLEDGER implementation#5544
teodanciu wants to merge 4 commits intomasterfrom
td/sub-ledger-implementation

Conversation

@teodanciu
Copy link
Contributor

Description

Checklist

  • Commits in meaningful sequence and with useful messages.
  • Tests added or updated when needed.
  • CHANGELOG.md files updated for packages with externally visible changes.
    NOTE: New section is never added with the code changes. (See RELEASING.md).
  • Versions updated in .cabal and CHANGELOG.md files when necessary, according to the
    versioning process.
  • Version bounds in .cabal files updated when necessary.
    NOTE: If bounds change in a cabal file, that package itself must have a version increase. (See RELEASING.md).
  • Code formatted (use scripts/fourmolize.sh).
  • Cabal files formatted (use scripts/cabal-format.sh).
  • CDDL files are up to date (use scripts/gen-cddl.sh)
  • hie.yaml updated (use scripts/gen-hie.sh).
  • Self-reviewed the diff.

@teodanciu teodanciu force-pushed the td/sub-ledger-implementation branch 3 times, most recently from adc236b to 85807e0 Compare January 28, 2026 17:20
@teodanciu teodanciu force-pushed the td/sub-ledger-implementation branch from 85807e0 to af2a02f Compare January 30, 2026 13:12
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