Repository navigation
Conversation
ORACLE_SIGNING_KEY and ORACLE_INDEX now accept comma separated lists, paired by position, so a single instance can vote on the SubgraphAvailabilityManager with several registered oracle addresses. A single key and index behave as before. - Static config errors (unparsable keys or indexes, count mismatch, duplicates, invalid contract mode) fail at startup before any transaction - Each signer posts its own config to DataEdge; a failing signer is logged and doesn't stop the others - Signers vote concurrently; a run fails only if every signer fails - A voteMany revert during gas estimation is reported as an error instead of being counted as success - Signers share one RPC provider and their logs carry oracle_index - New signer_votes_total and signer_vote_failures_total metrics labeled by oracle_index; denied_subgraphs_total still counts each change once - RewardsManager mode rejects more than one signing key
Maikol
force-pushed
the
feat/multiple-signers
branch
from
October 6, 2026 13:12
3d74ec4 to
15cb7a6
Compare
This branch has not been deployed
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
Allows a single oracle instance to vote on the
SubgraphAvailabilityManagerwith multiple signers, each registered at its own oracle index.ORACLE_SIGNING_KEY/--signing-keyandORACLE_INDEX/--oracle-indexaccept comma separated lists, paired by position. Existing single key / single index configs work unchanged.MultiStateManagersubmits the same votes through every signer. A failing signer doesn't stop the others; the run returns an error after all have run so the next run retries.RewardsManagermode rejects more than one signing key.Testing
MultiStateManager(all signers called, partial failure).0,3:0x69eb1769dc8f71bf0a0f0b5b829d0ef06a70f721625af1c881ca667c4cf4d00e), both indexes voted on two deployments with unavailable files, and together with index 2 reached the execution threshold, flippingisDeniedon the RewardsManager. Ran 55 passes with no errors.🤖 Generated with Claude Code