Skip to content

Conversation

@alessandromazza98
Copy link
Contributor

@alessandromazza98 alessandromazza98 force-pushed the ale/audit-new-auth-timestamp-check branch from 64b7a9b to 4e6e36a Compare November 14, 2025 16:09
Copy link
Contributor

@0xForerunner 0xForerunner left a comment

Choose a reason for hiding this comment

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

I don't think this fix is required. fn start_publishing is only ever called internally. We should never need to worry about an old authorization being passed in.

@alessandromazza98
Copy link
Contributor Author

I don't think this fix is required. fn start_publishing is only ever called internally. We should never need to worry about an old authorization being passed in.

what do you mean exactly with "internally" here? If I understand correctly, the start_publishing fn is called in the new_payload_job fn that is called by the payload builder service (reth dependency) to start a payload job for the given payload id if not already present.

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.

3 participants