Repository navigation
Revert "rotate publisher key: io.pilot.wallet (#528)" - #530
Merged
Merged
Conversation
The rotated pin only works once the wallet 0.4.0 entry (signed with the new key) is live. That entry is on hold: pilotctl v1.13.0-v1.13.9 delete an app's state on upgrade, so the hourly upgrade --all would delete 0.3.3 wallets' EVM keys. Until then the new pin makes every daemon refuse the installed 0.3.3 wallets (signed with the old key) and fails new installs. This restores the previous catalogue and signature byte for byte. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Restores the catalogue and its signature byte for byte to their state before #528.
#528 re-pinned
io.pilot.walletto a new publisher key, to be followed straight away by the 0.4.0 entry signed with that key (#529). #529 is on hold: pilotctl v1.13.0–v1.13.9 delete an app's state onupgrade(state carry-forward arrived in v1.13.10, #467), so the hourlyupgrade --allon those nodes would delete 0.3.3 wallets' EVM keys. That is tested, not inferred.With the new pin and no 0.4.0 entry, every daemon refuses the installed 0.3.3 wallets (signed with the old key) at its next pin refresh, and new installs fail. This puts the old pin back.
🤖 Generated with Claude Code