Your daily summary

Moonsettler's proposal introduces OP_PAIRCOMMIT, a new opcode for tapscript within the LNhance opcode family, including CTV, CSFS, IKEY, and PC, designed to optimize Lightning Network-Symmetry by minimizing SHA256 iterations for efficient rebindable channels. This opcode, which computes a "PairCommit" tagged SHA256 hash of the top two stack values, aims to facilitate unilateral closes in Lightning channels without the need for CAT, thereby offering a targeted solution for covenant tree or channel factory constructions. The proposal has been documented in a GitHub gist and submitted to the bitcoin/bips repository with contributions from Jeremy Rubin, Brandon Black, Salvatore Ingala, and Anthony Towns.

Andrew Poelstra highlights the challenges in maintaining an accessible and reliable email archive for Bitcoin development discussions due to the absence of a centralized entity, reflecting on the decentralized nature of the community's efforts and the vulnerabilities associated with relying on third-party organizations for information preservation. This mirrors broader tech community dilemmas on ensuring the longevity and accessibility of valuable digital archives amid technical, financial, and security challenges, as exemplified by the new gnusha.org archives.

Ariard addresses the complexities in open-source community dynamics, pointing out the significance of professional reputation, involvement in disputes, and the influence of employment relationships on freedom in open-source discussions. The email underscores the need for conflict of interest protections to maintain integrity in open-source contributions, reflecting on broader challenges of political activism and the importance of keeping Bitcoin development apolitical, with a focus on technical matters over cultural expression.

Jungly introduces Radpool, a novel approach to combat mining centralization through a syndicate of Mining Service Providers (MSPs), aiming to decentralize block template generation and scale down miner payouts while ensuring payment via Discreet Log Contracts (DLCs). This model promotes reliability and stability within the ecosystem, positioning Radpool as a bridge between centralized pools and peer-to-peer pools by offering decentralized template construction and payouts, thereby fostering network growth and competition among pool fees. Detailed discussions and development efforts are ongoing, with the community invited to contribute on Discord.

Subscribe to our weekly newsletter

Get the latest updates on the community, upcoming topics, and new discussions in your inbox every week.

Filter by List

Active Discussions 🔥

22 replies

Authored by

Ethan Heilman

Involving

Andrew Poelstra, Antoine Riard+6 others

  • An innovative Lamport signature scheme for Bitcoin was discussed at MIT DCI, avoiding OP_CAT.
  • The scheme relies on ECDSA signature lengths, requiring about 1000 signatures for security.
  • Despite its potential, the approach faces challenges like susceptibility to tuning and mix and match attacks.

5 replies

Authored by

Weikeng Chen

Involving

Brandon Black, Ethan Heilman+2 others

  • A novel solution introduces multi-byte opcodes to expand Bitcoin's functionality efficiently.
  • The proposed OP_OP method conserves NOPs and offers a flexible system for adding new opcodes.
  • This approach solicits community feedback to enhance Bitcoin opcode functionality sustainably.

3 replies

Authored by

Brandon Black

Involving

Antoine Poinsot, Murch+1 other

  • Discussions on CSFS BIP focus on including CSFSV opcode and leveraging NOPs.
  • CSFSA's inclusion aims to simplify script multisigs, potentially reducing weight units required.
  • Brandon Black seeks feedback, highlighting the collaborative effort in Bitcoin protocol development.

10 replies

Authored by

JohnLaw

Involving

harding, morehouse

  • The OPR protocol improves Lightning network payments by ensuring instant, size-agnostic resolution.
  • It deters dishonest behavior through a griefer-penalized mechanism, enhancing transaction security.
  • This protocol promises scalability and easier access, potentially revolutionizing Lightning payments.

4 replies

Authored by

renepickhardt

Involving

ajtowns, sorukumar

  • Recent research explores Lightning Network's channel depletion through mathematical theory.
  • Studies suggest nodes optimize fee potential, influencing channel liquidity and network topology.
  • Future strategies might focus on managing liquidity and predicting payment routes more effectively.

2 replies

Authored by

ajtowns

Involving

1440000bytes, AdamISZ

  • BIPs 118, 119, and 347 enhance Bitcoin's script capabilities, notably on signet.
  • APO and CTV's strategic uses include improved transaction flexibility and secure vault creation.
  • OP_CAT's prevalence in transactions surpasses APO and CTV, reflecting its broad application.

Today in Bitcoin/LN History

5 replies

Posted December 1, 2019 16:09 UTC

Authored by

Russell O'Connor

Involving

Anthony Towns

  • Anthony Towns shares a discussion on Taproot BIP, focusing on signing techniques.
  • The conversation suggests improvements for multisig sequences using sighash flags.
  • MAST design in Taproot is highlighted for efficiently analyzing script branches.

