Highlights from the bitcoin developer ecosystem
Hi Insiders. This is Tuma, open-source reporter from the Insider Edition. I spent 10+ hours in open-source developer calls in the Bitcoin ecosystem last week. Here is what caught my eye:
An update on BOLTs specifications.
During the monthly call, on Monday 9th, Lightning developers discussed the latest changes to the BOLTs specifications. In particular, three PRs were merged during the call after the different implementations ACKed the proposed modifications.
Specifically, PR1316 adds an explicit requirement for
offer_amountto be greater than0in BOLT12, PR1312 adds a test vector to fix inconsistencies across Lightning implementation in bech32 padding by rejecting invalid BOLT12 offers according to BIP173 rules, and PR1298 adds another test vector for non-canonical signatures in BOLT11.The next steps will be focused on merging two important PRs , namely PR1160, which will officially include channel splicing in the specifications, and PR995, which will enable simple taproot channels.
A BIPs Update
In the last days there was some movement in the BIP repository. Specifically, 3 new BIPs have been published, BIP128, BIP392, and BIP442, and two new BIPs have been assigned a number by BIP maintainer Murchandamus.
Published BIPs
A list of recently published BIPs
BIP442: OP_PAIRCOMMIT
Authors: Moonsettler, Brandon Black
Publishing Date: March 3rd, 2026
Layer: Consensus (Soft Fork)
BIP442 proposes a new tapscript opcode called OP_PAIRCOMMIT. The new operation would allow to add native support to commit to multiple items together. Basically, during execution the opcode would pop the two top elements from the stack, compute their hash, and push the resulting 32-byte hash back onto the stack. The idea behind the proposal it to facilitate more expressive contracts and improve data availability in Bitcoin scripts.
BIP392: Silent Payments Output Script Descriptor
Authors: Craig Raw
Publishing Date: March 5th, 2026
Layer: Applications
BIP392 specifies a new output script descriptor for silent payments, sp() . The descriptor, proposed by the creator of Sparrow Wallet, provides a standardized way to represent silent payment outputs within the output descriptor framework, enabling wallet interoperability and recovery using existing descriptor-based infrastructure. Iin particular, the new descriptor takes silent payment key material and describes P2TR outputs when combined with the sender’s input public key, as defined in BIP352. Checkout this presentation from Nifty to know more about this!
BIP128: Timelock-Recovery Storage Format
Authors: Oren Z
Publishing Date: February 27th, 2026
Layer: Applications
BIP128 specifies a standard format for storing timelock-recovery plans. The goal of this proposal is to allow users to simply importing these type of plans into services that provide automatic monitoring and execution.
Numbered BIPs
A list of BIPs that recently got assigned a number
BIP449: OP_TWEAKADD
Authors: Jeremy Rubin
Assigned Date: March 5th, 2026
Layer: Consensus (Soft Fork)
PR1944 introduces BIP449, which proposes a new tapscript opcode, called OP_TWEAKADD , which would provide a simple and verifiable way to modify a public key inside a script without revealing private keys or relying on hash locks. While Bitcoin already allows this type of “tweaking”, Rubin’s idea is to make this available at the consensus level. This would enable some interesting features, such as script-level key evolutions without full signature verification, spending conditions, and covenant-like constructions.
BIP448: A Taproot-native (re)bindable transaction proposal
Authors: Gregory Sanders, Antoine Poinsot, Steven Roose
Assigned Date: March 12th, 2026
Layer: Consensus (Soft Fork)
PR1974 introduces BIP448, which proposes to deploy three new opcodes bundled together, namely OP_TEMPLATEHASH (proposed in BIP446, which is part of the same PR), OP_CHECKSIGFROMSTACK, and OP_INTERNALKEY. According to the authors, the proposed opcodes are simple and well-understood and could provide powerful capabilities to improve second layer protocols while minimizing the risk of incurring in unintended behavior.
Other News from the Bitcoin World
Arkade Assets are live on mainnet: Arkade announced on X that their Bitcoin-native assets solution, Arkade Assets, was finally live on mainnet. Arkade Assets allows anyone to issue assets on the Bitcoin chain by embedding data directly into transactions using an
OP_RETURNoutput, without requiring any changes to the Bitcoin protocol.BIP54 is gaining traction: Two weeks ago, we covered the first BIP54 compatible block being mined. Last week, Mara, one of the largest active mining pool, joined the BIP54 movement by mining its first compatible block, at height 940548. It is possible to recognize a BIP54 compatible block by looking at the coinbase transaction
nLocktimefield, which must be set toblockHeight - 1.Bitcoin knowledge for autonomous agents: Spiral grantee Elias Roher created a new knowledge base for Bitcoin and Lightning development ecosystem. This project was specifically designed to be queried by AI agents through Model Context Protocol (MCP) servers for fast and precise lookups.
Preventing Denial-Of-Service: Bruno Garcia, Director of Engineering at Vinteum, announced on X that he was able to find and correct two denial-of-service (DOS) bugs in Floresta, a lightweight and embeddable Bitcoin client. The first vulnerability was linked to a missing size check that could result a large memory allocation with consequent usage of all the available memory. The other bug was related to the rate-limiting mechanism implemented in Floresta, which should check whether a peer is sending more than 10 messaging per second. However, the counter was never incremented, effectively making the mechanism futile.