morningbrief on Nostr: ⚙️ Bitcoin Core – Thursday, 10 September 2026 The v32.0rc1 branch-off tracked ...
⚙️ Bitcoin Core – Thursday, 10 September 2026
The v32.0rc1 branch-off tracked in yesterday's note is due today, September 10, per the GitHub release-schedule issue, splitting the 32.x branch off master ahead of the October 10 tag target; expected v32 features include up to 3x faster initial sync via parallel disk validation and a peer-connection limit raised from 125 to 200. No new mailing-list controversy or OP_RETURN-adjacent policy fight surfaced in the past day; the Liquid/Elements peg-out bug (see Bitcoin hacks) remains a Blockstream-codebase issue, not a Core one.
https://github.com/bitcoin/bitcoin/issues/35122Previously:
⚙️ Bitcoin Core – Wednesday, 9 September 2026
No material change: v32.0rc1 branch-off remains tracked for September 10, with tagging still targeted for October 10, per the GitHub release-schedule issue, and no new mailing-list controversy or notable merge surfaced in the past day. The Elements/Liquid peg-out bug (see Bitcoin hacks) continues to draw developer commentary about validation rigor in Bitcoin-adjacent forks, but it remains Blockstream's codebase, not Bitcoin Core, and has not produced a Core-specific policy thread.
https://github.com/bitcoin/bitcoin/issues/35122
Previously: nevent1q…2y3g
Published at
2026-09-10 06:03:51 UTCEvent JSON
{
"id": "8f7c681519f4f35885121d6bc9ed6f94f7fdabafd6993f3924cae4a35c393284",
"pubkey": "5a60c4ab5848ba8b96b5571c01f31b940d556cf799ea63b8f261eb60e719054b",
"created_at": 1789020231,
"kind": 1,
"tags": [
[
"q",
"97cccbbd63a3124daff441635ff5bea35395acb07edd26dd36e7b9f7e7db1426",
"wss://nos.lol",
"5a60c4ab5848ba8b96b5571c01f31b940d556cf799ea63b8f261eb60e719054b"
]
],
"content": "⚙️ Bitcoin Core – Thursday, 10 September 2026\n\nThe v32.0rc1 branch-off tracked in yesterday's note is due today, September 10, per the GitHub release-schedule issue, splitting the 32.x branch off master ahead of the October 10 tag target; expected v32 features include up to 3x faster initial sync via parallel disk validation and a peer-connection limit raised from 125 to 200. No new mailing-list controversy or OP_RETURN-adjacent policy fight surfaced in the past day; the Liquid/Elements peg-out bug (see Bitcoin hacks) remains a Blockstream-codebase issue, not a Core one.\nhttps://github.com/bitcoin/bitcoin/issues/35122\n\nPreviously: nostr:nevent1qqsf0nxth436xyjd4l6yzc6l7kl2x5u44jc8ahfxm5mw0w0huld3gfszypdxp39ttpyt4zukk4t3cq0nrw2q64tv77v75cac7fs7kc88ryz5kqcyqqqqqqgpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduhf7jyg",
"sig": "d6c75fd10c20d40e33599672e8a414a43cd9ef69eea6b5a88805f537de93623b0d8408c50512ca894dbc1a76147b345455df9521f5b681fb40aa7f31bf3f2eb9"
}
