Subscribe to our weekly newsletter

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

Summary

Recent discussions in the programming community have highlighted several developments in cryptocurrency protocols and user interfaces. Concerns about transaction malleability in Layer 2 contracts, specifically within the Lightning Network, have led to the recommendation of using Segregated Witness compatible scriptPubKeys and segwit v1 inputs to ensure transaction integrity. Meanwhile, a new feature called the "Raw Post" icon has been introduced to improve user interaction with complex post contents, aiding those who work with LaTeX or mermaid source code by providing straightforward access to markup text.

In the realm of Bitcoin smart contracts, a new SIGHASH scheme has been proposed to enhance transaction output bounds and validate fees, which could improve Poon-Dryja payment channels and Decker-Russell-Osuntokun update transactions. The scheme also emphasizes the importance of accuracy for watchtowers in maintaining network integrity. Additionally, privacy concerns in token systems are being addressed through the ecash blind signature scheme, ensuring anonymity for users and preventing token traceability by issuers.

Lastly, the blockchain community has seen the introduction of ortty, a command-line interface tool designed for interacting with Ordinals Inscriptions. Ortty functions as both an interactive explorer and a scriptable CLI, featuring capabilities like image display in terminals and batch operations for inscriptions management, and is available for download on major platforms. These collective efforts reflect the community's commitment to advancing the security, efficiency, and usability of cryptocurrency systems and blockchain technology.

New posts

February 2, 2024 09:52 UTC

delvingbitcoin

Raw markup icon for topics/comments

1 reply

  • A new "Raw Post" icon allows viewing raw markup in posts and comments.
  • It aids users working with LaTeX or mermaid code by simplifying content copying.
  • This feature enhances the experience for those dealing with complex text formats.

February 1, 2024 04:02 UTC

delvingbitcoin

Ortty: a terminal-based block explorer with a focus on inscriptions

1 reply

  • Ortty is a new command-line tool for Ordinals Inscriptions interaction, featuring an explorer and scriptable CLI.
  • It allows interactive exploration, batch operations, and supports terminal-based image display.
  • Available for download on major platforms, with capabilities showcased in screenshots for kitty terminal emulator users.

January 31, 2024 15:07 UTC

delvingbitcoin

Building Intuition for the Cashu Blind Signature Scheme

1 reply

  • The ecash scheme uses elliptic curves and hash functions for private transactions.
  • Alice blinds her key for tokens, Mike signs them, preserving anonymity.
  • Tokens prove ownership without revealing private keys, preventing double-spending.

January 31, 2024 06:52 UTC

delvingbitcoin

`sighash_outputdeltabounds`

1 reply

  • A new `SIGHASH` scheme aims to enhance Bitcoin smart contracts and channel updates.
  • It introduces 84-byte signatures to ensure fee validation within set limits.
  • The proposal offers solutions for channel fund conservation and Lightning Network adaptability.

January 30, 2024 09:32 UTC

delvingbitcoin

Malleability issues when creating shared transactions with segwit v0

1 reply

  • Layer 2 contracts use pre-signed refunds to secure against collaborative failures.
  • Transaction ID malleability can invalidate refunds and be used for blackmail in Lightning Network.
  • Segwit v1 binds signatures to inputs, yet omitting `prevtx` is safe only with taproot inputs.

January 29, 2024 22:29 UTC

delvingbitcoin

0conf LN channels and v3 anchors

7 replies

  • LN spec call reveals issues with 0conf channels in v3 transactions.
  • V3 transaction problems arise with unconfirmed ancestors during fee spikes or offline parties.
  • Potential solution may require funding transactions to have only confirmed inputs.

Ongoing Discussions

February 2, 2024 15:00 UTC

delvingbitcoin

An overview of the cluster mempool proposal

12 replies

  • The critique highlights inefficiency in current mempool management, advocating for streamlined methods.
  • Alternative solutions include peer-based transaction eviction management to minimize computational strain.
  • The complexity and limited applicability of sibling eviction raise doubts about its implementation value.