5 replies

Posted December 3, 2019 00:26 UTC

Authored by

Rusty Russell

Involving

Sergi Delgado Segura, Antoine Riard

  • Sergi Delgado Segura and Rusty Russell discuss the Lightning's WatchTower protocol.
  • They explore the protocol's messaging, accountability, and encryption standards.
  • Payment methods and attack preventions are also considered for protocol improvement.

5 replies

Posted August 16, 2023 15:22 UTC

Authored by

jamesob

Involving

Ajian, CubicEarth+3 others

  • Bitcoin scaling includes building 50,000 off-chain "bitcoin banks" for 1 billion users.
  • Increased block size risks centralization; innovations like Utreexo optimize but don't solve scalability.
  • Layer 2 solutions require sound policies and research for Bitcoin's integrity and scalability.

All Activity

4 replies

Posted November 19, 2024 22:54 UTC

Authored by

renepickhardt

Involving

ajtowns , sorukumar

The recent discourse on the Lightning Network (LN) explores the intricate dynamics of liquidity management and channel depletion within payment channel networks. Grounded in a mathematical framework, the discussion sheds light on how economic rationality and network topology intertwine to influence these phenomena.


5 replies

Posted November 19, 2024 19:35 UTC

Authored by

Weikeng Chen

Involving

Garlo Nicon, Brandon Black+2 others

In recent exchanges on the Bitcoin Development Mailing List, a series of proposals and insights regarding the development of Bitcoin script functionalities were discussed, focusing on enhancing flexibility and capability without compromising the blockchain's efficiency or existing operations. One innovative idea proposed involves the integration of opcode contexts through the script version, which would allow for a dynamic mapping from opcode numbers to their corresponding instructions.


22 replies

Posted November 17, 2024 21:59 UTC

Authored by

Ethan Heilman

Involving

Matthew Zipkin, Andrew Poelstra+6 others

The conversation explores innovative approaches to blockchain technology, particularly focusing on the implementation of covenants and introspection within Bitcoin's blockchain without necessitating OP_CAT. The dialogue delves into the limitations and potentials of utilizing opcodes like OP_SIZE for creating sophisticated contracts or covenants.


10 replies

Posted November 17, 2024 21:43 UTC

Authored by

JohnLaw

Involving

morehouse , harding +1 other

The discussion about the Off-chain Payment Resolution (OPR) protocol and its implications for the Lightning network touches upon several critical aspects of cryptocurrency transactions, particularly focusing on Hash Time Locked Contracts (HTLCs). The OPR protocol emerges as a novel solution aimed at addressing the limitations of the current Lightning Network by introducing mechanisms that discourage unprofitable force closures and mitigate the impact of griefing attacks.


1 reply

Posted November 17, 2024 18:56 UTC

Authored by

rustyrussell

Involving

ariard

The situation surrounding Antoine Riard's removal from the GitHub lightning organization is complex, involving multiple facets of interaction and decision-making within the open-source community. The sequence of events leading up to his removal is documented through various GitHub links provided for a more comprehensive understanding of the context.


2 replies

Posted November 16, 2024 23:13 UTC

Authored by

ajtowns

Involving

bytes , AdamISZ

The exploration of Bitcoin's technological advancements has led to significant interest and experimentation within the developer community, particularly in the areas of soft forks and novel transaction methodologies. One such experiment involved the demonstration of a spacechain using CheckTemplateVerify (CTV) on Signet, as seen in the simple-ctv-spacechain project on GitHub.


Posted November 16, 2024 14:58 UTC

Authored by

jungly

Radpool introduces a novel approach to combat mining centralization by establishing a syndicate of nodes referred to as Mining Service Providers (MSPs). This initiative is designed to decentralize block template generation, diverging from the traditional centralized mining pools.


3 replies

Posted November 15, 2024 15:33 UTC

Authored by

Brandon Black

Involving

moonsettler, Murch+1 other

The discourse within the Bitcoin Development Mailing List underscores a nuanced debate over the introduction of specific opcodes in the context of the CHECKSIGFROMSTACK (CSFS) Bitcoin Improvement Proposal (BIP). There's a divergence of views regarding the incorporation of the CHECKSIGFROMSTACKVERIFY (CSFSV) opcode into pre-tapscript versions.


bitcoin-dev

OP_PAIRCOMMIT

Posted November 15, 2024 00:00 UTC

Authored by

moonsettler

A new opcode, OP_PAIRCOMMIT, is proposed to be added to tapscript as part of the LNhance opcode family. This family includes CTV, CSFS, IKEY, and PC, aimed at enabling efficient rebindable channels adaptable to various covenant tree or channel factory constructions.


2 replies

Posted November 14, 2024 15:04 UTC

Authored by

ZmnSCPxj

Involving

