-
Notifications
You must be signed in to change notification settings - Fork 209
[Access] Fix executor address matching in scheduled tx indexer #8539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
peterargue
wants to merge
3
commits into
master
Choose a base branch
from
peter/scheduled-tx-executor-match
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+164
−24
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: onflow/flow-go
Length of output: 3928
🏁 Script executed:
Repository: onflow/flow-go
Length of output: 2170
🏁 Script executed:
Repository: onflow/flow-go
Length of output: 6130
🏁 Script executed:
Repository: onflow/flow-go
Length of output: 1043
Residual risk is real: ProcessCallbacksTransaction would be misidentified as executor transaction in v0 blocks.
The combination
Payer == EmptyAddress && len(Authorizers) == 1 && Authorizers[0] == executor(height) && len(Arguments) >= 1correctly handlesProcessScheduledTransactionsTransaction(zero args) andSystemChunkTransaction(zero args), and the height-aware executor address correctly maps toFlowServiceAccountin v0 blocks.However,
ProcessCallbacksTransactionin v0 satisfies all four conditions:SetPayer)FlowServiceAccount.AddressexecutorAddr.ByHeight()resolves toFlowServiceAccount.AddressWhen misidentified as an executor transaction, the code attempts to decode
Arguments[0]as a scheduled transaction ID at line 406. SinceProcessCallbacksTransaction's argument is a callback event ID, the decoding fails and aborts block indexing. This is not theoretical: such transactions exist in v0 blocks.A discriminator (e.g., script content comparison) is needed to distinguish executor transactions from
ProcessCallbacksTransaction.🤖 Prompt for AI Agents