All Activity

The latest release of Bitcoin Inquisition, version 29.2, is now available for download at GitHub. This version builds upon Bitcoin Core 29.3rc2 and introduces support for several proposed consensus changes aimed at enhancing the protocol's functionality and security.

The discussion focuses on the complex dynamics within Bitcoin's operation, particularly concerning how package relay, Child Pays for Parent (CPFP), ancestor limits, and block assembly interact to impact transaction inclusion and block utilization. A conceptual framework is proposed to shed light on the economic incentives and marginal trade-offs that guide miners in constructing blocks.

In recent developments regarding the Silent Payments module for libsecp256k1, it has been identified that the scanning method proposed in BIP-352 exhibits significant performance issues, particularly with transactions designed to be adversarial. This problem is notably prevalent when the transaction involves a large number of recipients sharing the same scan public key.

The academic paper titled "Market Power and the Bitcoin Protocol" challenges the conventional wisdom surrounding Bitcoin miners' behavior by suggesting that miners may intentionally forgo potential transaction fees in the short term as part of a strategic decision to influence average transaction fees over time. This perspective introduces the notion that miners engage in complex economic interactions within the Bitcoin network, potentially sacrificing immediate gains for higher future returns.

The exploration of cryptocurrency transactions, particularly within the context of the Mara slipstream and Bitcoin Improvement Proposal 347 (BIP-347), reveals the complexities and technical intricacies involved in executing and validating transactions on blockchain networks. The specific focus on a transaction attempting to navigate through the Mara slipstream network underscores the importance of adhering to protocol standards, including encoded instructions and the precision required for their formulation.

A novel approach to creating a quantum-secure vault through a simple secret-reveal scheme is being discussed, emphasizing its resistance to quantum attacks without the need for new signature schemes or cryptographic libraries. The scheme utilizes covenant-protected vaults with depth-locks, leveraging OP_CHECKTEMPLATEVERIFY (OP_CTV) as outlined in BIP119 and OP_TXHASH / OP_CHECKTXHASHVERIFY from current draft proposals.

The latest version of libsecp256k1, version 0.7.1, has been officially released and is now available for download and use. This new release focuses on several key areas to enhance its functionality and security.

The recent advancements in Bitcoin's authorization policies mark a significant step towards enhancing transaction validation processes. By integrating complex boolean logic, this novel approach surpasses the limitations of traditional threshold/multisignatures and scripts, offering a more nuanced control over Bitcoin spending without compromising privacy or efficiency.

The conversation around "dust attack" UTXOs in on-chain wallets highlights a significant security and privacy challenge within the cryptocurrency space. Dust attacks involve sending small amounts of cryptocurrency to various addresses with the intent to compromise privacy by linking unrelated UTXOs when they are spent together.

The concept of "Digital Latin" analogizes the Bitcoin Layer 1 protocol to Latin, emphasizing its need to become a fixed, immutable foundation resistant to changes. This comparison is drawn from the characteristic stability of dead languages, which, unlike living languages, do not undergo semantic drift.

In a recent exploration of the advancements in BitVm flavors, attention was drawn to the foundational cryptographic primitive known as "garbled circuits". This concept is pivotal for facilitating secure multi-party games between distrustful parties, offering a framework to model channel jamming within blockchain technology as a multi-party game involving entities like Alice, Bob, and Caroll.

The exploration of off-chain cryptography has led to more advanced and expressive smart contracts within the Bitcoin ecosystem. Innovations such as BitVM have introduced the use of SNARKs (Succinct Non-Interactive Arguments of Knowledge) to facilitate the proof of arbitrary computation, alongside garbled circuits which allow for the verification of these proofs to be efficiently moved off-chain.

A recent development shared on the Bitcoin Development Mailing List highlights the technical demonstration of integrating the Falcon post-quantum signature scheme into Bitcoin Core. This integration, implemented as a soft fork within the classic Pay to Witness Public Key Hash (P2WPKH) mode, serves as a practical reference for future consideration of Falcon's adoption, especially as it nears FIPS standardization.

