If you can accept the risks, Bitcoin can be a very good investment. For serious companies and marketing executives, attracting just one new lifetime customer, business partner, or employee, leveraging a premium domain, will justify this excellent long-term investment. Bastien Teinturier: Because there’s only one other party can actually change the feerate of a commitment transaction and it’s the channel initiator. Bastien Teinturier: Yeah, I think also one of the reasons we don’t see pinning is that really, it’s harder to pin right now and make it work your while, because right now, commitment transactions do pay some fees. I would argue that by the time Bitcoin becomes a high volume consumer traded currency most transactions will pass through some form of cash register. This provides a smart way to issue the currency and also creates youtu.be write an article incentive for more people to mine. Nothing is latency sensitive here, so this really isn’t an issue. Here, you can manually adjust the fee if required. And honestly, the communication is really not an issue here, because you are actually closing that channel, you’ve already decided that you want it to close it, so you’re not relaying any Hash Time Locked Contracts (HTLCs) on
>

So, t-bast, it sounds like you’re comfortable kind of walking through what Rusty’s proposing here. It’s also just a life headache, but it’s a judgment call, because right now, LN kind of works on firm handshakes, nobody’s attacking each other, nobody’s doing channel jamming, but that could all change overnight. A future change to LDK may close channels with feerates that are too low, and work on proposals like package relay may make anchor outputs or similar techniques adaptable enough to eliminate concerns about present feerates. So, a number of people have been working on this package relay and v3, ephemeral anchors, cluster mempool, all this stuff. 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". Follow the live Bitcoin price using the real-time chart, and read the latest Bitcoin news and forecasts to plan your trades using fundamental and technical analysis. A trading strategy is simply a plan you follow when executin
es.

● Rust-Lightning 0.0.98 is a minor release containing several improvements and bug fixes. ● How do route hints affect pathfinding? CSV, route hints; we have a couple of releases, HWI and LDK to go over; and just a single lone Bitcoin Core GUI PR to review. Mike Schmidt: Well, it’s great to have some Lightning expertise for this newsletter, that’s for sure. I understand why that would be the case for the initial open commitment, because when the opener opens a channel and the - well, I guess the other party does accept it anyway. Greg Sanders: Well, statechains is another thing that needs - It’s any time-based contract, right? Greg Sanders: Sure. Yeah, so for the past year or so, I’ve been working on an implementation of what’s called Eltoo, which I picked the name LN-Symmetry. Greg Sanders: Yeah, well part of it, right. 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? And so you really have to care that there are ways of paying fees and getting in blocks properly, which there really isn’t t
ll right now.

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. Greg, folks may be familiar with some of your further background working on Bitcoin, but you’ve been doing some Lightning work recently. I work at ACINQ on the Lightning specification and implementation Eclair, and on the Phoenix wallet as well. Then, instead of signing the transaction directly, the wallet signs that hash. 5256 allows reading the wallet passphrase from a file. Prior, LND already supported importing Base64-encoded PSBTs either as plain text or from file. The duplication issue was effectively prevented by the subsequent introduction of BIP34 which required the block’s height as the first item in ascriptase transaction’s scriptSig. Maybe you can kind of put it to rest why that wasn’t a main discussion item during the meeting and why? So basically, it’s kind of a trade-off between the case where your channel partner falls over versus they’re trying to pin you and steal your funds. When it comes to cryptocurrencies, the funds are typically lent by the exchange in return for a funding fee.