February 2, 2024 07:59 UTC

delvingbitcoin

Taxonomy of Transaction Fees in Smart Contracts

11 replies

  • Running a mining operation allows LSPs to use Bitcoin more cost-effectively than smaller entities.
  • Utilizing accelerators grants them control through their terms, influencing centralization.
  • Frequent, large transactions may compromise Bitcoin's fundamental decentralization and affect smaller LSPs' autonomy.

February 2, 2024 05:25 UTC

delvingbitcoin

64 bit arithmetic soft fork

41 replies

  • Stack operations' change aims to manage overflows by pushing result and overflow in LE64.
  • Balancing extended calculations and ease of existing overflow checks is crucial for programmers.
  • Evolving standards must consider trade-offs between functionality and code complexity.

January 31, 2024 19:13 UTC

delvingbitcoin

Ephemeral Anchors and MEVil

8 replies

  • Discussion centers on bypassing full diagram checks for mempool transaction incentives.
  • Packages mixing `TxA` with burns or `TxB` yield identical rates, affecting `TxC` eviction.
  • Simulating conflicts via execution phase checks could manage cluster-based RBF without diagramming.

January 31, 2024 08:40 UTC

bitcoin-dev

One-Shot Replace-By-Fee-Rate

15 replies

  • A vulnerability in Replace-By-Fee rules allowed replacing transactions with less profitable ones.
  • An untested pull request and a new code change aim to prevent these unprofitable replacements.
  • The "fee-rate-depth" concept is introduced to ensure only more profitable transactions replace others.

January 30, 2024 21:10 UTC

delvingbitcoin

Block-stalling issue in Core prior to v22.0

3 replies

  • Operating a non-listening node hampers attackers' ability to exploit vulnerabilities.
  • The strategy limits exposure, adhering to the principle of least privilege.
  • Adopting this measure protects node integrity, enhancing system stability.

January 30, 2024 05:17 UTC

lightning-dev

CheckTemplateVerify Does Not Scale Due to UTXO's Required For Fee Payment

7 replies

  • The DRo protocol's use of `SIGHASH_NOINPUT` excludes `nSequence` from transaction signatures.
  • Update transactions mandate equal input and output amounts, not allowing direct fee deductions.
  • Closing transaction fees require an external UTXO, usually supplied by the initiating party.

January 30, 2024 04:12 UTC

bitcoin-dev

CheckTemplateVerify Does Not Scale Due to UTXO's Required For Fee Payment

17 replies

  • "Anchor outputs" mitigate Lightning Network fee rate mismatches but raise blockspace usage.
  • Peter Todd suggests multi-fee rate offchain transaction versions, risking exploitation by some parties.
  • Fair fee distribution and HTLC complexities are unresolved in multi-feerate transaction proposals.

January 30, 2024 00:39 UTC

delvingbitcoin

Mailing list mode

6 replies

  • Managing digital information is essential for organization and staying current.
  • Traditional email filters automatically sort messages, simplifying management.
  • Mailing list mode consolidates forum updates, aiding in tracking discussions.

January 29, 2024 22:41 UTC

delvingbitcoin

Warnet + Increase Tx Relay Rate

12 replies

  • Balancing security and efficiency, the network employs a tx relay rate to manage bandwidth.
  • Adjusting the tx relay rate impacts transaction prioritization and node mempool synchronization.
  • Proposals suggest increasing the tx relay rate, considering peak mempool activity and RBF usage.

January 29, 2024 15:04 UTC

delvingbitcoin

Replace-By-Fee-Rate vs V3

5 replies

  • Bitcoin Core combats free relay with mandatory fees and a dynamic minimum fee policy.
  • V3 introduces rules to reduce unpaid relays and limit free relay opportunities.
  • Some argue for a liberal relay policy, though refining existing protocols is preferred.