This makes it an important topic of discussion in our Binance review. EVICT received a moderate amount of discussion on the mailing list as of this writing, with no major concerns noted but also roughly the same seemingly low level of enthusiasm which greeted the TLUV proposal last year. So, that’s like another level. But that’s further in the future, like considerable further in the future. With future updates to the mempool, hopefully we get around that just basically for free, where any channels that have already updated with v3 and ephemeral anchors will benefit from these other background updates as well. So, a number of people have been working on this package relay and v3, ephemeral anchors, cluster mempool, all this stuff. Mike Schmidt: Greg had mentioned DLCs as another potential protocol or different types of protocols that should be considering relay policy, mempool, and getting confirmations. Wait till V3 package relay?
/>

We noted in the newsletter, "We strongly recommend readers with an interest in transaction relay policy, which affects almost all second-layer protocols, read the notes for the insightful feedback provided by LN developers on several ongoing initiatives". This question, I guess, is for Murch, Greg or t-bast, but are there other layer 2 protocols that we see having an interest in contributing to some of these discussions? There is concern about the health of the Ethereum platform. Do you think that miners who support Ethereum and the hard fork might want to attack Ethereum Classic in order to make ensure that only one chain survives the hard fork? And in the interim, you can reduce your exposure by essentially reducing the amount of HTLC exposure you have in total, which is a configurable parameter, which I think all implementations do now. We have asked all validators to temporarily suspend BSC.
/>

Mark Erhardt: Sorry, I wanted to make the call back here that the proposal with the v3 transactions and the ephemeral anchors, of course, is what allows commitment transactions themselves no longer to have any fees. And so, basically it’s looking at what parts would be worth it to get a first cut of updates to the LN spec, and so there’s some back and forth on that. So, just moving the funding transactions to use MuSig2 already has a very nice benefit for all users, and it’s a good way to start experimenting with taproot with MuSig2 before moving on to PTLC. Mike Schmidt: https://youtu.be Murch, you good to wrap up this first bullet? Oh, Murch, you can poke your head in. Greg Sanders: Yeah, I can speak to that a bit. Greg Sanders: Well, statechains is another thing that needs - It’s any time-based contract, right? Bastien Teinturier: Okay, so for now, the first thing we are doing with taproot is just moving the funding transactions, the channel output to use the MuSig2 taproot output. Because it’s one thing to have the code, let’s say, launched and Bitcoin Core nodes get updated, and eventually the network updates enough where you can rely upon
p>

It’s, I would say, in the garden-path case, where the nice case where your counterparty just went offline and won’t talk to you anymore, it would become more expensive to resolve these HTLCs in an unpinnable way. Even if this isn’t the case, some Bitcoin community members contend that Bitcoin SV doesn’t meet the typical technical standards for a reputable exchange anyway, given how many transaction confirmations top exchanges usually require before they recognize deposits. The report showed its holdings of bitcoin exceeded customer deposits on a single day in November. Normally, water is so cheap because it is already so plentiful - although the difference between having zero litres of water and one litre of water per day is that of life and death, the difference between 99 and 100 litres of water per day is only a slightly less comfortable shower. I haven’t seen a lot of contribution from those projects, aside from having open dialogues. I’m making sure that whatever we’re building would actually be useful by these projects, I think that’s very important. Basically, I think there’s some basic agreement on this line that we’re shooting for with package relay, v3, and ephemeral anchors, where the commitment transaction can get a very nice cleanup and improvement and kind of confirmation requirements, while the rest, there’s still some pinning vectors beyond that with HTLC transactions.