Skip to content

submit io.pilot.wallet v0.4.1 - #134

Merged
TeoSlayer merged 1 commit into
mainfrom
submit/io.pilot.wallet-0.4.1
Oct 8, 2026
Merged

TeoSlayer merged 1 commit into
mainfrom
submit/io.pilot.wallet-0.4.1

Conversation

@TeoSlayer

Copy link
Copy Markdown
Contributor

Wallet 0.4.1: the four bundles from pilot-protocol/wallet v0.4.1, for darwin and linux on amd64 and arm64. It replaces the 0.4.0 submission (#131), which never reached the catalogue.

Why 0.4.1

pilotctl v1.13.0–v1.13.9 delete an app's dir on upgrade, and the updater runs upgrade --all every hour. Publishing 0.4.0 would have deleted 0.3.3 wallets' EVM keys on those nodes, so its catalogue PR (pilotprotocol#529) was closed.

0.4.1's manifest declares identity.verify (wallet#50). Those pilotctl versions don't know that capability, so they refuse the upgrade and leave the key on disk. pilotctl v1.13.10 and later carry the state forward and accept it. Validating it here needs app-store v1.0.7 (#133).

What changes for users

  • The wallet keeps its keys. It keeps a copy of both identity files outside the install dir. It restores a missing one instead of creating a new key, and it refuses to create a key while any copy exists.
  • Exits when its daemon dies, wallet.help lists every method, plus spend-cap and Base Sepolia fixes. The full changelog is in metadata.json.

Publisher key

The bundles are signed with the rotated key ed25519:xAD0ai5G…, which is pinned in the live catalogue (pilotprotocol#531, signed with the catalogue key).

Checked before opening

  • pilot-app verify (app-store v1.0.7) passes on all four bundles, and verify-update passes against the live catalogue.
  • The tarballs are byte-identical to the release assets.
  • Each binary's format matches its platform.
  • The released darwin-arm64 binary and manifest went through install 0.3.3 → upgrade → uninstall → reinstall, with 0.3.3 and 0.4.1 signed by different keys:
    • pilotctl v1.11.2 and v1.12.3 have no upgrade;
    • v1.13.0, v1.13.5 and v1.13.9 refuse, and the key stays intact;
    • v1.13.10, v1.17.0 and main keep the same key throughout.

After merge

publish-on-merge opens the catalogue PR, signed with CATALOG_SIGN_KEY. The wallet is stateful, so that PR needs an approved_bumps entry.

🤖 Generated with Claude Code

Replaces 0.4.0, which was never in the catalogue: pilotctl v1.13.0-v1.13.9
would have deleted 0.3.3 wallets' EVM keys while upgrading to it. 0.4.1's
manifest declares identity.verify, which those versions do not know, so
they refuse the upgrade and the key stays (pilot-protocol/wallet#50).
The four bundles are the wallet v0.4.1 release assets, signed with the
rotated publisher key.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@TeoSlayer
TeoSlayer merged commit 25db519 into main Oct 8, 2026
10 of 11 checks passed
@TeoSlayer
TeoSlayer deleted the submit/io.pilot.wallet-0.4.1 branch October 8, 2026 15:07
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