Tracking P2P Alerts

[doitian]

• Alert 20230001 Tracking P2P Alerts #3800 (comment)
• Alert 20230002 Tracking P2P Alerts #3800 (comment)

[doitian]

Alert 20230001

Yank ckb v0.105.*

{
  "id": "0x134af71",
  "cancel": "0x0",
  "min_version": "0.105.0-pre",
  "max_version": "0.105.1",
  "priority": "0x14",
  "notice_until": "0x18785a51000",
  "message": "CKB v0.105.* have bugs. Please upgrade to the latest version.",
  "signatures": [
    "0x8dca283684ff3cd024bd6a67efb24617e90e31dc69ac809ac6ac5e243a57b7aa6711228dfbd8a5cc89a68d3065b685e5c56c70740e8d3487fd538dc914d0c97c00",
    "0x4554b37824e17ea02432507e372c869301a415bf718e0a5a33b6df75cd32fbab7cf8176ca8b079c28266ce1f33c3f61fbff19e27be2a85f5a14faa2b1b474e0a01"
  ]
}

alert message hash: 0xa87c9d43fdf299a89fc12cf1a0e1628e2e9a6d643c760fc25c66ebd1992f3b1f

Collecting Signatures

• @doitian
• @quake

[Keith-CY]

We are hosting a v0.106.* ckb node, and also get this message, is it by design?

Ref: Magickbase/ckb-explorer-public-issues#166

[doitian]

We are hosting a v0.106.* ckb node, and also get this message, is it by design?

Ref: Magickbase/ckb-explorer-public-issues#166

See #3802

Workarounds:

• Upgrade to v0.107.0 (to be released on Jan 28th), or
• Client filters the alerts in get_blockchain_info to see whether the min_version and max_version matches the current node version.

[doitian]

Alert 20230002

Testnet upgrade notice for the hardfork ckb2023

{
  "id": "0x134af72",
  "cancel": "0x0",
  "min_version": "0.0.1",
  "max_version": "0.110.0",
  "priority": "0x14",
  "notice_until": "TBD",
  "message": "TBD",
  "signatures": [
  ]
}

alert message hash: TBD

Collecting Signatures

• TBD
• TBD