revert(kaspa): remove escrow startup verification#452
Merged
Conversation
The startup check that verifies escrow config matches hub anchor requires querying potentially old Kaspa transactions. The Kaspa REST APIs (both api-tn10 and rest.tn.kaspa.rollapp.network) fail to return old/spent transactions, causing validators to panic on startup. Removing this check to unblock the blumbus migration. The check was a footgun prevention but querying old TXs is unreliable. This reverts the changes from PR #441. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
api-tn10.kaspa.organdrest.tn.kaspa.rollapp.networkfail to return old/spent transactionsProblem
During the blumbus escrow migration, validators are panicking on startup:
The hub anchor TX is too old to be queryable via the Kaspa REST APIs.
Context
This reverts PR #441. The check was a footgun prevention for post-migration config drift, but querying old TXs is unreliable. We need an alternative approach that doesn't rely on querying potentially pruned transactions.
Test plan
cargo check -p validatorpasses🤖 Generated with Claude Code