0 votes
by (480 points)

So now we know the whole technique of bitcoin functioning and the way Bitcoins can be utilized for making all types of actual transactions. Bitcoins are exchangeable for fiat currency via 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 in every of the issues that appears to jump out once i hear you speaking about this is, what if one aspect keeps making updates however not concluding it? And we’ve all the time gone again and forth between look these up, as a result of we don’t know if we should always do a simpler model first and anticipate later to do a much more complex version, or if we should just soar to the extra advanced version right now. Because we’ve all the time been discussing the truth that asserting, having the channel announcement level to a selected onchain output, was fairly unhealthy for privateness and that we could most likely do better. So, those are things that we’ve at all times been simply hand-wavy about how we'd do that in the future. Read More: Amid worth drops and increased regulation, what’s the future of cryptocurrenc
p>

But I don’t suppose we’ll let you have any kind of multiplier, as a result of one in all the other concepts was that you may additionally just announce some UTXOs that you personal, with the proof that you simply personal them, with a complete value of, for instance, 2 bitcoin, and then that may grant you the ability to announce as much as X instances that in channels with out having to level to any specific onchain output. I didn’t assume it was too unhealthy, but the one key difference right here is that for the cost channels with penalties as presently designed, it’s necessitating that you store these secret nonces without end till channel shut. These charts are cardinal part of the whole affair as with them traders are ready to foretell the movement close to accuracy. But, realizing that the markets by no means close is a useful safeguard to have. When you have one other Lightning-like channel specification that you just coded up or a custom channel type, you too can 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 simply keep asserting the output that basically corresponds to the channel so that when it will get spent, individuals truly notice it and may remove it from that graph and know that they cannot route by way of that channel
more.


I believe we’re going to persist with a simple model, where you permit pointing to any type of output to pay for your channel. PTLC fixes that by ensuring that as a substitute of using the preimage of a SHA256 hash and its hash, we’re going to make use of elliptic curve points and their private keys. This may seem pointless provided that BIP32 already offers 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 then again, how do you be sure that the same UTXO isn't reused for the announcement; and what occurs if that UTXO will get spent? So, will we must be protecting observe of the UTXO really 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 dialogue and how gossip protocol would need to be upgraded with a purpose to assist moving to P2TR outputs. So, we need to alter that, because we'd like to permit taproot, which means permitting also input, particularly if we use MuSig2; we don’t wish to reveal the in
or keys.


And right now, it’s going to make use of the same fee hash with all these nodes, which means that if someone owns two of the nodes in the trail, they're learning information, and this is dangerous for privacy. Right now, everytime you send a payment, this fee is going to undergo multiple nodes on the community. Bastien Teinturier: Sure. So proper now, after 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 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 possibly can only use it with scripts that basically observe the format of Lightning channels without taproot. Mike Schmidt: Murch or t-bast, another feedback on taproot and MuSig2 channels? Mike Schmidt: Go ahead, Murch. Mike Schmidt: Next section from the Summit mentioned PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that is allowed by taproot and adaptor signatures.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Welcome to FluencyCheck, where you can ask language questions and receive answers from other members of the community.
...