renepickhardt, ZmnSCPxj

The discussion highlights the integration and potential challenges of implementing channel factories within the Lightning Network, emphasizing the necessity for plugins to monitor unilateral exits from these factories. It acknowledges that while the base node software will continue to monitor the blockchain for channels, the closure of a factory layer does not necessarily impede the operation of its hosted channels, which can still function directly onchain.


2 replies

Posted November 14, 2024 14:30 UTC

Authored by

Bryan Bishop

Involving

Weikeng Chen, Andrew Poelstra

The ongoing discussion raises concerns about the sustainability and reliability of hosting Bitcoin mailing lists, emphasizing the need for the community to secure its domain to ensure the longevity of critical communication channels. This arises from challenges experienced with external organizations like the Linux Foundation, which may not always provide indefinite support for Bitcoin-related projects.


2 replies

Posted November 13, 2024 22:06 UTC

Authored by

Ethan Heilman

Involving

Antoine Riard

The paper discusses a groundbreaking approach to cryptographic verification in Bitcoin transactions, particularly focusing on the balance between complexity and practicality within the scripting limitations of Bitcoin. It proposes an innovative method for creating and spending covenants in Bitcoin that does not require soft forks, using Tapscript.


Posted November 13, 2024 08:07 UTC

Authored by

ajtowns

Jonas Nick recently highlighted an innovative application of WOTS+ (Winternitz One-Time Signature Plus) using expanded script opcodes proposed for the GSR project, showcasing a method for generating and verifying signatures within Bitcoin transactions. This method involves creating a WOTS+ secret/public key pair, which then facilitates the generation of a large script encoding the public key, seed, and randomizers.


1 reply

Posted November 12, 2024 16:07 UTC

Authored by

Matt Corallo

The recent discussions within the Bitcoin development community have brought attention to the limitations of the current BIP 21 standard, which primarily focuses on transactions using base58 addresses and lacks official support for more advanced addressing schemes like Segwit and Taproot. Given the significant adoption of wallets that can handle these newer types of addresses and decode lightning payment instructions from URI query parameters, there's a consensus on the need to modernize BIP 21. This update would not only accommodate the inclusion of Segwit and Taproot addresses in URI bodies but also support the evolving Bitcoin payment landscape, including Silent Payments and BOLT 12.


4 replies

Posted November 12, 2024 00:26 UTC

Authored by

andyschroder

Involving

accumulator , andyschroder

The recent discussions and developments around BOLT12 have introduced innovative concepts aimed at enhancing the blockchain ecosystem's efficiency and security. Among these, the notion of "Bundled Payments" stands out as a pivotal addition.


49 replies

Posted November 9, 2024 15:16 UTC

Authored by

AntoineP

Involving

bytes , sjors +11 others

The analysis of the Great Consensus Cleanup proposal by Matt Corallo delves into addressing various inefficiencies and vulnerabilities within the Bitcoin protocol to enhance its security and performance. The proposal identifies critical issues, such as the timewarp vulnerability in the mining difficulty adjustment mechanism, which could be exploited to artificially lower mining difficulty, thereby destabilizing the network.


1 reply

Posted November 6, 2024 19:16 UTC

Authored by

ismaelsadeeq

Involving

murch

The discussion opens with a query about the rationale behind distinguishing transactions for fee prediction purposes based on whether they have been confirmed or not. It suggests considering transactions received in the last 10 minutes as a benchmark for competition, implying a more dynamic approach to predicting transaction fees.

The core of the analysis evaluates the effectiveness of various fee rate forecasters over 1293 blocks, from block 848920 to 850213.


10 replies

Posted November 5, 2024 18:24 UTC

Authored by

AntoineP

Involving

instagibbs , andrewtoth +4 others

The email discussion delves into the architectural decisions of Libbitcoin, particularly focusing on its approach to transaction validation in comparison with Bitcoin Core. Libbitcoin opts for a strategy where transactions below a certain milestone are not subjected to confirmability checks, such as verifying the existence and unspent status of inputs.


Posted November 5, 2024 11:57 UTC

Authored by

cndolo

In a recent exploration of the Lightning Network's (LN) susceptibility to censorship by network-level adversaries, such as Autonomous Systems (AS), significant findings were presented that shine a light on potential vulnerabilities within this decentralized payment system. The research delves into how privacy attacks leverage the identifiability of peer-to-peer messages through TCP headers, despite encryption.


Posted November 4, 2024 18:29 UTC

Authored by

Robert Netzke

The post on Delving Bitcoin introduces a proposed file format for importing and exporting descriptor-based wallets, which the author suggests might be suitable as a Bitcoin Improvement Proposal (BIP). The motivation behind this proposal stems from the complexities surrounding inheritance of digital assets, particularly for heirs who may not possess technical knowledge.


