Blog entry by Tahlia Kahn
So now we all know the entire technique of bitcoin functioning and how Bitcoins can be used for making all kinds of real transactions. Bitcoins are exchangeable for fiat forex via cryptocurrency exchanges and can be utilized to make purchases from merchants and retailers that settle for them. Greg Sanders: Yeah, if I can soar in. Mark Erhardt: So I’m questioning, certainly one of the problems that appears to leap out when i hear you speaking about this is, what if one side retains making updates but not concluding it? And we’ve always gone back and forth between these, because we don’t know if we should do a easier model first and watch for later to do a much more advanced version, or if we should just bounce to the extra complicated version proper now. Because we’ve at all times been discussing the truth that announcing, having the channel announcement point to a selected onchain output, was quite dangerous for privacy and that we could in all probability do higher. So, those are issues that we’ve all the time been simply hand-wavy about how we would do that sooner or later. Read More: Amid value drops and increased regulation, what’s the way forward for cryptocurrency?
But I don’t assume we’ll allow you to have any type of multiplier, as a result of one in all the opposite ideas was that you could also just announce some UTXOs that you own, with the proof that you just personal them, with a total value of, for instance, 2 bitcoin, and then that might grant you the flexibility to announce up to X instances that in channels without having to point to any particular onchain output. I didn’t assume it was too unhealthy, however the one key difference right here is that for the payment channels with penalties as at present designed, it’s necessitating that you retailer these secret nonces without end until channel close. These charts are cardinal a part of the whole affair as with them traders are ready to predict the motion near accuracy. But, realizing that the markets by no means shut is a useful safeguard to have. When you have one other Lightning-like channel specification that you just coded up or a customized channel type, you may as well embrace that on this channel announcement and it'll simply work. That’s why we’re not doing that proper now, and that’s why most individuals will just keep asserting the output that actually corresponds to the channel in order that when it will get spent, folks actually discover it and can take away it from that graph and know that they can not route by way of that channel anymore.
I believe we’re going to follow a easy model, where you enable pointing to any sort of output to pay for your channel. PTLC fixes that by making sure that as a substitute of utilizing the preimage of a SHA256 hash and its hash, we’re going to use elliptic curve factors and their private keys. This could appear unnecessary provided that BIP32 already gives prolonged private keys (xprvs) that may be shared between signing wallets. Maybe we will start with t-bast. Can the channel keep open when the UTXO will get spent? And alternatively, how do you make sure that the identical UTXO isn't reused for the announcement; and what occurs if that UTXO will get spent? So, will we should be conserving monitor of the UTXO truly not being moved while it's the stand-in to have announced the channel? Mike Schmidt: The taproot and MuSig2 channel dialogue somewhat leads into the updated channel announcement discussion and the way gossip protocol would have to be upgraded so as to assist shifting to P2TR outputs. So, we'd like to vary that, as a result of we need to allow taproot, which suggests allowing additionally input, especially if we use MuSig2; we don’t need to reveal the interior keys.
And right now, it’s going to make use of the same payment hash with all these nodes, which means that if somebody owns two of the nodes in the path, they are studying info, and this is unhealthy for privateness. Right now, everytime you ship a payment, this cost goes to go through multiple nodes on the network. Bastien Teinturier: Sure. So right now, https://m.blog.naver.com/ajjuguru/223229645304 after we introduced the channel on the network, we explicitly announced node IDs and the Bitcoin keys which are inside the multisig 2-of-2, and folks verified that the output that we are referencing is definitely locked with the script hash of multisig 2-of-2 of these two keys, so you may solely use it with scripts that basically comply with the format of Lightning channels without taproot. Mike Schmidt: Murch or t-bast, some other comments on taproot and MuSig2 channels? Mike Schmidt: Go forward, Murch. Mike Schmidt: Next part from the Summit discussed PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that is allowed by taproot and adaptor signatures.