fix(kaspa): handle null payload in transaction trace#450
Merged
Conversation
Migration transactions have no payload (no withdrawals processed), but the trace function required a non-null payload. Treat null as empty — no message IDs to extract. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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
MessageIDsencodes to zero bytes → Kaspa stores as null)recursive_trace_transactions) required a non-null payload and would error with "No payload found in transaction"Context
After migration, the post-migration sync traces the new escrow UTXO back to the old hub anchor via the migration TX. The migration TX has no withdrawal messages (just moves funds), so its payload is null.
Test plan
api-tn10.kaspa.org🤖 Generated with Claude Code