People make this argument because they are comparing Bitcoin in it’s current state to a modern currency. So, making sure that you are actually pinning it and getting more value out of the attack than what you paid to actually make the pinning work is probably quite hard today, especially with the state of the mempool. As the number of users grows, the value per coin increases. But I don’t think we’ll allow you to have any kind of multiplier, because one of the other ideas was that you could also just announce some UTXOs that you own, with the proof that you own them, with a total value of, for example, 2 bitcoin, and then that would grant you the ability to announce up to X times that in channels without having to point to any specific onchain output. And I’m curious how Lightning engineers are thinking about taproot and MuSig2 related channels and how the audience should think about their nearer term uses in Lightning, in contrast to something that I think a lot of Bitcoin hopefuls are thinking about, which is Point Time Locked Contracts (PTLCs) involving schnorr signatures and adaptor signatures.
As a result, it will already be possible to proceed with the platform test in demo mode at this point. However, the solutions currently put forward by developers seeking to solve this problem suggest that the technological advances already made by blockchain will only continue, and these networks may well be able to handle much more data in the future. Hemant Jadhav is a crypto and blockchain writer with an expertise in technological content. Blockchain terdesentralisasi, yang berarti tidak dikendalikan oleh satu organisasi mana pun. Walaupun dari web tersebut juga menyediakan fasilitas untuk menggabungkan dan menggenerate PRIVATE-KEY yang asli, tetapi alangkah lebih aman bila kita gunakan web yang lain saja. Smaller Dark Web Bitcoin mixers may not have enough people performing transactions in a similar amount of Bitcoin as you, so either it’s going to be more obvious that it was you, or you’re going to be waiting too long for enough similar transactions to be registered. This is the main issue here, in my opinion, where you’re basically holding on extra key material. The main question that we had during the Summit is that there’s work when the current proposal spends the MuSig2 output for both commitment transactions and splices and mutual closes, which means that we have to manage nonce-state, MuSig2 nonce-state in many places, and it’s potentially dangerous because managing those nonces correctly is really important for secu
.
I didn’t think it was too bad, but the one key difference here is that for the payment channels with penalties as currently designed, it’s necessitating that you store these secret nonces forever until channel close. Mark Erhardt: Oh, maybe one. But as well, I mean, the biggest one is requirements for something like anyprevout, right? 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. So we’re only focusing published on youtu.be that funding output for now. I’m making sure that whatever we’re building would actually be useful by these projects, I think that’s very important. I think we’re going to stick to a simple version, where you allow pointing to any type of output to pay for your channel. And we’ve always gone back and forth between those, because we don’t know if we should do a simpler version first and wait for later to do a much more complex version, or if we should just jump to the more complex version right now. And even with that one, I think we’ve ironed out almost all the details, and I think both LND and LDK have a first version, a first prototype that is working a
t end-to-end.
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. For the proof of work as Ponzi economics argument to be valid, in my opinion, there needs to be a convincing reason why the collective drain on external resources will be experienced by the crowd as a prompt to precipitate back into individuals. But now your Bitcoin address is in the open and can be potentially traced back to a real person. I’m not sure what the consensus is right now. Maybe it’s a little too many steps back, but I don’t think we see a ton of pinning on the network right now. So obviously, pinning is possible and makes things harder, but how much weight should we be putting on fixing pinning if we don’t see any of it on mainnet? 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?