Posted November 4, 2024 17:45 UTC

Authored by

Jonas Nick

The latest version 0.6.0 of libsecp256k1 has been officially released, introducing several noteworthy updates and improvements to the library. Among the key enhancements is the addition of a MuSig2 module, marking a significant advancement in the library's functionality.


Posted November 4, 2024 15:34 UTC

Authored by

Adam Borcany

The exploration of Bitcoin transaction security through the implementation of proof-of-work (PoW) locked outputs presents a novel approach to adjusting difficulty in a more granular manner than current methods allow. Traditionally, signature grinding has been used to create PoW-locked output scripts in Bitcoin, exploiting the variable size of DER-encoded ECDSA signatures.


Posted November 4, 2024 13:06 UTC

Authored by

Michael Ford

The release of Bitcoin Core version 27.2 has been announced, available for download from Bitcoin Core's official website or through BitTorrent with the provided magnet link. This update encompasses several bug fixes, performance enhancements, and updated translations.


Posted November 4, 2024 10:50 UTC

Authored by

fanquake

Bitcoin Core version 27.2 has been officially released, available for download from the specified source or via BitTorrent. This update comes with a variety of fixes and improvements aimed at enhancing the overall performance and user experience.


1 reply

Posted October 30, 2024 19:39 UTC

Authored by

ajtowns

Involving

bramcohen

The discourse on integrating an 'apply' functionality within a higher-level programming language delineates the nuanced balance between retaining the compiled language's efficiency and embodying functionalities akin to a lower-level language without compromising the former's sophistication. The unique characteristic of the 'apply' function serves as a bridge between high and low-level languages, necessitating byte-level specifications for inputs, which can be achieved through a compilation process rather than imposing strict optimization requirements at the language level.


17 replies

Posted October 30, 2024 12:55 UTC

Authored by

reardencode

Involving

michaelfolkson , instagibbs +8 others

The addition of the OP_PAIRCOMMIT (PC) opcode to the LNhance family marks a significant development in the enhancement of the LNhance-Symmetry channel, as evidenced by the sequence CTV PC IK CSFS. This new opcode is part of an ongoing effort to refine blockchain functionality and efficiency, particularly within the Bitcoin network.


5 replies

Posted October 29, 2024 16:43 UTC

Authored by

/dev /fd

Involving

Abubakar Ismail, Peter Todd

The introduction of package transactions in Bitcoin represents a pivotal development, emphasizing the potential to refine these structures for improved transaction integrity and efficiency. The discussion highlights the significance of early optimization to mitigate security and privacy concerns associated with address reuse.


1 reply

Posted October 29, 2024 09:36 UTC

Authored by

bytes

Involving

40000bytes

The recent discussions at the bitcoin++ conference shed light on the innovative applications of the ecash protocol, extending its use beyond traditional monetary transactions. The focus was particularly on the potential for utilizing blind signatures, as seen in the coinjoin by Wabisabi, for applications like discount coupons.


1 reply

Posted October 25, 2024 14:49 UTC

Authored by

Andrew Toth

Involving

waxwing/ AdamISZ

The discussion revolves around a Bitcoin Improvement Proposal (BIP) geared towards standardizing the generation and verification of discrete logarithm equality proofs (DLEQ proofs) within the context of the secp256k1 elliptic curve, crucial for Bitcoin and similar cryptocurrencies. This proposal is inspired by advancements in ECDSA adaptor signatures and aims for compatibility with implementations like those by BlockstreamResearch.


7 replies

Posted October 23, 2024 20:35 UTC

Authored by

AntoineP

Involving

roasbeef , ariard +3 others

The refusal of Niklas and AntoineP to delay the disclosure of a significant vulnerability, identified as CVE-2024-38365, against the wishes of the btcd maintainers has sparked a discussion on the ethics and responsibilities surrounding the discovery and reporting of security flaws. The vulnerability in question, known as the "findanddelete" bug within the btcd environment, was detailed shortly after btcd released their security advisory, with comprehensive information made available through a detailed disclosure and btcd's security advisory page.


1 reply

Posted October 22, 2024 20:21 UTC

Authored by

ellemouton

Involving

harding

The recent summit discussions have revealed a consensus on the necessity for considerable updates to the current protocol proposal, emphasizing the introduction of new message structures and their announcement methodologies. A pivotal change involves transitioning to a Pure Type-Length-Value (TLV) format for all new messages.


2 replies

Posted October 22, 2024 19:51 UTC

Authored by

cryptoquick

Involving

conduition

The conversation around introducing quantum resistance into the Bitcoin protocol is gaining momentum, driven by the escalating concerns over the potential threats quantum computing may pose to the cryptocurrency's security infrastructure. The proposed Bitcoin Improvement Proposal (BIP) seeks to preemptively address these threats by incorporating a suitable signature algorithm that would prepare Bitcoin for the advanced capabilities of quantum computing.


