[guardian-proxy] Route provisioning to a standby guardian backend#782
Draft
0xsiddharthks wants to merge 1 commit into
Draft
[guardian-proxy] Route provisioning to a standby guardian backend#7820xsiddharthks wants to merge 1 commit into
0xsiddharthks wants to merge 1 commit into
Conversation
Arming a standby guardian (the #765-#770 lifecycle) runs its KP ceremony while the old guardian still serves nodes — but the proxy had one backend, so the relay and the KP tooling's session pinning could only ever see the ACTIVE guardian, whose info hard-fails the standby prechecks (btc pubkey/limiter/epoch all set). Give the proxy an optional STANDBY_GUARDIAN_URL: the relay (share submissions and its accumulator/session reads) targets it when set, while the node-facing forwarder and wid cache always front the active backend. Unset, the relay provisions the active backend — first-deploy and steady-state behavior are unchanged. KP tooling needs to pin the session it actually submits to, so the relay service gains GetStandbyInfo (its backend's GetGuardianInfo, returned untouched); kp_provision's session pinning and its pre-submit prechecks both move to it. Attestation verification of the response is unchanged.
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
Arming a standby guardian (the #765–#770 lifecycle) runs its KP ceremony while the old guardian still serves nodes — but the proxy had one backend, so the relay and the KP tooling's session pinning could only ever see the ACTIVE guardian, whose info hard-fails the standby prechecks (btc pubkey/limiter/epoch all set).
Changes
STANDBY_GUARDIAN_URL: the relay (share submissions + its session/threshold reads) targets it when set, while the node-facing forwarder and wid cache always front the active backend. Unset, the relay provisions the active backend — first-deploy and steady-state behavior unchanged.GetStandbyInfoonGuardianRelayService: the relay backend'sGetGuardianInfo, returned untouched.kp_provision's session pinning and its pre-submit prechecks both move to it (attestation verification of the response unchanged) — KPs pin exactly the session the relay forwards to.