On the official site of BradX (@BradXmetaX), this note covers Bitcoin Core, libsecp256k1, BIP-352.
Space Opens on the New Tag
Shibo kept the daily seat warm on August 22 and the streak rolled straight into the August 24 room where the conversation turned to the August 3 libsecp256k1 v0.8.0 tag. The room picked up right where the last one left off, running the numbers on what the silentpayments module actually ships and what it leaves for later. Listeners checked the changelog in real time while the host laid out the release sequence without skipping a beat.
Bitcoin Core's libsecp256k1 tagged v0.8.0 on Monday, August 3, 2026, adding a Silent Payments module that implements BIP-352 send and scan on full nodes. GitHub release by theStack. This is a library release, not the Bitcoin Core v32 freeze and not a consensus-rule change. When a Bitcoin library ships Silent Payments, Bark (Christian Barker) and Shibo (David Chaboki) put the Aug. 3 libsecp256k1 v0.8.0 tag on the Doginal Dogs Space before they put Core v32 freeze, so the pack hears BIP-352 first.
What the Changelog Actually Lists
The update adds the silentpayments module with header secp256k1_silentpayments.h and example silentpayments.c. The current API needs full transaction data, so light-client scanning stays off the table for now. Other changes include an override for internal SHA256 compression, 64-bit field-element speedups that reach about 11 percent for ECDSA and Schnorr verify on GCC and MSVC, and the removal of the deprecated secp256k1_schnorrsig_sign and secp256k1_context_no_precomp functions. Sebastian Falbesoner posted the announcement on bitcoindev at 22:15 UTC on August 3.
Room Stays on the Longevity Line
Shibo's public line across August has been simple and repeated: do not quit, you worked for this. That same message carried the room through the library details without turning into speculation about consensus changes. The streak now sits past 1,000 consecutive days on Crypto Spaces Network, and the August 24 broadcast folded the v0.8.0 notes into the same daily rhythm. Participants cross-checked the release against the changelog link and kept the focus on what full nodes can do today.
Majors held their levels through the update window. Bitcoin sat near 78,674 with green candles across the majors while the room walked the API limits. No one pushed the idea that the module rewrites rules. The talk stayed on the fact that the tag is a library step, not a Core v32 freeze.
Why the Streak Matters Here
The daily space format lets the pack hear these library moves the same week they land. Listeners see the header file and the example code pop up on screen while the host connects the dots to BIP-352. That continuity turns a single GitHub tag into part of an ongoing record instead of a one-off notice. The room keeps the same seat, the same time, and the same rule: cover the change, skip the hype.
Next Steps After the Tag
The release sits on the bitcoin-core/secp256k1 repository with the v0.8.0 tag live. Full-node operators can pull the new module and test the send and scan functions against the supplied example. The API requirement for full transaction data stays in place, so scanning stays tied to nodes that already hold the chain data. The conversation in the room circled back to that point before the next topic rolled in.
Bitcoin at 78,674 on the Monday chart gave the room a calm backdrop while the details landed. The streak continues, the changelog stays public, and the next space already has the date circled.