1 reply

Posted October 22, 2024 13:52 UTC

Authored by

MishaKomarov

Involving

GaloisField2718

The discussion centers around the innovative implementation of covenants in Bitcoin through the use of Polynomial Inner Product Encryption (PIPE), which does not necessitate a soft fork, enhancing the blockchain's capabilities by allowing for advanced spending rules. These rules can specify conditions under which coins can be spent, such as restricting transactions to certain addresses or after particular conditions are met.


3 replies

Posted October 21, 2024 21:38 UTC

Authored by

roasbeef

Involving

everythingSats , benthecarman +1 other

The discussion highlights a pivotal moment in the development of Payment Through Lightning Channels (PTLC), focusing on the debate between adopting single signature or MuSig2 based adapter signatures. The recent merge of the musig module for libsecp, which does not yet implement MuSig2 adapter signatures, suggests that further developments, including drafting a new Bitcoin Improvement Proposal (BIP), are anticipated.


Posted October 20, 2024 06:56 UTC

Authored by

Antoine Riard

During the summer, a significant effort was made to enhance the bitcoind build system and further develop the libbitcoinkernel projects. The motivation behind these efforts was to explore the feasibility of running the historical bitcoin consensus engine independently within a secure enclave.


7 replies

Posted October 18, 2024 04:01 UTC

Authored by

tbast

Involving

David Harding , Vincenzo Palazzo +1 other

The recent discussion focuses on the development of a new protocol aiming to enhance privacy and security within the CLN (C-Lightning) framework, as detailed in an updated proposal available at bLIP 42. This protocol introduces the use of a distinct invreq_payer_id for each contact, a method that significantly improves domain separation.


31 replies

Posted October 17, 2024 22:42 UTC

Authored by

ZmnSCPxj

Involving

cryptoquick , ariard +3 others

The discussion delves into the intricate details and concerns surrounding the SuperScalar mechanism and its integration and impact on the Bitcoin Lightning Network, particularly focusing on scalability, security, and operational efficiency. The mechanism, influenced by the Decker-Wattenhofer decrementing-nSequence mechanisms and timeout trees, is engineered to enhance offchain liquidity allocation to new users without necessitating any changes to blockchain consensus.


Posted October 17, 2024 13:40 UTC

Authored by

Andrew Toth

This proposal introduces enhancements to the Partially Signed Bitcoin Transaction (PSBT) format, specifically Version 2 as outlined in BIP 370, to support silent payments as described in BIP352. Silent payments aim to enhance privacy by altering how transaction outputs are computed and verified, necessitating additional data fields and revised responsibilities for entities involved in the transaction process.

Silent payment transactions differ from standard PSBTs in that output scripts cannot be finalized until all inputs have been added to the transaction.


Posted October 17, 2024 00:45 UTC

Authored by

scott beeker

The consideration of transitioning Bitcoin to a post-quantum cryptographic algorithm such as SLH-DSA (Stateless Hash-Based Digital Signature Algorithm) stems from the growing concern over potential threats posed by quantum computing. This transition is seen as crucial for safeguarding Bitcoin against the capabilities of quantum computers, which could eventually break the cryptocurrency's current elliptic curve cryptography.


9 replies

Posted October 15, 2024 22:32 UTC

Authored by

AntoineP

Involving

David Harding , ariard +2 others

The conversation delves into the technical nuances of Bitcoin's scripting and signature verification mechanisms, particularly focusing on the FindAndDelete function and its implications for script execution and consensus. The FindAndDelete function is crucial as it modifies a copy of the script for the purpose of committing to it in the sighash without affecting the script being executed.


30 replies

Posted October 15, 2024 21:03 UTC

Authored by

EthnTuttle

Involving

davidcaseria , bytes +5 others

The conversation on the Stratum Mining protocol's GitHub page delves into the pivotal advancements represented by the Stratum V2 mining protocol. This protocol is seen as a significant leap forward for the mining sector, promising enhanced efficiency and security.


15 replies

Posted October 14, 2024 13:03 UTC

Authored by

halseth

Involving

bytes , ajtowns +4 others

The recent updates to a specific repository have introduced significant enhancements in the verification of schnorr signatures within a Zero-Knowledge (ZK) environment for blockchain transactions. This development eliminates the need to blind public keys during the verification process, focusing on proving the validity of a signature associated with a public key in the Unspent Transaction Output (UTXO) set without revealing the key itself.


4 replies

Posted October 14, 2024 09:00 UTC

Authored by

Weiji Guo

Involving

Weikeng Chen