Programming Lightning is an educational initiative aimed at providing developers and technically inclined individuals with a hands-on understanding of the Lightning network. This project, supported by grants from Spiral and HRF, draws inspiration from "Programming Bitcoin" and strives to teach the inner workings of Lightning through practical coding exercises.

The security foundation of Bitcoin is significantly anchored in its use of elliptic curve cryptography. This cryptographic technique ensures the generation of Bitcoin signatures with private keys while safeguarding against the reverse engineering of these private keys from public keys, a task deemed nearly impossible with conventional computing power.

The recent modifications to the Bitcoin Core code have sparked considerable interest within the development community, particularly concerning the testnet4 adjustments. These changes are aimed at addressing an issue identified with the testnet4, where after block 150,000, the minimum difficulty rule is disabled.

The ongoing development of a Bitcoin Improvement Proposal (BIP) focuses on introducing changes to enhance spending silent payment outputs. This effort is documented through a GitHub gist and a mailing list post, both of which provide comprehensive details about the proposed modifications.

A recent scholarly paper published on arXiv provides a comprehensive geometric framework aimed at understanding several phenomena observed in payment channel networks, with a particular focus on the Lightning Network. This study revisits well-known challenges such as channel depletion and capital inefficiency in two-party channels while introducing a unified structural explanation that encompasses these issues.

The recent discussions delve into the complexities of managing blockchain transactions, specifically focusing on Silent Payments and their integration with Nostr for notification purposes. The concept of Silent Payments introduces a non-interactive way to receive payments, where the transaction details are known only to the sender, necessitating an efficient method for notifying the receiver about incoming transactions.

The Quantum‑Resistant Address Migration Protocol (QRAMP) introduces an innovative approach to enhance blockchain security against quantum threats by incorporating a two-phase commit and spend flow for legacy Unspent Transaction Outputs (UTXOs). This protocol design is aimed at allowing these UTXOs to remain spendable even after the activation of quantum-resistant mechanisms, effectively placing them in a quarantine mode.

The Hornet UTXO(1) database represents a significant leap forward in Bitcoin client technology, specifically designed to enhance consensus validation efficiency. Developed as part of the experimental Hornet Node project, this new database is built from the ground up using modern C++ for maximum parallelism, achieving remarkable improvements in throughput for Bitcoin consensus validation processes.

The latest release of Bitcoin Core, version v30.2, is now officially available for download from Bitcoin Core's website. This update brings with it a host of new features, various bug fixes, performance improvements, and updated translations.

The discussion revolves around a proposed change in the default encryption algorithm from AES-GCM to CHACHA20. The suggestion emphasizes the significance of integrating this change into the core, highlighting the advantage of not needing to introduce new dependencies solely for this purpose.

The blog post focuses on a significant update to the analysis of miner revenue changes in relation to block propagation time within the Bitcoin network. Originally, the study depicted how each miner's share of total blocks found varied with block propagation times, using absolute values presented as percentages.

The recent announcement of Bitcoin Core version v30.2rc1 marks a significant update, available for download at bitcoincore.org. This new release encompasses an array of enhancements including fresh features, numerous bug fixes, and performance improvements, alongside updated translations.

Mutation testing serves as a crucial technique in software testing, aiming to evaluate the effectiveness of test suites by introducing mutants into the source code and observing if existing tests can detect these changes. In the context of Bitcoin Core, a weekly mutation testing cycle is conducted on the master branch, where mutants are generated and assessed through unit, functional, and fuzz testing.

The email highlights a resource pertinent to cryptography but not exclusively centered on Bitcoin, directing attention to Joy of Cryptography. This reference serves as an additional tool for those interested in the broader field of cryptography, offering insights and information beyond the specific realm of Bitcoin.

The recent discussions and developments within the Bitcoin community, particularly on the Bitcoin Development Mailing List, have highlighted critical challenges and proposed solutions regarding transaction fees and network policies. Matt initiated a conversation emphasizing the difficulties users face due to discrepancies in minrelaytxfee and incrementalrelayfee settings across nodes.

