• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

So now we all know the entire technique of bitcoin functioning and the way Bitcoins can be used for making all types of actual transactions. Bitcoins are exchangeable for fiat foreign money via cryptocurrency exchanges and can be used to make purchases from merchants and retailers that settle for them. Greg Sanders: Yeah, if I can jump in. Mark Erhardt: So I’m wondering, one among the issues that appears to jump out after i hear you speaking about that is, what if one facet retains making updates however not concluding it? And we’ve at all times gone again and forth between those, as a result of we don’t know if we must always do a simpler model first and look forward to later to do a much more advanced version, or if we should always simply soar to the extra complicated model proper now. Because we’ve at all times been discussing the fact that saying, having the channel announcement point to a specific onchain output, was fairly bad for privateness and that we might probably do better. So, these are issues that we’ve always been just hand-wavy about how we'd do that in the future. Read More: Amid value drops and increased regulation, what’s the future of cryptocurrency?

But I don’t suppose we’ll can help you have any sort of multiplier, as a result of one of the other ideas was that you can also just announce some UTXOs that you own, with the proof that you personal them, with a complete worth of, for example, 2 bitcoin, after which that may grant you the power to announce as much as X instances that in channels without having to point to any specific onchain output. I didn’t think it was too bad, but the one key distinction here is that for the payment channels with penalties as presently designed, it’s necessitating that you store these secret nonces endlessly until channel shut. These charts are cardinal part of the whole affair as with them traders are in a position to predict the motion near accuracy. But, figuring out that the markets never shut is a useful safeguard to have. When you've got another Lightning-like channel specification that you just coded up or a custom channel sort, you can too embrace that in this channel announcement and it will simply work. That’s why we’re not doing that right now, and that’s why most individuals will simply keep asserting the output that basically corresponds to the channel in order that when it will get spent, individuals really discover it and may remove it from that graph and know that they cannot route by means of that channel anymore.

I feel we’re going to keep on with a simple model, where you allow pointing to any kind of output to pay to your channel. PTLC fixes that by making sure that instead of using the preimage of a SHA256 hash and its hash, we’re going to use elliptic curve factors and their private keys. This could seem unnecessary on condition that BIP32 already offers prolonged private keys (xprvs) that can be shared between signing wallets. Maybe we can start with t-bast. Can the channel keep open when the UTXO will get spent? And alternatively, how do you guantee that the same UTXO will not be reused for the announcement; and what happens if that UTXO will get spent? So, will we must be holding observe of the UTXO actually not being moved whereas it's the stand-in to have announced the channel? Mike Schmidt: The taproot and MuSig2 channel discussion somewhat leads into the updated channel announcement discussion and how gossip protocol would should be upgraded in an effort to support transferring to P2TR outputs. So, we need to alter that, as a result of we want to allow taproot, which suggests permitting additionally input, particularly if we use MuSig2; we don’t wish to reveal the inner keys.

And right now, it’s going to make use of the identical payment hash with all these nodes, which signifies that if someone owns two of the nodes in the trail, they are studying information, and that is bad for privateness. Right now, whenever you ship a fee, this fee goes to go through multiple nodes on the network. Bastien Teinturier: Sure. So right now, when we announced the channel on the network, we explicitly introduced node IDs and the Bitcoin keys which might be contained in the multisig 2-of-2, and other people verified that the output that we are referencing is actually locked with the script hash of multisig 2-of-2 of these two keys, so you can solely use it with scripts that really observe the format of Lightning channels with out taproot. Mike Schmidt: Murch or youtu.be t-bast, another comments on taproot and MuSig2 channels? Mike Schmidt: Go ahead, Murch. Mike Schmidt: Next part from the Summit mentioned PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that's allowed by taproot and adaptor signatures.