Skip to content

[dependency-upgrade] Upgrade kyoto 0.5.0 → 0.6.0#672

Merged
0xsiddharthks merged 1 commit into
mainfrom
siddharth/upgrade-kyoto-0.6
Jun 10, 2026
Merged

[dependency-upgrade] Upgrade kyoto 0.5.0 → 0.6.0#672
0xsiddharthks merged 1 commit into
mainfrom
siddharth/upgrade-kyoto-0.6

Conversation

@0xsiddharthks

@0xsiddharthks 0xsiddharthks commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Upgrades kyoto light client from 0.5.0 → 0.6.0 (latest).

kyoto upgrades:

  • HeaderCheckpointHashCheckpoint — API change only
  • fix(net): Do not disconnect unknown messages — 0.5.0's P2P reader dropped a peer on any unrecognized message (Unknown => Disconnect)

Release PR

TLDR: no significant change for us in this release

Picks up the upstream `fix(net): Do not disconnect unknown messages`:
0.5.0 dropped a peer on any unrecognized P2P message, which with our
`whitelist_only` single-peer setup means NoReachablePeers -> node exit ->
supervision restart. 0.6.0 ignores unknown messages instead, cutting
spurious restarts.

The only breaking API change is the `HeaderCheckpoint` -> `HashCheckpoint`
rename (mechanical, all in btc_monitor). `bitcoin` is already pinned at
0.32.8 to match the new exact pin, so there's no transitive churn.
@0xsiddharthks 0xsiddharthks changed the title [btc-monitor] Upgrade kyoto (bip157) 0.5.0 → 0.6.0 [kyoto-hardening][dependency-upgrade] Upgrade kyoto 0.5.0 → 0.6.0 Jun 7, 2026
@0xsiddharthks 0xsiddharthks marked this pull request as ready for review June 10, 2026 12:59
@0xsiddharthks 0xsiddharthks requested a review from bmwill as a code owner June 10, 2026 12:59
@0xsiddharthks 0xsiddharthks changed the title [kyoto-hardening][dependency-upgrade] Upgrade kyoto 0.5.0 → 0.6.0 [dependency-upgrade] Upgrade kyoto 0.5.0 → 0.6.0 Jun 10, 2026
Comment thread Cargo.toml
corepc-client = { version = "0.10.0", features = ["client-sync"] }
jsonrpc = "0.18.0"
kyoto = { package = "bip157", version = "0.5.0" }
kyoto = { package = "bip157", version = "0.6.0" }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we calling bip157 kyoto?

@0xsiddharthks 0xsiddharthks merged commit aa5e810 into main Jun 10, 2026
14 checks passed
@0xsiddharthks 0xsiddharthks deleted the siddharth/upgrade-kyoto-0.6 branch June 10, 2026 16:30
@dlukegordon dlukegordon restored the siddharth/upgrade-kyoto-0.6 branch June 10, 2026 23:45
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.

2 participants