The discourse regarding the adoption of Bitcoin Improvement Proposal 3 (BIP 3) within the Bitcoin community has been a focal point of recent discussions. Initially, the proposal received significant support from community members, with notable figures expressing their backing.

The introduction of Bithoven marks a significant step in smart contract language development, aiming to merge the structured correctness inherent in Miniscript with a more intuitive, imperative control flow syntax reminiscent of languages like C. This move is designed to facilitate ease of use for developers while adhering to the stringent safety requirements critical for Bitcoin Script operations. The primary objective here is to enable the creation of code that is both safe and optimized without compromising on the familiar control structures developers are accustomed to.

A significant issue has been identified in Bitcoin Core versions 30.0 and 30.1, where a bug related to wallet migration could lead to the deletion of all files in the wallet directory under certain conditions, potentially causing a loss of funds. This problem arises specifically during the failure of migrating a wallet.dat file.

The discourse elaborates on the potential and challenges of scaling Bitcoin payments through the Lightning Network, particularly focusing on the network's structural limitations due to its reliance on liquidity availability. It introduces a novel solution named Ark, which aims to address these limitations by facilitating multi-party state updates and utilizing virtual UTXOs (vTXOs) managed by an Ark Service Provider (ASP).

Nic's discussion focuses on the norms surrounding unpaid exploratory work in the context of open-source funding models, particularly within the Bitcoin ecosystem. He notes a common expectation among grant administrators that preliminary work, including project outlining and scoping, should be carried out without compensation.

The draft BIP titled Safe Redaction, proposed for community feedback, aims to introduce a soft fork that would allow node operators the flexibility to redact arbitrary data deemed objectionable while still enjoying the full benefits of operating a node. The proposal utilizes BIP 3 as its foundation for a couple of significant reasons.

The recent discussions on the Bitcoin Improvement Proposal (BIP) 54 have brought to light various technical considerations and debates within the Bitcoin community, focusing on optimizing coinbase transaction uniqueness and handling. A significant critique from Luke Dashjr revolves around the use of the coinbase transaction's nLockTime for embedding an extranonce.

The introduction of OP_CHECKCONSOLIDATION (OP_CC) proposes a significant enhancement in the Bitcoin network's efficiency by optimizing consolidation transactions. This opcode streamlines the process by allowing subsequent inputs from the same scriptPubKey (SPK) to bypass individual signatures after the first input, leveraging that initial signature for validation.

The discussion initiated by Oren on BitcoinTalk and further elaborated in emails revolves around a proposed Bitcoin Improvement Proposal (BIP) focusing on Timelock-Recovery plans. This concept seeks to address the security concerns and logistical challenges associated with storing recovery seeds for Bitcoin, especially in terms of inheritance and long-term access.

In the realm of Bitcoin development, a nuanced conversation unfolds regarding the dynamics between Signet and Testnet environments, particularly from the perspective of mining. Saint Wenhao, a participant in this dialogue, shares insights into the operational mechanics and potential improvements within these testing frameworks.

The recent discourse on employing commit-based approaches for enhancing security within the digital transaction space highlights a consensus towards using commitments at each developmental stage, which inherently mitigates risks associated with MITM-style substitution and replay attacks. This method is favored as a safer, incremental step compared to an immediate shift to full quantum-safe (PQ) signature schemes.

The person behind the proposal has introduced an innovative Layer 3 protocol aimed at addressing some of Bitcoin's significant challenges, particularly around trust and custody in transactions. They underline that despite Bitcoin's revolutionary presence in the financial world, it inherently suffers from compromises such as slow transaction speeds compared to traditional card payments, high transaction fees for small amounts, and limited functionality restrained by game theory.

In the domain of cryptocurrency mining, there's a nuanced debate regarding the preferences of miners, also known as hashers, when it comes to choosing between custodial services and self-sovereignty. A common assumption prevails that most miners would opt for a custodian that charges slightly higher rewards fees in exchange for managing the complexities associated with mining.

