In Brief
Ten threads before the headline decks: Core security, node sync, wallet performance, project process, Loupe findings, funding, privacy, local policy, network measurement, and a markets story on Strategy's STRC.
PRIVATEBROADCAST
Bitcoin Core v31.1rc1 is led by a private-broadcast IP-leak fix and the disclosure-handling story around it.
P2P UTXO SHARING
BIP-452 proposes moving AssumeUTXO snapshots peer-to-peer, with new messages and a UTXO-set Merkle-root check.
WALLET / DEPS
Branch-and-Bound coin selection, libevent removal, RBF signalling, assumevalid compaction, and secp256k1 performance work.
CORE PROCESS
bitcoin-core/meta#46 asks when external conduct should affect repository access. Treat it as governance, not code review.
PROJECT LOUPE
LDK v0.2.3 ships a cluster of Loupe-reported DoS, panic, graph-limit and interop fixes.
FUNDING
Maelstrom annual report (privacy-weighted grantees); OpenSats LTS for Utreexo's Calvin Kim; Brink's Hornet and Bedrock testing tools.
PRIVACY
Marmot v2 specs (deterministic group state, transport-agnostic); Payjoin to Cashu via CDK PR2049 and BIP77.
SELF-CUSTODY
AUSTRAC Travel Rule starts 1 July; Bitaroo opts out of info-sharing via its SHAZAM system; libssh2 RCE; Ledger physical-mail seed scam.
NETWORK
b10c outbound connection-success-rate measurements; the first ASmap build-quality dashboard.
MARKETS / STRC
Strategy's STRC preferred fell below its $100 par, pausing at-the-market share sales and prompting a first Bitcoin sale since 2022; debate over dividend sustainability.
Privatebroadcast IP Leak
The July Core release story is not a feature launch. It is a privacy bug in a privacy feature.
THE BUG
-privatebroadcast is supposed to keep transaction broadcast away from clearnet identity leakage. The v31.1 release candidate is led by a fix for a path that could reveal a clearnet IP.WHY IT MATTERS
Broadcast privacy is fragile because the failure is metadata, not a bad signature or invalid block. Users usually cannot detect the leak after the fact.
RELEASE SHAPE
The rc also carries validation, P2P, wallet, MuSig empty-pubkey rejection, and Boost compatibility fixes, but the privacy disclosure is the reason to pay attention.
ROOM QUESTION
How should wallets and node operators talk about experimental privacy features when the fallback behaviour can reveal exactly what the feature was meant to hide?
P2P UTXO Set Sharing
BIP-452 is about making AssumeUTXO easier to obtain without trusting a website, torrent, or one-off download.
ASSUMEUTXO
AssumeUTXO lets a node start from a signed UTXO-set snapshot at a known block height, become useful quickly, then verify historical blocks in the background.
THE PROPOSAL
Fabian Jahr's BIP-452 moves snapshot distribution into Bitcoin P2P: a service bit, four new messages, chunk transfer, and a UTXO-set Merkle root for verification.
WHY IT HELPS
If it works, a new node can get the same fast-start benefit from peers instead of needing an out-of-band snapshot source.
OPEN RISK
Antoine Riard flagged CPU-asymmetric DoS risk from malleated chunks. Sjors also asks whether UTXO commitments are worth it if the only goal is faster IBD.
Wallet And Dependencies
This is the unglamorous performance and dependency work that makes normal node and wallet operation less brittle.
BRANCH AND BOUND
Murch's coin-selection rewrite skips already-visited input sets, so the wallet can explore more useful combinations within the same iteration budget.
LIBEVENT REMOVAL
Core's HTTP/RPC server moves from libevent to an in-tree implementation, reducing an external dependency in a high-value process surface.
IBD PERFORMANCE
LevelDB compaction at the assumevalid boundary targets a real sync bottleneck, especially on HDDs, where the packet cites roughly 15% IBD speedup.
SIGNATURE PATH
A secp256k1 int128 force-inline change is another small performance win in validation. These are not headline changes, but they compound.
RBF FINGERPRINTING
The wallet RBF-signalling discussion moved away from MAX-1 after data showed MAX-2 is already common enough to be the lower-fingerprint choice.
Core Process
bitcoin-core/meta#46 is not about a patch. It is about what repository access means when conflict happens outside the repository.
THE QUESTION
Should Bitcoin Core ban or restrict contributors for external conduct if their in-repository behaviour and patches are otherwise reviewable?
ONE SIDE
Murch argues a ban can be in order when someone publicly accuses the project of crimes for years without evidence, because that damages the project and contributors.
THE OTHER SIDE
stickies-v argues refusing technically good patches over out-of-repo conduct is unworkable and risks turning access decisions into social enforcement.
WHY IT BELONGS HERE
Open-source governance is infrastructure. Repository access, maintainer discretion, and contributor trust shape what code gets reviewed and merged.
Project Loupe
LDK v0.2.3 is the useful item here: a security-heavy release driven by systematic vulnerability finding.
WHAT SHIPPED
LDK v0.2.3 includes roughly a dozen DoS and panic fixes, with many reports attributed to Project Loupe.
BUG CLUSTER
Examples from the packet: Bolt11 pubkey-recovery panic, LSPSDateTime pre-1970 panic, HashDoS, and rapid-gossip-sync graph-size limiting.
CORRECTNESS
The release also fixes an MPP-claim race with async monitor updates, which is not just a crash story. It is channel-state correctness under real async conditions.
INTEROP
PR #4647 generates blinded paths so LND peers stop refusing BOLT12 onion messages. That is the kind of boring interop fix that makes specs usable.
TAKEAWAY
Loupe is interesting because it makes the maintenance burden visible: Lightning libraries need adversarial inputs, fuzzing-style attention, and cross-implementation feedback.
Funding And Tooling
A month of grants and testing infrastructure, with privacy and verification work heavily represented.
MAELSTROM
First annual grant report highlights rkrux, stratospher, benalleng and macgyver13, with two of four grantees now full-time on privacy work.
OPENSATS
Long-term support for Calvin Kim keeps Utreexo moving: accumulator work aimed at making fully validating nodes cheaper to run and sync.
BRINK
Hornet and Bedrock both sit in the testing stack: executable consensus specification, differential testing against Core, and deterministic low-level test environments.
MAINTAINER LOAD
Btrust's open-source hackathon included contribution-spam tooling, a useful signal that AI-assisted low-quality PRs are now a maintainer-workload problem.
Privacy Plumbing
The interesting movement is mostly protocol plumbing: group state, payjoin, Cashu, and transport choices.
MARMOT v2
Specs move toward deterministic group-state consensus with hard-coded parameters, so members cannot silently fork the group by choosing different settings.
TRANSPORT-AGNOSTIC
Marmot also becomes less tied to any single transport. That matters if private coordination protocols need to survive Nostr, relay, or messaging churn.
PAYJOIN TO CASHU
CDK PR2049 builds toward Payjoin-to-Cashu using BIP77 async payjoin: the receiver contributes a UTXO, breaking the common-input heuristic.
QUESTION
Which privacy work is closest to normal wallet UX: better coinjoins, payjoin, ecash, silent payments, or messaging-layer coordination?
Self-Custody And Local Policy
The Australian Travel Rule deadline is local; the rest is the usual warning that self-custody also means operational hygiene.
AUSTRAC
The Travel Rule starts 1 July for Australian VASPs: originator and beneficiary information, counterparty due diligence, and risk-based self-hosted-wallet policy.
BITAROO SHAZAM
Bitaroo says it will avoid Travel Rule information-sharing through its SHAZAM system. The mechanism is undisclosed, so this is a discussion hook, not a conclusion.
libssh2 RCE
Client-side RCE via a malicious SSH server affects tooling people actually use: Git, curl, SCP clients and firmware updaters can all sit near key material.
LEDGER MAIL SCAM
Physical letters posing as firmware-update notices used QR codes to harvest seeds, reportedly drawing on address data from the old Ledger breach.
Network Operations
The useful part is measurement: how reachable peers actually are, and whether ASmap data is getting better.
OUTBOUND SUCCESS
b10c's measurements show IPv4 outbound success rates remain low, while Tor, I2P and IPv6 look healthier. Reachability is still uneven by network.
V2 TRANSPORT
Most outbound attempts now target v2-transport-capable nodes, but downgrades still happen. That is progress, with a real deployment tail.
ASmap DASHBOARD
The first ASmap build-quality dashboard makes drift and match quality inspectable instead of burying it in generated data files.
WHY CARE
Peer diversity, eclipse resistance, and transport privacy all depend on boring network facts. Dashboards and crawlers beat vibes.
Strategy's STRC Falls Below Par
A markets story rather than a protocol one: Strategy's newest preferred stock is meant to sit at $100, and through June it did not.
WHAT STRC IS
STRC ("Stretch") is a perpetual preferred stock Strategy (MSTR) launched in July 2025 to help fund its Bitcoin purchases. Its dividend rate is reset on a monthly cadence to keep the price near its $100 par.
BELOW PAR
Through June 2026 STRC traded well under par, closing around $89 on 18 June and near $73 by late June. Because it is below par, Strategy paused its at-the-market share sales, removing a lever it uses to keep buying Bitcoin.
THE DIVIDEND SQUEEZE
Strategy held the stated rate at 11.50% for a fourth month while the effective yield climbed toward 15%. Markets expect a rise to 12-12.5%, and Strive's competing SATA preferred pays 13%.
THE SALE THAT RATTLED THE MARKET
To fund STRC distributions, Strategy disclosed on 1 June that it sold 32 BTC (~$2.5M) in late May, its first Bitcoin sale since 2022, against Michael Saylor's long-stated pledge never to sell. It has also built a $1.1B dollar reserve for preferred dividends and debt.
THE DEBATE
Critics argue the preferred dividends are funded by new share sales or Bitcoin sales rather than operating cash flow, calling the structure circular or Ponzi-like. Strategy and its supporters read the held rate as stable demand and point to the rate-reset mechanism and the dollar reserve as the design working as intended.
STRC's price is volatile and its rate resets monthly; these are late-June figures, re-verify at meeting time.
Discussion
Pick the thread that should not stay a roundup item next month.
QUESTION
Which bucket deserves a real deck next month: Core process, Loupe-style library hardening, privacy plumbing, or local compliance?
STRATEGY / STRC
Is STRC a Bitcoin story or a markets story? Does a treasury company selling BTC to fund preferred dividends create network-level risk, or does it stay with its own shareholders?
OPEN ISSUE
The Travel Rule deadline lands the day before the meetup; the SHAZAM mechanism is undisclosed, so verify before drawing conclusions.