The recent updates in cryptographic solutions within the domain of open application circuits emphasize a shift towards recursive verification to streamline the process. This approach negates the requirement to publish each application circuit's verification key on-chain, opting instead for a singular circuit verified through recursion.


5 replies

Posted October 12, 2024 04:46 UTC

Authored by

Antoine Riard

Involving

Peter Todd, waxwing/ AdamISZ

The conversation starts with the recognition of a need for clear, step-by-step instructions for volunteers interested in setting up new nodes, focusing on the use of current and default installations of Core/btcd along with lnd/cln/ldk. It delves into specifics such as the amount required in channels, the necessary number of channels, the relevance of channel types, volunteer interconnectivity, desired network topology, and the significance of network connectivity and Tor usage.


3 replies

Posted October 11, 2024 20:17 UTC

Authored by

ZmnSCPxj

Involving

ariard , bytes +1 other

The discussion around Bitcoin's development and the challenges in implementing consensus changes delves into the complexities beyond the technical aspects, such as halving cycles and market speculation. It suggests that the evolution and stabilization of Bitcoin are significantly influenced by broader factors, including real-world power dynamics and the roles of influential figures and financial stakeholders.


26 replies

Posted October 10, 2024 22:36 UTC

Authored by

salvatoshi

Involving

sipa , josibake +6 others

In the realm of cryptocurrency security, especially within Bitcoin's framework, the conversation about enhancing the functionality and security of Extended Public Keys (XPUBs) through various hashing methods is gaining attention. The goal is to devise a system that can derive chain code from XPUBs in a manner immune to the order in which they are applied, addressing issues related to wallet policies or descriptors' sequence and their behaviors in multi-signature setups.


Posted October 10, 2024 12:56 UTC

Authored by

ajtowns

The latest release, Bitcoin Inquisition 28.0, is now publicly accessible at the provided GitHub link, building upon the foundations of Bitcoin Core 28.0. This version introduces several significant enhancements including support for TRUC and anchor relay mechanisms while implementing a default full replace by fee behavior to optimize transaction handling.


Posted October 9, 2024 19:30 UTC

Authored by

Niklas Goegge

The recent communication highlights significant security vulnerabilities identified in Bitcoin Core versions preceding 25.0, marking an important development for users and contributors alike. These vulnerabilities are meticulously documented and can be found through the provided links, which include detailed discussions on issues like mutated blocks hindering propagation, challenges with sending large inventories, and a specific vulnerability that could lead to a crash when processing block transactions.


Posted October 9, 2024 16:32 UTC

Authored by

waxwing/ AdamISZ

The blog post authored by AdamISZ/waxwing, available at Reyify, delves into the concept of adaptor signatures and their potential expansion beyond traditional limitations. The initial inquiry revolves around the utility of on-chain verification for statements not confined to the secp256k1 generator G. This question branches into two directions: the recognition of its usefulness for Zero-Knowledge Proof (ZKP) constructions and the acknowledgment of its current impracticality due to limitations in verification capabilities.

The core of the investigation examines if adaptor signatures could enable a form of verification that is not directly possible.


Posted October 7, 2024 20:25 UTC

Authored by

MishaKomarov

This post introduces Bitcoin PIPEs (Polynomial Inner Product Encryption), a groundbreaking approach to implementing covenants on Bitcoin without necessitating a soft fork. Covenants are mechanisms that enable users to set specific conditions on how their coins can be spent in the future, thereby unlocking advanced spending rules and new use cases such as the native verification of Zero-Knowledge Proofs, the creation of native tokens with complex behaviors, and restaking mechanisms to pool Bitcoin for securing other networks.


Posted October 7, 2024 12:16 UTC

Authored by

Dr. Craig S. Wrong

The project Swift Bitcoin, accessible through GitHub and its website, represents a significant effort by the creator to delve deeply into the inner workings of Bitcoin. Initially, it was conceived as a platform for the developer to enhance their understanding of Bitcoin's mechanics, focusing on the implementation of various Bitcoin Improvement Proposals (BIPs) using Swift, a favorite programming language of the developer.


Posted October 4, 2024 23:31 UTC

Authored by

Ava Chow

Bitcoin Core version 28.0 is now available for download from bitcoincore.org, introducing new features, several bug fixes, performance improvements, and updated translations. Users encountering bugs are encouraged to report them on the project's GitHub issue tracker at GitHub.


Posted October 4, 2024 06:45 UTC

Authored by

ajtowns

The integration of Plotly.js for graphing capabilities within a Discourse theme component represents a significant advancement in data visualization directly within forums or discussion platforms. This development enables users to create and interact with traditional XY plots using simple text markup, eliminating the need for external image generation.


3 replies

Posted September 28, 2024 02:28 UTC

Authored by

James Ferguson

Involving

Pieter Wuille, Keagan McClelland