The recent IRC meeting held on December 18, 2025, in the ctv-csfs-activation channel focused on discussing the activation parameters for BIP 119. Participants reached a consensus on employing BIP 9, opting for conservative parameters to guide its implementation.

In an effort to streamline communication and ensure that moderated emails reach their intended audience, a new procedure has been implemented for the Bitcoin Development Mailing List. A secondary mailing list, similar to the one previously found at https://lists.ozlabs.org/listinfo/bitcoin-dev-moderation, has been established to handle moderated messages.

The discussion opens with the consideration of new peer-to-peer (P2P) messaging protocols that could enhance the functionality and efficiency of blockchain networks. Specifically, it highlights the potential benefits of implementing template sharing, updating the bip324-one-byte-message-types, and facilitating the sharing of recent stale blocks.

A comprehensive rewrite of BIP 360 was initiated by Ethan Heilman, Isabel Foxen Duke, and Hunter Beast in response to the community's call for clearer documentation. The overhaul was deemed necessary following significant technical updates that shifted the proposal's direction, particularly concerning quantum resistance strategies.

In a collaborative effort led by Ethan Heilman, Isabel Foxen Duke, and their team, there's been a significant revision of BIP 360 to enhance Bitcoin's resilience against potential quantum computing threats. This overhaul was initiated due to the need for clearer and more coherent proposals after community feedback highlighted that previous versions had undergone extensive technical changes.

In a recent network crawl conducted on December 17, 2025, significant changes were observed in the acceptance of low fee filters by network nodes compared to measurements taken in September of the same year. Initially, only 2.0 percent of nodes accepted a low feefilter on September 10, which slightly increased to 3.9 percent by September 15. However, by December 17, there was a notable rise to 27.7 percent.

The email delves into an advanced method designed to enhance the security of Bitcoin transactions against potential quantum computing threats and signature forgeries. This method incorporates a multi-phase approach leveraging OP_CHECKTEMPLATEVERIFY (OP_CTV) and OP_TXHASH/OP_CHECKTXHASHVERIFY protocols, as detailed in BIP119 and a draft proposal.

Erik's proposal introduces a pioneering approach to safeguard the Bitcoin blockchain from quantum threats by implementing a novel security mechanism that does not necessitate the development of a new signature scheme. This method focuses on enhancing the proof of utxo ownership through a chain-native authorization primitive, leveraging the economic assumptions integral to transaction finality.

The introduction of statechains to the Bitcoin ecosystem over six years ago marked a pivotal step towards enhancing user privacy and transaction efficiency. The evolution of this concept, particularly through Commerce Block's Mercury Layer and the further innovation of incorporating blinded signing, has significantly refined the way statechains function.

The dialogue revolves around a series of proposed updates and critiques concerning the design and operational mechanics of a Bitcoin-related project, presumably called BMAX. The focus is on how shares within this system are managed, particularly in relation to mining difficulty and rewards distribution.

The discussion emphasizes the importance of maintaining neutrality and fairness in the development and implementation of protocols, particularly in relation to spam filtering. It argues against the inclusion of arbitrary filters within the core client by default, as this could potentially reinforce social stratums or subjective aspects of the protocol.

The implementation of silent payments in the Bitcoin Development Kit (BDK) is currently under exploration, focusing on incorporating this feature into BDK's transaction creation process, which is built around Partially Signed Bitcoin Transactions (PSBTs). The initiative seeks to address a gap in the existing PSBT specifications by proposing modifications that would accommodate the nuances of silent payment transactions.

The discourse on BIP54 and its implications for blockchain technology delves into the intricacies of preventing timewarp attacks while addressing future challenges, namely the nTime overflow issue. A proposed modification suggests incorporating a u64 timestamp within the coinbase transaction as a means to mitigate the timewarp attack.

The ongoing discourse within the Bitcoin development community centers on addressing the timestamp overflow issue inherent in Bitcoin's blockchain protocol. A notable proposition involves deploying a soft fork to leverage the "timewarp attack," aiming to extend the functionality of the current system without necessitating a complete overhaul.

