Skip to content

feat(ledger-protocol-transition-map): map protocol version changes in ledger ranges - #491

Merged
egekoca merged 2 commits into
RevenantLabs:mainfrom
Caneryy:feat/ledger-protocol-transition-map
Sep 30, 2026
Merged

egekoca merged 2 commits into
RevenantLabs:mainfrom
Caneryy:feat/ledger-protocol-transition-map

Conversation

@Caneryy

@Caneryy Caneryy commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds a read-only Ledger Protocol Transition Map that scans a bounded Horizon ledger range and groups adjacent protocol versions.

  • Validates start ledger + bounded count before fetching
  • Groups contiguous same-version ledgers into runs
  • Marks exact transitions only when both neighboring sequences were fetched
  • Flags sequence gaps / partial pages so upgrades are not asserted across missing data
  • Shows network, range, and a copyable transition summary

Files

Entire slice under features/ledger-protocol-transition-map/ (35 files).

Out of scope

  • No unbounded history scan
  • No prediction of future upgrades
  • No changes outside this feature folder

Test plan

  • npm run verify:features -- ledger-protocol-transition-map
  • npm test -- --run features/ledger-protocol-transition-map (43 tests)

Closes #470

@drips-wave

drips-wave Bot commented Sep 29, 2026

Copy link
Copy Markdown

@Caneryy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@egekoca
egekoca merged commit ae8af41 into RevenantLabs:main Sep 30, 2026
1 check passed
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.

[Network & Infrastructure] Ledger Protocol Transition Map

2 participants