pull down to refresh

📝 Transcripts - Bitcoin Core Dev meetup (Oct 2025)
558 sats \ 2 comments \ @bitcoin_devs 4 Nov bitcoin

📝 Bitcoin Core Dev Tech Meeting (Oct 2025) — Transcripts Now Live

Last week, many Bitcoin Core developers met in Frankfurt for the bi-annual in-person Dev Tech meetup.
18 unconference-style sessions were held, covering topics like:

  • ASMap
  • Secp256k1 & quantum
  • CISA
  • Cluster mempool
  • Libsha
  • Multiprocess & mining interface
  • Silent Payments
  • MuSig2
  • Fuzz testing
  • Mempool & relay policy
  • Consensus cleanup
    ...and more.

Notes are now fully published on btctranscripts.com:
👉 https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/
(18 transcripts, all searchable & linkable)

Related PR
Schmidty opened the PR to include these in the archive:
https://github.com/bitcointranscripts/bitcointranscripts/pull/593 (merged ✅)

Bitcoin Transcripts unlocks the wisdom, knowledge, and history from Bitcoin tech podcasts, presentations, and other audio-visual media. We make technical Bitcoin knowledge more accessible to learners, builders, and educators.

write
preview
related posts
10 sats \ 0 replies \ @DarthCoin 4 Nov

reply
0 sats \ 0 replies \ @Filiprogrammer 5 Nov
Sphincs+

Size optimized, security level 1: 7.8kb (schnorr 64 bytes)

Since standardization, some optimizations have happened:

Sphincs+C (extra 700-1000 hashes to grind during signing, but verification is better): 6.3kb signature sizes

Source: https://btctranscripts.com/bitcoin-core-dev-tech/2025-10/breaking-secp256k1

Shows you how huge Quantum resistant signatures are. For the same security level, signatures would have to be around 100x larger than today with ECDSA. This would be a big waste of precious block space.

Also quantum computers are far from being practical anyway. They can just about break 21 into its prime factors: 21=3*7. Easily solvable in my head.

reply