The current initiative to update a book underscores the significance of community feedback in refining its contents. This process aims at ensuring the material's relevance and accuracy by inviting suggestions on potential improvements or corrections.

The discourse within the Bitcoin development community encompasses a broad spectrum of opinions on how to manage and mitigate spam within the Bitcoin network, as well as the broader implications for the network's functionality and philosophical underpinnings. Notably, the conversations reflect a deep engagement with both the technical and philosophical aspects of Bitcoin's design and operation.

One significant thread of discussion addresses the challenge of defining what constitutes spam on the Bitcoin blockchain.

The DustSweep proposal, crafted with the intention of addressing the accumulation of uneconomical dust in the Unspent Transaction Output (UTXO) set within the Bitcoin network, aims to offer a structured method for consolidating these dust transactions. This initiative proposes a category of transactions that nodes would relay and miners include, specifically during periods when both mempool and block space utilization are low.

Victor is developing a non-custodial vault system with a focus on a 2-of-2 multisig construction and a CSV-based recovery path, aiming for a solution that enhances the security and functionality of Bitcoin transactions without introducing custodial risks. His system employs an immediate spending path requiring both keys for transaction authorization and a delayed recovery path facilitated by a time-delay mechanism.

SHRINCS represents a novel hybrid signature scheme designed to combine the efficiency of stateful hash-based signatures with the robustness of stateless ones, positioning it as a particularly suitable choice for applications requiring a limited number of signatures from a given key. By leveraging an unbalanced XMSS tree for stateful operations and a variant of SPHINCS+ for stateless operations, SHRINCS achieves a high level of operational efficiency under typical conditions while ensuring reliability through a fallback mechanism in case of state loss or corruption.

Next week, a meeting will be organized to deliberate on the activation parameters for BIP 119. Participants are encouraged to familiarize themselves with the related pull requests, various activation methods, and previous meeting logs to contribute effectively to the discussion.

The recent initiative by SatsBridge introduces a pioneering protocol that integrates Bitcoin's Lightning Network (LN) with Ethereum's smart contract capabilities, focusing on enhancing user experience and security in cross-chain wallet architecture. This protocol utilizes LNURL AUTH to extend its application towards managing Ethereum abstracted accounts, thus enabling Lightning wallets to serve as remote signers for these accounts without necessitating any modifications to the existing Lightning wallets.

The proposal titled "The Cat," available on GitHub, presents a new strategy for limiting the use of Bitcoin for non-monetary purposes, specifically targeting protocols like inscriptions and Stamps-style applications. These currently account for a significant portion of the Bitcoin network's Unspent Transaction Output (UTXO) set, which is a critical element in Bitcoin's blockchain management.

The email discusses two Bitcoin Improvement Proposals (BIPs) published by the sender for peer review. The first proposal, named BUDS (Bitcoin Unified Data Standard), is an informational proposal that aims to establish a neutral, non-consensus taxonomy for describing transaction data within the Bitcoin network.

The conversation within the Bitcoin Development Mailing List has been rich with discussions on enhancing Bitcoin's security landscape in anticipation of quantum computing advancements. One pivotal area of focus is the exploration and implementation of post-quantum cryptographic solutions that can provide robust security against potential quantum attacks.

The Bitcoin network is confronted with a significant issue due to its reliance on a 32-bit unsigned integer for timestamping, setting an overflow date of February 7, 2106. This limitation threatens the network's operational integrity, potentially leading to block validation failures, difficulty adjustment issues, malfunctioning time-locked transactions, and corruption of the Median Time Past (MTP) mechanism.

A recent proposal highlights a novel approach towards managing the ScriptPubKey length in UTXO transactions within blockchain networks. The suggestion includes implementing a limit of 260 bytes on the ScriptPubKey length for new UTXOs, introducing an exception for transactions in blocks divisible by 256 without remainder.

