Skip to content

[btc-monitor] Never rotate the trusted peer connection on a timer#676

Draft
0xsiddharthks wants to merge 1 commit into
mainfrom
siddharth/btc-monitor-max-connection-time
Draft

[btc-monitor] Never rotate the trusted peer connection on a timer#676
0xsiddharthks wants to merge 1 commit into
mainfrom
siddharth/btc-monitor-max-connection-time

Conversation

@0xsiddharthks

Copy link
Copy Markdown
Contributor

Kyoto's default max_connection_time silently ends every peer connection after 2 hours, and with whitelist_only each rotation consumes a whitelist entry — so each node's kyoto died with NoReachablePeers every ~4 hours like clockwork (devnet's 240-minute restart metronome, 54 exits in 48h) and paid a full resync. Our peers are our own trusted bitcoin-core nodes, so never rotate them on a timer.

Pairs with sui-operations#8134; upstream kyoto fixes for the remaining disconnect causes (whitelist retry, inv deafness) are in flight.

Kyoto's default max_connection_time silently ends every connection
after 2h, and with whitelist_only each rotation consumes a whitelist
entry: the node exits with NoReachablePeers every ~4h like clockwork
(the 240-minute restart metronome on devnet) and pays a full resync.
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