SATURDAY, MAR28
1. Brink impact, 2. Blockstream maintenance gap, 3. Volatility falling, 4. Privacy mission creep
From Proto and Bitkey - part of the Bitcoin ecosystem at Block, Inc.
1. impact
Brink's 2025 Engineering Impact Report details how eight funded developers strengthened Bitcoin Core's foundational infrastructure through code review, testing, security work, and release management. According to Executive Director Mike Schmidt, Brink engineers collectively submitted over 6,000 review comments on Bitcoin Core pull requests, serving as "a line of defense between a code change and the Bitcoin network." The organization also sponsored the first independent third-party security audit of Bitcoin Core, conducted by Quarkslab over four months, which found no critical, high, or medium-severity issues in peer-to-peer networking, mempool, chain management, or consensus logic. Beyond review, engineers advanced cryptographic tooling in libsecp256k1 for silent payments, MuSig2, and FROST threshold signatures, while contributing to the Bitcoin Kernel project to extract consensus validation logic into a standalone library. One engineer led all seven 2025 Bitcoin Core releases and merged 56% of the project's pull requests. The report illustrates how sustained, unglamorous engineering work underpins the security and reliability of the network's most critical software.
-EDITOR·OP_DAILY2. gap
Blockstream Research has completed a two-and-a-half-year maintenance gap in libsecp256k1-zkp, the cryptographic library that underpins the Liquid Network, Elements, and the company's functionary infrastructure. The library is a fork of libsecp256k1, the same code that powers signature verification for every Bitcoin transaction on the main chain, and extends it with advanced primitives including zero-knowledge proofs, Confidential Transactions, and adaptor signature support. According to the Blockstream team, the update brings zkp fully in sync with upstream libsecp256k1, which itself has received substantial improvements since 2023. Research director Jonas Nick and cryptographic engineer Tim Ruffing, both maintainers of the upstream library, led the effort. "Every Bitcoin transaction you have ever made relies on this library for signature verification," the post notes, placing the stakes in practical terms. The catch-up matters because stale cryptographic dependencies can introduce subtle vulnerabilities or prevent security patches from propagating downstream. For developers building on Liquid or testing privacy-preserving Bitcoin constructions, this removes a significant maintenance burden.
-EDITOR·OP_DAILY3. falling
A new report from Charles Schwab finds that bitcoin's historical volatility dropped to 42% in 2025, roughly half the level it recorded in 2021, and now sits below the volatility readings of some of the largest U.S. technology stocks. According to the report, Tesla posted a 63% historical volatility reading last year, while Nvidia registered 50%, both exceeding bitcoin's figure. Schwab's analysis frames the shift as evidence that bitcoin is maturing as a traded financial asset, moving from a speculative instrument defined by outsized swings to something that behaves more like a major equity instead of a collectable or novelty. The decline in volatility is structurally significant for institutional allocators, many of whom use volatility thresholds as a primary filter for portfolio eligibility. Whether this trend holds as market conditions shift is an open question, but the data point gives compliance and risk teams at traditional financial institutions a more defensible position when evaluating bitcoin exposure.
-EDITOR·OP_DAILY4. creep
A report from 404 Media, highlighted by EFF, documents how automated license plate reader systems are already being used for purposes their vendors publicly disclaim. In December 2025, a Georgia State Patrol officer ticketed a motorcyclist based on footage from a Flock Safety ALPR camera, with the ticket explicitly noting the driver was "holding phone in left hand." The problem: Flock's own published policy states its cameras "cannot be queried to find people and are not used to enforce traffic violations." EFF points out that this is a textbook example of surveillance mission creep, the well-documented pattern where tools deployed for one stated purpose expand into others once the infrastructure is in place. Speed cameras and other traffic enforcement systems have since been connected to Flock's ALPR network through its Partner program. For privacy advocates, the episode illustrates why building out surveillance infrastructure is irreversible in practice. Once installed, the question is not whether the tools will be repurposed but how quickly, and whether any policy boundary will hold.
-EDITOR·OP_DAILYConsider subscribing and sharing OP_Daily with your community.