[bitcoin-dev] ossification and misaligned incentive concerns

2023-11-03 Thread Erik Aronesty via bitcoin-dev
currently, there are providers of anonymity services, scaling services, custody, and other services layered on top of bitcoin using trust-based and federated models. as bitcoin becomes more popular, these service providers have increasingly had a louder "voice" in development and maintenance of th

Re: [bitcoin-dev] The Pinning & Replacement Problem Set

2023-11-03 Thread Antoine Riard via bitcoin-dev
Hi John, I think lightning and other second time-sensitive layers being hit by safety issues whenever the blocks are full is common knowledge as the issue is being described in the paper under the "forced expiration spam" issues arising spontaneously within an environment with high block space dem

[bitcoin-dev] Bitcoin Core 26.0 release candidate 2 available

2023-11-03 Thread Michael Ford via bitcoin-dev
Binaries for Bitcoin Core version v26.0rc2 are available from: https://bitcoincore.org/bin/bitcoin-core-26.0/test.rc2/ Source code can be found in git under the signed tag https://github.com/bitcoin/bitcoin/tree/v26.0rc2 This is a release candidate for a new major version release. Prel

Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?

2023-11-03 Thread Melvin Carvalho via bitcoin-dev
pá 3. 11. 2023 v 11:16 odesílatel Brad Morrison napsal: > Melvin/all, > > You make good points about high network fees being disruptive. > > What is more disruptive are spikes & valleys (instability) that last > longer than the mempool cycle can handle. > > Right now, https://mempool.space/ indic

Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?

2023-11-03 Thread Brad Morrison via bitcoin-dev
Melvin/all, You make good points about high network fees being disruptive. What is more disruptive are spikes & valleys (instability) that last longer than the mempool cycle can handle. Right now, https://mempool.space/ indicates that there are about 105,000 unconfirmed transactions and that

Re: [bitcoin-dev] OP_Expire and Coinbase-Like Behavior: Making HTLCs Safer by Letting Transactions Expire Safely

2023-11-03 Thread Antoine Riard via bitcoin-dev
> The idea with package relay is that commitment transaction fees will > be zero and that fees will always be paid via CPFP on the anchor > output. Yes, even if multiple commitment transactions are pre-signed with a RBF range of more than zero, an attacker can always select the lowest fees pre-sig

Re: [bitcoin-dev] OP_Expire and Coinbase-Like Behavior: Making HTLCs Safer by Letting Transactions Expire Safely

2023-11-03 Thread Antoine Riard via bitcoin-dev
> To be clear, are you talking about anchor channels or non-anchor channels? > Because in anchor channels, all outputs other than the anchor outputs provided > for fee bumping can't be spent until the commitment transaction is mined, which > means RBF/CPFP isn't relevant. I think the distinction i