In the realm of cryptocurrency, particularly Bitcoin, managing small, unspendable residual amounts known as dust is a challenge that impacts network efficiency, transaction fees, and privacy. The proposal titled "Keep the Change," which introduces the concept of "OP_KEEPCHANGE," aims to address these issues by crediting small residual Unspent Transaction Outputs (UTXOs) to the primary recipient’s address instead of generating new change outputs.


4 replies

Posted September 27, 2024 18:42 UTC

Authored by

ajtowns

Involving

garlonicon , levantah +1 other

The discussion introduces a novel approach to Pay to Proof of Work (P2W) transactions on the Bitcoin testnet4, utilizing a specific address and script that leverages a less than 60-byte signature requirement. This method allows for a gradual increase in difficulty without necessitating any consensus changes, making it applicable across various networks including the mainnet.


4 replies

Posted September 26, 2024 23:03 UTC

Authored by

carla

Involving

ProofOfKeags , morehouse

The discussion surrounding the reputation system for managing Hashed Timelock Contracts (HTLCs) within a network highlights several critical points related to the decision-making process of forwarding and receiving HTLCs. It emphasizes the dual focus of nodes on both incoming and outgoing directions, ensuring that transactions are endorsed by nodes with reputable histories.


7 replies

Posted September 26, 2024 18:02 UTC

Authored by

renepickhardt

Involving

AntonioPerez , harding +2 others

The discussion centers on the nuances of network state weighting, liquidity distribution in channels, and their implications for node balance uniformity within the context of minimum cost flow (MCF) computations and wealth distribution. The sender initially corrects a miscount in states to ten, which alters the basis of their argument regarding the probability models used to compare wealth distributions and payment feasibility.


3 replies

Posted September 26, 2024 15:02 UTC

Authored by

Jonas Nick

Involving

Antoine Riard, Weikeng Chen

The discussion revolves around several key challenges and innovations in the realm of blockchain technology, with a particular focus on privacy, scalability, and efficiency. One significant challenge highlighted is the process of bridging within blockchain protocols, which is crucial for enhancing Bitcoin's capabilities, including the introduction of strong privacy measures.


2 replies

Posted September 26, 2024 12:59 UTC

Authored by

sCryptts

Involving

benthecarman, ajtowns

The exploration of enhancing Bitcoin's covenant mechanism through the use of OP_CAT combined with the Schnorr signature scheme represents a significant stride in streamlining the signature computation process. By adopting a specialized technique for key selection, this method addresses the inherent limitations of Bitcoin Script's OP_ADD operation, which struggles with directly incrementing a 256-bit integer.


9 replies

Posted September 25, 2024 12:04 UTC

Authored by

Hunter Beast

Involving

PierreLuc DallaireDemers, Antoine Riard+1 other

The recent discussions and updates surrounding the development of a Bitcoin Improvement Proposal (BIP) to introduce quantum resistance into Bitcoin's cryptographic framework underscore the community's proactive approach towards safeguarding the cryptocurrency against potential quantum computing threats. Central to these discussions is the acknowledgment of IBM's advancements in quantum computing, particularly with its Quantum System Two, which potentially supports up to 16,000 qubits.


3 replies

Posted September 25, 2024 02:22 UTC

Authored by

ZmnSCPxj

Involving

renepickhardt , ZmnSCPxj

The discussion on the incorporation of multiparty channel constructs within payment channel networks highlights both potential benefits and challenges. The primary advantage of these constructs is their ability to enhance payment reliability and offer service level guarantees.


delvingbitcoin

Lightning Cheques

Posted September 24, 2024 21:23 UTC

Authored by

andyschroder

The concept of Lightning Cheques is introduced as an innovative paper-based payment method within the cryptocurrency domain, specifically tailored for offline transactions using the Lightning Network. These instruments combine a BOLT12 invoice_request on the front side with an offer on the back, facilitating a new way to conduct transactions without direct internet access.


1 reply

Posted September 24, 2024 15:36 UTC

Authored by

rustaceanrob

Involving

valuedmammal

The discussion focuses on improving the wallet recovery process for cryptocurrency users and their heirs, highlighting the necessity for an intuitive and standardized approach. The current recovery methods, which often require manual insertion of descriptors from various file formats like txt or json, are deemed inadequate and cumbersome.


20 replies

Posted September 23, 2024 18:48 UTC

Authored by

kravens

Involving

bytes , conduition +5 others

The conversation largely focuses on the intricacies and challenges associated with implementing privacy-centric protocols in cryptocurrency transactions, particularly those that enhance anonymity without relying on centralized coordination. A key point of discussion is the SINGLE|ACP protocol, which, despite its potential for maintaining transaction privacy, faces scrutiny over its requirement for matching input/output indices.


10 replies

