자유게시판

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

So now we all know the whole means of bitcoin functioning and the way Bitcoins can be used for making all types of real transactions. Bitcoins are exchangeable for fiat currency click through the up coming page cryptocurrency exchanges and can be utilized to make purchases from merchants and retailers that accept them. Greg Sanders: Yeah, if I can leap in. Mark Erhardt: So I’m wondering, considered one of the problems that seems to jump out once i hear you speaking about that is, what if one side retains making updates however not concluding it? And we’ve always gone again and forth between these, because we don’t know if we should do a simpler version first and look ahead to later to do a way more complicated model, or if we must always simply jump to the more complicated version right now. Because we’ve all the time been discussing the truth that saying, having the channel announcement point to a selected onchain output, was fairly dangerous for privateness and that we might in all probability do better. So, those are issues that we’ve always been simply hand-wavy about how we'd do that in the future. Read More: Amid value drops and increased regulation, what’s the way forward for cryptocurrency?

But I don’t think we’ll help you have any type of multiplier, as a result of certainly one of the other ideas was that you can additionally simply announce some UTXOs that you just own, with the proof that you just personal them, with a complete value of, for instance, 2 bitcoin, and then that might grant you the flexibility to announce up to X instances that in channels with out having to point to any particular onchain output. I didn’t assume it was too dangerous, however the one key difference here is that for the payment channels with penalties as at present designed, it’s necessitating that you simply store these secret nonces eternally till channel shut. These charts are cardinal part of the entire affair as with them traders are able to foretell the motion near accuracy. But, figuring out that the markets by no means shut is a useful safeguard to have. If in case you have another Lightning-like channel specification that you simply coded up or a custom channel type, it's also possible to embrace that on this channel announcement and it will just work. That’s why we’re not doing that right now, and that’s why most people will simply keep saying the output that actually corresponds to the channel so that when it will get spent, people actually discover it and can take away it from that graph and know that they cannot route through that channel anymore.

I believe we’re going to follow a easy version, where you allow pointing to any type of output to pay to your channel. PTLC fixes that by ensuring that as an alternative of using the preimage of a SHA256 hash and its hash, we’re going to make use of elliptic curve points and their non-public keys. This could seem unnecessary provided that BIP32 already provides extended personal keys (xprvs) that can be shared between signing wallets. Maybe we can begin with t-bast. Can the channel keep open when the UTXO gets spent? And alternatively, how do you ensure that the same UTXO isn't reused for the announcement; and what occurs if that UTXO will get spent? So, will we should be holding observe of the UTXO actually not being moved while it is the stand-in to have introduced the channel? Mike Schmidt: The taproot and MuSig2 channel discussion somewhat leads into the updated channel announcement discussion and how gossip protocol would have to be upgraded with the intention to assist shifting to P2TR outputs. So, we want to alter that, as a result of we want to allow taproot, which implies permitting additionally input, particularly if we use MuSig2; we don’t need to reveal the interior keys.

And right now, it’s going to make use of the identical fee hash with all these nodes, which implies that if someone owns two of the nodes in the path, they are learning information, and this is unhealthy for privateness. Right now, whenever you send a payment, this fee is going to go through multiple nodes on the network. Bastien Teinturier: Sure. So proper now, once we introduced the channel on the community, we explicitly announced node IDs and the Bitcoin keys that are inside the multisig 2-of-2, and 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 may solely use it with scripts that basically follow the format of Lightning channels without taproot. Mike Schmidt: Murch or t-bast, another comments on taproot and MuSig2 channels? Mike Schmidt: Go ahead, 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.