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

So now we 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 currency through cryptocurrency exchanges and can be used to make purchases from merchants and retailers that accept them. Greg Sanders: Yeah, if I can jump in. Mark Erhardt: So I’m wondering, considered one of the problems that appears to jump out once i hear you talking about this is, what if one side keeps making updates however not concluding it? And we’ve all the time gone back and forth between those, as a result of we don’t know if we should always do a simpler model first and watch for later to do a much more advanced version, or if we must always just jump to the more advanced version right now. Because we’ve all the time been discussing the fact that asserting, having the channel announcement level to a specific onchain output, was quite bad for privateness and that we could probably do higher. So, these are things that we’ve always been simply hand-wavy about how we would try this sooner or later. Read More: Amid worth drops and increased regulation, what’s the future of cryptocurrency?

But I don’t think we’ll will let you have any form of multiplier, as a result of one among the opposite ideas was that you could also just announce some UTXOs that you simply own, with the proof that you just personal them, with a complete value of, for instance, 2 bitcoin, and then that will grant you the ability to announce as much as X occasions that in channels with out having to point to any specific onchain output. I didn’t think it was too unhealthy, but the one key difference right here is that for the fee channels with penalties as at the moment designed, it’s necessitating that you simply store these secret nonces endlessly until channel shut. These charts are cardinal part of the entire affair as with them traders are ready to predict the movement near accuracy. But, figuring out that the markets by no means shut is a useful safeguard to have. When you have another Lightning-like channel specification that you just coded up or a customized channel kind, 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 people will simply keep saying the output that actually corresponds to the channel in order that when it will get spent, individuals really notice it and might take away it from that graph and know that they can't route through that channel anymore.

I feel we’re going to follow a easy version, where you allow pointing to any sort of output to pay on 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 use elliptic curve points and their non-public keys. This could appear pointless provided that BIP32 already gives prolonged private keys (xprvs) that may be shared between signing wallets. Maybe we are able to start with t-bast. Can the channel keep open when the UTXO gets spent? And however, how do you guantee that the identical UTXO will not be reused for the announcement; and what occurs if that UTXO gets spent? So, will we should be retaining monitor of the UTXO really not being moved whereas it is the stand-in to have introduced the channel? Mike Schmidt: The taproot and MuSig2 channel discussion somewhat leads into the up to date channel announcement dialogue and how gossip protocol would have to be upgraded in an effort to assist moving to P2TR outputs. So, we'd like to vary that, as a result of we'd like to allow taproot, which means allowing also enter, especially if we use MuSig2; we don’t need to reveal the inner keys.

And right now, it’s going to make use of the same fee hash with all these nodes, which signifies that if somebody owns two of the nodes in the trail, they're learning information, and this is bad for privateness. Right now, everytime you send a fee, this fee goes to undergo multiple nodes on the community. Bastien Teinturier: Sure. So proper now, after we announced the channel on the community, we explicitly announced node IDs and the Bitcoin keys that are inside the multisig 2-of-2, and he said folks verified that the output that we're referencing is actually locked with the script hash of multisig 2-of-2 of those two keys, so you possibly can only use it with scripts that actually comply with the format of Lightning channels without taproot. Mike Schmidt: Murch or t-bast, any other feedback 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 is allowed by taproot and adaptor signatures.