Skip to content

Conversation

@arepala-uml
Copy link
Contributor

  1. Added ledgerValidateHistorical option to the dingo configuration, defaulting to '14d'.
  2. This change replaces the hard-coded two-week historical validation threshold with a configurable setting.

Closes #672

Signed-off-by: Akhil Repala <arepala@blinklabs.io>
@arepala-uml arepala-uml marked this pull request as ready for review August 10, 2025 22:24
@arepala-uml arepala-uml requested a review from a team as a code owner August 10, 2025 22:24
"fmt"
"io"
"log/slog"
"time"
Copy link
Member

Choose a reason for hiding this comment

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

Rather than use time, we should use blocks.

This is part of the CardanoNodeConfig genesis configs. We can skip Byron, since we'll never be in Byron and it be recent. In the ShelleyGenesis() return, you can get SecurityParam from the gouroboros ledger shelley.ShelleyGenesis object, which is an int (though it actually has to be positive...)

We load this similarly to epoch length.

Copy link
Contributor

Choose a reason for hiding this comment

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

We can make this change in a follow-up ticket

@agaffney agaffney dismissed wolf31o2’s stale review August 14, 2025 20:39

We can make this change in a follow-up ticket

@agaffney agaffney merged commit 4872d43 into main Aug 14, 2025
12 of 15 checks passed
@agaffney agaffney deleted the ledger_validation_threshold branch August 14, 2025 20:39
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.

Make ledger historical validation threshold configurable

4 participants