Skip to content

harden frame tx decoding from malformed responses - #878

Merged
pk910 merged 5 commits into
masterfrom
pk910/frames-devnet-0-fixes-2
Oct 2, 2026
Merged

pk910 merged 5 commits into
masterfrom
pk910/frames-devnet-0-fixes-2

Conversation

@pk910

@pk910 pk910 commented Sep 27, 2026

Copy link
Copy Markdown
Member

No description provided.

@redpandabot

This comment has been minimized.

Both sides added process_transactions_test.go; the resolution keeps every
test from each.
A blob or set-code transaction reported without the recipient its type
requires decodes as an unknown type, like a frame transaction reported
without its frames. Its missing recipient was no evidence of a creation,
yet a CREATE address was derived from it and registered as a contract.

A creation is now claimed only for a transaction decoded in full.
@pk910
pk910 enabled auto-merge October 2, 2026 11:04

@redpandabot redpandabot Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Summary

The PR hardens tx indexing against clients that report a decodable transaction type without its type-specific content: the fetcher retries other clients and only falls back to the poorer answer, and processTransaction no longer reads a missing recipient of an undecoded transaction as a contract creation. The core fix is sound across the retry/fallback paths I traced, but the previously flagged sender-only debit for an undecoded value transfer remains unaddressed.

Issues

  • 🟡 indexer/execution/txindexer/process_transactions.go:375 — value transfer of an undecoded transaction is recorded as a sender-only debit — see the thread on that line

Reviewed @ 9debd719
"RTFM."

Comment thread indexer/execution/txindexer/process_transactions.go
@pk910
pk910 disabled auto-merge October 2, 2026 15:06
@pk910
pk910 merged commit 5feb5a0 into master Oct 2, 2026
5 checks passed
@pk910
pk910 deleted the pk910/frames-devnet-0-fixes-2 branch October 2, 2026 15:06
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.

2 participants