Sebastian 🟩πŸ₯• (@theStack) profile picture

Passionate about #bitcoin (Core contributor since 2019), nature, OpenBSD, books, bass, beer & chess 🏞️ PGP: 6A8F 9C26 6528 E25A EB1D 7731 C237 1D91 CB71 6EA7

Vienna
Joined March 2009
Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)Photo by Sebastian 🟩πŸ₯• (@theStack)
Sebastian 🟩πŸ₯• retweeted
> On platforms other than Linux, a malicious peer could cause a node to run out of memory by sending TCP urgent (out-of-band) data. A fix for this issue was released in Bitcoin Core versions 29.5, 30.4, 31.2 and 32.1. This is trivial to exploit. If you’re running Bitcoin Core on an affected platform, you should upgrade.
3
7
34
2,608
Sebastian 🟩πŸ₯• retweeted
There sure has been a lot of *talk* about Bitcoin development these last 18 months. Meanwhile, there's been an awful lot of actual development work done. Examples of what Bitcoin Core has been working on throughout this all: - a node that syncs in nearly half the time - a path to 5x faster (SwiftSync) - a new GUI to make running that node easier, maybe even on mobile - a redesigned mempool with better fee bumping and fee estimates - a mining interface so individual miners can build their own block templates (Stratum v2) - a private broadcast so your transactions can't be traced to your IP - a reproducible map of the entire internet for node eclipse attack protection - a better way to relay time-sensitive Lightning and Ark transactions for confirmation - a multisig that's cheaper, more private, and looks like any other payment on-chain (MuSig2) - a private payment address with zero linkable payments (silent payments) - a threshold (e.g. 3-of-5) signature scheme that looks like a single signature (FROST) - a proposal to fix known protocol bugs and current attack vectors (BIP54) - a slew of post-quantum research to be ready for future attack vectors - a first-ever independent security audit for more eyes on the code - a new tool that attacks a live node the way a real adversary would (Fuzzamoto) - a fix that killed an entire class of disk-filling attacks - a replacement for a risky external library - a consensus engine the whole ecosystem can build on (Bitcoin Kernel) Over a hundred contributors and more than a dozen funding organizations around the world. Not without controversy. Not without bugs. But undeniable progress. August will come and go. This work will continue.
36
129
16
449
42,816
2 and 1/2 years, 5 PR takes, 1284 review comments, 1 protocol change and countless force-pushes and CI runs later, we made it to the finish line and the Silent Payments (BIP-352) module has finally landed in libsecp256k1! πŸ€«πŸŽ‰ #1471 β†’ #1519 β†’ #1698 β†’ #1765 πŸβœ…(β†’ #1792 πŸ·οΈβ›”)
7
34
5
152
26,876
Over the years, this effort was driven primarily by BIP-352 author @josibake. Huge kudos! πŸ‘πŸ«‘ Thanks to everyone who helped make this happen, whether through PR reviews or conceptual discussions: @achow101, @andrew_s_toth, antonilol, @brrrunog, @craigraw, Eunovo, @fjahr, furszy,
1
2
1
36
1,881
jlest01, @n1ckler, @LLFOURN, @L0RINC, macgyver13, nymius, @real_or_random, sipa, @provoost, @SomsenRuben, @Sosthene___, @spherostrat, @theuni, w0xlt. πŸ™
1
25
759
Sebastian 🟩πŸ₯• retweeted
We are excited to announce that Martin Zumsande (@lightlike1) has (re)joined Brink to continue his work on Bitcoin Core including P2P networking, validation, testing, and review!
7
14
2
81
8,805
Sebastian 🟩πŸ₯• retweeted
Thanks to all the work done by @fjahr and pinheadz, libevent is no-longer a dependency of Bitcoin Core, This means a minimal bitcoind, now only has a single, header only, external dependency; which is Boost MultiIndex. Work is ongoing to replace this too.
7
28
3
122
11,917
Sebastian 🟩πŸ₯• retweeted
We are excited to announce that conduition (@conduition_io) has joined Brink as cryptographic engineer working on post-quantum cryptographic research and implementation!
6
29
6
111
68,303
Sebastian 🟩πŸ₯• retweeted
Sparrow v2.5.0 released with: Silent Payments (SP) wallets SP-capable Frigate public server @2140_dev bitview.space fee rates source sparrowwallet.com/download
39
226
49
912
319,296
Sebastian 🟩πŸ₯• retweeted
TIL that Pieter Wuille published a libsecp256k1 tutorial. wuille.net/posts/secp256k1-t…
4
48
5
203
10,875
Sebastian 🟩πŸ₯• retweeted
Bitcoin Core v31.0 was released! It is available from: bitcoincore.org/en/download/ Release notes: bitcoincore.org/en/releases/…
164
123
44
463
138,375
Sebastian 🟩πŸ₯• retweeted
BIP376: "Spending Silent Payment Outputs with PSBTs" has been published.
4
19
88
4,876
Sebastian 🟩πŸ₯• retweeted
With an increasing number of discussions around the BIP54 β€œConsensus Cleanup” soft fork proposal, I helped put together an information site about BIP54. β€œBitcoin has four known vulnerabilities that have gone unfixed for 15 years. BIP54, "Consensus Cleanup", proposes four narrowly-scoped changes to address these issues in Bitcoin's consensus rules that date back to the original version of Bitcoin in 2009.” bip54.org/
13
56
5
160
35,795
Sebastian 🟩πŸ₯• retweeted
Silent payments is not just a new approach to static payment codes. It's the first serious contender to improve the address derivation system since HD wallets in 2013. HD wallets were a big win over single keys, and silent payments could be a similar leap forward.
9
118
15
518
35,101
Exploits Replay: Nymius presents on a scanning problem with Silent Payment BIP352 that was discovered 6mo ago and his thoughts on how to discover these kinds of vulnerabilities earlier at @btcplusplus exploits edition in Florianopolis, Brazil this past Feb πŸ‡§πŸ‡·#btcpp
6
10
542
Sebastian 🟩πŸ₯• retweeted
Wie kΓΆnnten wir #Bitcoin quantensicher machen, wie schwer ist das und was brΓ€uchte es dafΓΌr? In unserem Quantengipfel fassen wir den aktuellen Stand mit @n1ckler und @murchandamus zusammen. Doch hΓΆrt am besten selbst! coinspondent.de/2026/03/31/h…
4
12
32
3,356
Sebastian 🟩πŸ₯• retweeted
Today we’re publishing Brink's 2025 Engineering Impact Report covering the work of the eight Bitcoin Core engineers we funded last year and why we think this work is important.
6
29
5
110
33,996
Sebastian 🟩πŸ₯• retweeted
A new release candidate of Bitcoin Core, v31.0rc1, is available for testing. This is a new major release, and follows v30.2. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
104
42
25
161
33,499