Hi Insiders. This is Tuma, open-source reporter from the Insider Edition.
In this week update we feature the ongoing effort to migrate LDK from GitHub to a self-hosted instance, after the company banned the Lightning implementation from running CI.
We also cover a new BIP being published, BIP95, which defines a new testnet to replace testnet4, and six new BIPs being assigned a number. In particular, BIP453, provides common terminology for transaction components, BIPs 455, 456, and 457 compose the specifications for the SwiftSync protocol for faster IBD, and BIPs 458 and 459 describe half and full signatureaggregation, an important building block towards CISA.
Finally, we cover some interesting news from the Bitcoin ecosystem. In particular, we present some interviews from Nairobi, mempool(.)space joining the SV2 working group, and some useful information about how to protect yourself during the upcoming forks.
Highlights from the bitcoin developer ecosystem
I spent 10+ hours in open-source developer calls in the Bitcoin ecosystem last week. Here is what caught my eye:
A new repository for LDK is being created to move away from GitHub
During the biweekly call, on Monday 6th, LDK contributors discussed the ongoing effort to migrate their codebases from GitHub to a self-hosted instance on Forgejo, managed by rust-bitcoin.
The decision to migrate to a self-hosted instance was taken after lead developer Matt Corallo denounced on X that GitHub had banned the project from running CI on their project, effectively forcing developers to look for other alternatives.
As of today, developers are focused on migrating rust-lightning. No new PRs can be opened, and the old repository on GitHub remains as a mirror. LDK-node and LDK-server will be the next project to be moved.
A BIPs Update
In the last days there was some movement in the BIP repository. Specifically, one new BIP has been published and six new BIPs have been assigned a number by BIP maintainer Murchandamus.
Published BIPs
A list of recently published BIPs
BIP95: Testnet 5
Authors: Pol Espinasa, Fabian Jahr
Published On: Jun 25th, 2026
Layer: Applications
BIP95 defines a new testnet to replace the current testnet4. The new testnet removes the difficulty
exception defined in the previous iteration, due to its sustained exploitation that has historically made testing difficult. Moreover, testnet5 raises the minimum difficulty and enforces the consensus
rules specified in BIP54 from block 1
Numbered BIPs
A list of BIPs that recently got assigned a number
BIP453: Terminology of Transaction Components
Authors: Murch
Assigned On: Jun 20th, 2026
Type: Informational
PR2195 introduces BIP453, an informational BIP that aims to provide a common terminology for transaction components to be used in Bitcoin-related technical writing and future BIPs.
BIP455: Peer sharing of block spent coins
Authors: Robert Netzke, Ruben Somsen
Assigned On: Jun 22th, 2026
Layer: Peer Services
PR2152 introduces BIP455, the first BIP that composes the specifications for SwiftSync, a protocol for clients to parallelize initial block download (IBD). BIP455 defines how additional data can be shared over the P2P network to allow a client to validate blocks in arbitrary order.
BIP456: Hints for unspent coins
Authors: Robert Netzke, Ruben Somsen
Assigned On: Jun 22th, 2026
Layer: Peer Services
PR2152 introduces BIP456, the second BIP that composes the specifications for SwiftSync. BIP456 defines a representation of the UTXO set to be used as “hint” to verify the correctness of the set of unspent coins that a client arrived at through SwiftSync.
BIP457: SwiftSync initial block download
Authors: Robert Netzke, Ruben Somsen
Assigned On: Jun 22th, 2026
Layer: Applications
PR2152 introduces BIP457, the main BIP that composes the specifications for SwiftSync. BIP457 describes the different components of the protocol and the way it tries to achieve faster IBD through parallelization.
BIP458: Half-Aggregation of BIP 340 Signatures
Authors: Tim Ruffing, Jonas Nick, Fabian Jahr
Assigned On: Jul 2nd, 2026
Layer: Applications
PR2205 introduces BIP458, which describes how to perform half-aggregation of Schnorr signatures, as per BIP340. Half-aggregation is a non-interactive process for aggregating a collection of signatures into a single signature, whose size is approximately half of the combined size of the original signatures. This approach could also be leveraged for signatures in the inputs of Bitcoin transactions, a process known as cross-input signature aggregation (CISA).
BIP459: Full-Aggregation of BIP 340 Signatures
Authors: Fabian Jahr
Assigned On: Jul 10th, 2026
Layer: Applications
PR2210 introduces BIP459, which describes full-aggregation of Schnorr signatures, as per BIP340, a standard for Discrete Logarithm-Based Interactive Aggregate Signatures (DahLIAS) interactive aggregate signature scheme. Full-aggregation is an interactive process for aggregating a certain number of signatures into a single one, whose final size is the same as a single BIP 340 signature (64 bytes), regardless of the number of signers.
One of the most interesting applications of this BIP is CISA. However, the author notes that this would require a consensus change, which is outside of the scope of this proposal.
Other News from the Bitcoin World
Voices from Nairobi: Check out our interviews with Alex Gleason and M. K. Fain (Team Soapbox) and Sharon Murugi (Btrust) from Bitcoin++ Open-source Edition in Nairobi. Stay tuned for more!
Mempool <> Stratum V2: The Stratum V2 project recently announced that mempool.space had joined the SV2 working group. The goal is to standardize how miners who build their own block templates leave their mark on blocks in an open format, so that block explorer can read and present them.
Fork season: with two possible forks happening in the next months, bitcoin holders should be aware of the risks they could be facing. Murch wrote an extensive blog post on replay attacks, Robin Linus provided information on the same topic, and Calle warned against attacks on privacy and risk of leaking private keys. Check them out to be ready for what is coming!
Looking for an opportunity to join up with some bitcoin devs in person? Join us in Toronto this July 22- 24 to talk about finding consensus in Bitcoin!