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

So now we know the entire technique of bitcoin functioning and how Bitcoins can be utilized for making all sorts of actual transactions. Bitcoins are exchangeable for fiat currency by way of 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 questioning, one of the issues that appears to leap out when i hear you speaking about that is, what if one aspect keeps making updates but not concluding it? And we’ve all the time gone back and forth between these, as a result of we don’t know if we must always do a simpler version first and look ahead to later to do a much more complicated model, or if we should always just leap to the extra advanced model right now. Because we’ve at all times been discussing the truth that asserting, having the channel announcement point to a specific onchain output, was quite unhealthy for privateness and that we may in all probability do better. So, these are things that we’ve all the time been just hand-wavy about how we would do that sooner or later. Read More: Amid value drops and elevated regulation, what’s the future of cryptocurrency?

But I don’t assume we’ll mean you can have any sort of multiplier, as a result of one of the other ideas was that you would additionally simply announce some UTXOs that you just personal, with the proof that you just personal them, with a total worth of, for instance, 2 bitcoin, after which that might grant you the power to announce up to X occasions that in channels with out having to level to any specific onchain output. I didn’t suppose it was too unhealthy, however the one key difference right here is that for the payment channels with penalties as currently designed, it’s necessitating that you store these secret nonces eternally until channel close. These charts are cardinal a part of the whole affair as with them traders are able to predict the movement close to accuracy. But, realizing that the markets by no means close is a useful safeguard to have. If you have one other Lightning-like channel specification that you coded up or a customized channel type, you can too embody 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 asserting the output that actually corresponds to the channel so that when it will get spent, resources individuals really discover it and may take away it from that graph and know that they cannot route via that channel anymore.

I feel we’re going to stick to a simple model, the place you allow pointing to any kind of output to pay in your channel. PTLC fixes that by making sure that as a substitute 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 pointless given 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 stay open when the UTXO gets spent? And alternatively, how do you ensure that the same UTXO shouldn't be reused for the announcement; and what happens if that UTXO will get spent? So, will we need to be protecting track of the UTXO actually not being moved whereas it's the stand-in to have introduced the channel? Mike Schmidt: The taproot and MuSig2 channel dialogue considerably leads into the updated channel announcement discussion and the way gossip protocol would have to be upgraded in order to help shifting to P2TR outputs. So, we'd like to alter that, as a result of we'd like to allow taproot, which suggests permitting additionally input, particularly if we use MuSig2; we don’t want to reveal the interior keys.

And right now, it’s going to use the same fee hash with all these nodes, which implies that if someone owns two of the nodes in the path, they're learning data, and that is unhealthy for privateness. Right now, everytime you ship a payment, this fee is going to undergo a number of nodes on the network. Bastien Teinturier: Sure. So proper now, after we introduced the channel on the community, we explicitly introduced node IDs and the Bitcoin keys which might be inside the multisig 2-of-2, and other people 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'll be able to only use it with scripts that actually comply with the format of Lightning channels with out taproot. Mike Schmidt: Murch or t-bast, another comments on taproot and MuSig2 channels? Mike Schmidt: Go ahead, Murch. Mike Schmidt: Next section from the Summit discussed PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that is allowed by taproot and adaptor signatures.