Skip to content

Route PTC data requests through configured nodes - #433

Open
AntiD2ta wants to merge 2 commits into
gloas-ptc-dutyfrom
gloas-ptc-data-addresses
Open

Route PTC data requests through configured nodes#433
AntiD2ta wants to merge 2 commits into
gloas-ptc-dutyfrom
gloas-ptc-data-addresses

Conversation

@AntiD2ta

@AntiD2ta AntiD2ta commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Use a dedicated payload-attestation-data multiclient and direct top-level fallback.

Files: main.go, util/config.go, clients_test.go, util/config_test.go, docs/configuration.md.


Stack created with GitHub Stacks CLIGive Feedback 💬

@AntiD2ta AntiD2ta self-assigned this Aug 27, 2026
@AntiD2ta
AntiD2ta marked this pull request as ready for review August 27, 2026 15:48
Use a dedicated payload-attestation-data multiclient and direct top-level fallback.

Files: main.go, util/config.go, clients_test.go, util/config_test.go, docs/configuration.md.

Note: gosilent test ./... remains blocked by the existing blockrelay/v1 RelayWrongType error-text expectation under this Go toolchain; this branch has the same failure.
Payload attestation data addresses read their own strategy key directly and
fell straight back to the top-level addresses, skipping the documented
strategies-level default that every other data path honours.  Resolve them
with BeaconNodeAddresses so strategies.beacon-node-addresses applies, and
cover the strategies-level and direct-override cases.

Move the configuration example next to its siblings, note in the startup
comment that unusable payload attestation data addresses do fail startup,
and record the new option in the changelog.
@AntiD2ta
AntiD2ta force-pushed the gloas-ptc-data-addresses branch from fab0442 to a6bd33f Compare August 27, 2026 16:00
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.

1 participant