Age | Commit message (Collapse) | Author |
|
This fixes an issue in backporting to 0.13 as 0.13 enforces SF
activation by block version lockin instead of through a hard-coded
block height.
Github-Pull: #8916
Rebased-From: a4ad37d4ef4bcd81bc9d867b277efdebc86bc2e8
|
|
Github-Pull: #8916
Rebased-From: 032e883b937a6b70d5c367fc2ee57d7eea8cb473
|
|
Github-Pull: #8904
Rebased-From: 4cdece40419bcc97345357f9268e03b0aff400b5
|
|
Github-Pull: #8393
Rebased-From: 27acfc1d2ee53cc52b54befd2d4bfa24a77a2eef
|
|
sync_with_ping() only guarantees that the node has processed messages
it's received from the peer, not that block announcements from the node have
made it back to the peer. Replace sync_with_ping() with an explicit check that
the node's tip has been announced.
Github-Pull: #8882
Rebased-From: 6976db2f4687d575e1b4bee5aaf1d93a794f23c3
|
|
Also fix a bug in the sync_with_ping() helper function
Github-Pull: #8854
Rebased-From: b5fd666984fdb7125cb809c773b36034f32128cc
|
|
Python lambda use was incorrect.
sendcmpct messages need to be synchronized with RPC calls to generate().
Headers need to be synced (eg with getheaders) for cmpctblock announcements
to start.
Last test omitted sending a sendcmpct message.
Github-Pull: #8739
Rebased-From: 157254a4bfdfc4ca3ad5bf2d84e82f290bd0c7f2)
|
|
Github-Pull: #8418
Rebased-From: 45c7ddd109465e03551f5b39c2e650c243b4a078
|