Posted September 23, 2024 14:33 UTC

Authored by

virtu

Involving

sipa , bytes +1 other

The discussion begins by addressing a novel encoding mechanism devised to maintain the integrity of response entries' order. This is crucial given that recursive resolvers may alter the sequence, potentially leading to data misinterpretation.


98 replies

Posted September 19, 2024 18:48 UTC

Authored by

Ava Chow

Involving

Léo Haf, Greg Tonoski+34 others

The recent discourse within the Bitcoin Development Mailing List has shed light on the pressing issue of managing and advancing Bitcoin Improvement Proposals (BIPs), which are crucial for the evolution of Bitcoin's protocol. The acknowledgment of a bottleneck in the BIP process, primarily due to limited oversight capacity, has catalyzed discussions on enhancing the procedural framework for BIP evaluations and integrations.

A pivotal suggestion that emerged from these talks is the proposal to augment the team of BIP editors.


39 replies

Posted September 19, 2024 14:55 UTC

Authored by

Fi

Involving

plebhash , marathongary +4 others

The recent advancements and discussions within the cryptocurrency mining community highlight several key developments aimed at enhancing the transparency, efficiency, and fairness of mining operations. A notable update has been made to the share accounting system, as detailed in a GitHub repository, which introduces significant changes intended to improve share verification and management.


1 reply

Posted September 19, 2024 08:12 UTC

Authored by

Antoine Poinsot

Involving

Antoine Riard

Antoine Poinsot has highlighted a pivotal update concerning Bitcoin Core, specifically addressing the misconception that checkpoints are no longer utilized as a defense mechanism against known attacks. This clarification comes in the wake of discussions sparked by the report produced by Darosior, which led to the reevaluation of the role of checkpoints within the Bitcoin Core infrastructure.


2 replies

Posted September 13, 2024 14:58 UTC

Authored by

Jassu

Involving

mcelrath, Jassu7082

Proof of Partial Work (PoPW) is a concept significant within the realm of cryptocurrency mining, particularly in the context of mining pools. It represents the effort miners contribute by submitting shares that demonstrate the work they've performed, even if it hasn't led to the discovery of a new block.


12 replies

Posted September 11, 2024 15:14 UTC

Authored by

remyers

Involving

murch , remyers

The recent developments in optimizing transaction fees through innovative coin selection strategies have garnered significant attention within the cryptocurrency community, particularly among Bitcoin developers and Lightning Service Providers (LSPs). A focal point of these discussions has been the draft pull request PR 30080 on Bitcoin's GitHub repository.


Posted September 9, 2024 12:40 UTC

Authored by

Ethan Heilman

The Bitcoin Improvement Proposal (BIP) discussed introduces a new opcode, FOLDFUNCTIONSTREAM, which is a modification of the existing NOP4 opcode within the Bitcoin scripting system. This opcode aims to efficiently perform functional folds across data, addressing issues related to computational expense and safety in script execution.


Posted September 9, 2024 10:54 UTC

Authored by

dgpv

The recent update to B'SST, a project hosted on GitHub, marks a significant transition from a proprietary license to AGPLv3 with its version update from 0.1.3 to 0.1.4. This change primarily aims to address the concerns and limitations imposed by the previous licensing model.


16 replies

Posted September 5, 2024 09:04 UTC

Authored by

reardencode

Involving

sipa , moonsettler +3 others

In the exploration of cryptographic security, a novel approach known as "Dark Smoothie" has been brought to light, revealing a significant vulnerability within digital transactions. This method allows an attacker to extract sensitive information, specifically a 256-bit seed, from just two signatures generated by the same device.


4 replies

Posted September 3, 2024 00:35 UTC

Authored by

Victor Kolobov

Involving

Matt Corallo, /dev /fd+1 other

The discussion encompasses a variety of topics related to Bitcoin development, particularly focusing on the post-Taproot activation landscape and the exploration of covenants or contracting primitives extending Bitcoin script. It reflects on the historical stalemate in consensus discussions since Taproot's activation in 2021, suggesting that a lack of trial-and-error design and development processes akin to those used for Schnorr/Taproot changes has hindered progress.


Posted September 3, 2024 00:13 UTC

Authored by

shehzanmaredia

The recent release of the Lava Loans paper introduces a new DLC-based loans protocol aimed at facilitating more trust-minimized bitcoin-secured loans. This development is shared within the Delving Bitcoin community, where it has garnered attention and feedback from its active members.


Posted September 2, 2024 23:18 UTC

Authored by

Tobin Harding

The ReadCompactSize function, as defined in serialize.h, includes an optional range_check parameter that is set to true by default. This setting ensures that the value read by the function does not exceed 0x02000000, effectively enforcing a limit that keeps the compact size value within the bounds of a 32-bit unsigned integer.