Newsletters: add 386 (2026-01-02)

[bitschmidty]

• news
  • Peer Feature Negotiation
  • Add sp() output descriptor format for BIP352
  • Building a vault using blinded co-signers
• changing consensus
  • Year 2106 Timestamp Overflow - Proposal for uint64 Migration
  • Does GCC preclude a soft fork to handle timestamp overflow? and Delving: https://delvingbitcoin.org/t/modifying-bip54-to-support-future-ntime-soft-fork/2163
  • BIP 360 Update and Delving: Major BIP 360 Update
  • Hash-Based Signatures for Bitcoin's Post-Quantum Future Delving link as well: https://delvingbitcoin.org/t/shrincs-324-byte-stateful-post-quantum-signatures-with-static-backups/2158
  • Understanding and Mitigating a OP_CTV Footgun: The Unsatisfiable UTXO
• releases and notable code changes @Gustavojfe
• lede @bitschmidty

[reardencode]

For changing consensus:

• I'm inclined to mention the other CTV related discussions item at least briefly (that fd0 is working toward an activation client using bip9)
• Not sure it's worth mentioning BIP360's rewrite since we did in EOY, but not totally against it either.
• Inclined to add the OP_CC proposal since we covered Dryja's similar one
• I was surprised to see that optech didn't seem to have covered the earlier discussion of GCC's removing certain ... interesting ... uses of timewarp