The discourse on integrating a scheduled transaction broadcast feature into Bitcoin Core delves into its potential to enhance user privacy and strategic transaction management. This proposed functionality allows users to set transactions for future execution, either based on a specific time or block height, addressing needs such as disguising the transaction creation time or preparing for future conditions unsuitable for current bitcoin scripts.

The primary focus of the ongoing project is to develop a method for removing objectionable content from the blockchain, adhering to a set of meticulously defined design goals. These goals ensure that the removal process remains optional, ensuring that each node can decide independently whether to engage in the removal of content.

The concept of managing Bitcoin's Unspent Transaction Outputs (UTXO) set size through a feedback mechanism is presented as a solution to enhance the cryptocurrency's scalability and ensure long-term decentralization. Inspired by Proportional-Integral-Derivative (PID) control systems used in engineering, this strategy aims to mitigate the issues arising from the unbounded growth of the UTXO set, which could increase RAM requirements for nodes and potentially centralize the network among well-resourced participants.

The discussion around improving network traffic management for Bitcoin nodes has evolved significantly, focusing on the need for better segregation of traffic types to enhance security and efficiency. Initially, Bitcoin connections did not distinguish between different types of network messages, leading to a mixed traffic flow over a single network link.

The recent release of LND version 0.19.0 marks a significant advancement in addressing critical security vulnerabilities within the Lightning Network Daemon (LND), underscoring an ongoing effort to enhance the platform’s security posture. This update, available at LND 0.19.0, introduces essential fixes aimed at mitigating one denial of service (DoS) vulnerability and two theft of fund vulnerabilities.

The recent discussions and proposals within the Bitcoin Development community have spotlighted several advancements and considerations surrounding silent payment mechanisms, wallet descriptors, and the optimization of Bitcoin's technical infrastructure. A significant focus has been placed on enhancing wallet interoperability and the efficiency of backup and recovery processes through a Bitcoin Improvement Proposal (BIP) which introduces a novel top-level script expression, sp().

Vanadium represents a novel approach to developing firmware applications for hardware signing devices, addressing the longstanding challenges faced in embedded development such as limited RAM and flash memory, slow iteration cycles, and the complexities of debugging. Developed as a RISC-V Virtual Machine capable of running in an embedded Secure Element, Vanadium offers a significant departure from traditional development constraints by enabling the execution of arbitrary applications, termed "V-Apps," within a secure enclave environment.

The discussion centers around the proposal of a new BIP (Bitcoin Improvement Proposal) that aims to introduce an alternative output descriptor format, denoted as sp(). This initiative stems from the consideration of various ideas presented in a previously referenced PR (Pull Request).

A new prototype aimed at bolstering Bitcoin security through a vault-like scheme has been introduced, integrating the concept of blinded co-signers with Musig2, a multi-signature protocol. This innovative approach emphasizes minimizing the information available to co-signers about transactions to enhance the protection of fund movements on the blockchain.

The cryptocurrency community has been actively discussing the challenges associated with slow block propagation, particularly focusing on how it affects miners. An intriguing aspect of this discussion is the concept of optimistic mining, a method that allows miners to begin working on a new chain tip before its validation is completed.

The discussion centers on the technical complexity and implications of integrating specific primitives like OP_CSFS into blockchain technology to influence miner behavior, specifically to disincentivize the inclusion of third-party transactions. The initial assertion challenges the clarity and practical application of these combined primitives in creating effective smart contracts for this purpose.

A concern was raised regarding the potential for attackers to manipulate the reputation system in Lightning Network protocols, specifically targeting the mechanism by which reputations are calculated based on response times to payment requests. The mechanism under scrutiny allows for a 90-second window for replies; however, an attacker could exploit this by timing their responses such that they reply within the window while causing the next node in the sequence to exceed this limit due to inherent network delays.

The LN-Symmetry Project has taken significant strides in advancing the eltoo proposal, transforming it into research-quality software aimed at enhancing the Lightning Network's efficiency and reliability. Through meticulous development, the project has introduced basic functional tests for various channel operations, including openings, payments, and unilateral closes, among others.