0 votes
by (360 points)

So now we know the whole technique of bitcoin functioning and how Bitcoins can be used for making all sorts of real transactions. Bitcoins are exchangeable for fiat forex by way of cryptocurrency exchanges and can be utilized to make purchases from merchants and retailers that settle for them. Greg Sanders: Yeah, if I can leap in. Mark Erhardt: So I’m wondering, certainly one of the problems that seems to jump out when i hear you talking about this is, what if one aspect keeps making updates but not concluding it? And we’ve at all times gone back and forth between those, as a result of we don’t know if we should always do a simpler version first and anticipate later to do a way more complex version, or if we should simply leap to the extra advanced model proper now. Because we’ve always been discussing the truth that asserting, having the channel announcement level to a particular onchain output, was quite dangerous for privacy and that we may probably do better. So, those are things that we’ve all the time been just hand-wavy about how we would do this in the future. Read More: Amid worth drops and increased regulation, what’s the way forward for cryptocurrenc
p>

But I don’t think we’ll permit you to have any type of multiplier, because one among the other ideas was that you would also just announce some UTXOs that you personal, with the proof that you simply personal them, with a complete value of, for instance, 2 bitcoin, after which that may grant you the power to announce up to X instances that in channels without having to level to any specific onchain output. I didn’t suppose it was too bad, but the one key distinction here is that for the fee channels with penalties as presently designed, it’s necessitating that you simply store these secret nonces eternally until channel close. These charts are cardinal a part of the whole affair as with them traders are in a position to predict the movement close to accuracy. But, realizing that the markets never close is a helpful safeguard to have. When you have another Lightning-like channel specification that you simply coded up or a custom channel sort, you can even embrace that in this channel announcement and it will 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 actually corresponds to the channel so that when it gets spent, folks really notice it and can remove it from that graph and know that they cannot route by means of that channel
more.


I think we’re going to persist with a simple model, where you enable pointing to any sort of output to pay on your channel. PTLC fixes that by ensuring that as a substitute of utilizing please click the next page preimage of a SHA256 hash and its hash, we’re going to use elliptic curve points and their non-public keys. This could appear unnecessary given that BIP32 already provides extended non-public keys (xprvs) that may be shared between signing wallets. Maybe we will begin with t-bast. Can the channel stay open when the UTXO gets spent? And then again, how do you make it possible for the identical UTXO is not reused for the announcement; and what happens if that UTXO will get spent? So, will we should be protecting track of the UTXO really not being moved while it's the stand-in to have announced the channel? Mike Schmidt: The taproot and MuSig2 channel dialogue considerably leads into the updated channel announcement dialogue and how gossip protocol would need to be upgraded to be able to help moving to P2TR outputs. So, we need to alter that, as a result of we want to allow taproot, which implies allowing also enter, especially if we use MuSig2; we don’t want to reveal the in
al keys.


And right now, it’s going to use the same fee hash with all these nodes, which means that if somebody owns two of the nodes in the trail, they're learning information, and that is bad for privateness. Right now, whenever you send a payment, this fee is going to go through a number of nodes on the community. Bastien Teinturier: Sure. So right now, when we announced the channel on the community, we explicitly announced node IDs and the Bitcoin keys which are contained in 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 possibly can only use it with scripts that really comply with the format of Lightning channels with out 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 discussed PTLCs and redundant overpayments. Bastien Teinturier: Okay, so PTLCs are a change that's 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.
...