[guardian] anchor on-chain trust on the enclave build (PCR0), not the ephemeral key#690
Draft
0xsiddharthks wants to merge 1 commit into
Draft
[guardian] anchor on-chain trust on the enclave build (PCR0), not the ephemeral key#6900xsiddharthks wants to merge 1 commit into
0xsiddharthks wants to merge 1 commit into
Conversation
… ephemeral key The committee node pinned the guardian's ephemeral ed25519 key on-chain, so a guardian reboot (which mints a fresh key) broke verification and stalled withdrawals. Replace that anchor with the expected enclave build: - config.move stores guardian_pcr0 + guardian_git_revision instead of guardian_public_key; set_guardian / finish_publish set the build. - update_guardian governance now rotates the build (+ url), enabling committee-governed enclave upgrades. - publish CLI takes --guardian-pcr0 / --guardian-git-revision (optional, all-zero default for non-Nitro dev); the immutable BTC key is unchanged. The node verifies the live ephemeral key against this build via Nitro attestation (a no-op in non-Nitro dev) in a follow-up PR.
This was referenced Jun 18, 2026
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.
The committee node pins the guardian's ephemeral ed25519 key on-chain, so a guardian reboot (fresh key) breaks verification and stalls withdrawals. Anchor on the expected enclave build instead, so Nitro attestation can vouch for a fresh key each boot (the mainnet model).
config.move: storeguardian_pcr0+guardian_git_revisionin place ofguardian_public_key;finish_publishand theupdate_guardiangovernance action set/rotate the build.--guardian-pcr0/--guardian-git-revision, optional with all-zero defaults for non-Nitro dev. BTC key unchanged (required, immutable).onchaingetters for the build; e2e publishes the all-zero placeholder.Node-side attestation verification against this anchor is a follow-up (stacks on #666/#675). Supersedes the ephemeral-key-PVC approach in #668.