- This topic is empty.
September 29, 2023 at 2:48 am #2788antonettaderryGuest
<br> Bastien Teinturier: Sure. So right now, when we announced the channel on the network, 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 those two keys, so you can only use it with scripts that really follow the format of Lightning channels without taproot. So, we need to change that, because we need to allow taproot, which means allowing also input, especially if we use MuSig2; we don’t want to reveal the internal keys. And they’re going to be tweaked at every hop, which means that even if you have multiple nodes that are on the path of the same payment, it’s not going to be payment hash, you’re going to see a different point, 바이낸스 – our source, a different secret than in both nodes. Right now, whenever you send a payment, this payment is going to go through multiple nodes on the network.
And we’ve always gone back and forth between those, because we don’t know if we should do a simpler version first and wait for later to do a much more complex version, or if we should just jump to the more complex version right now. So, you can point out any output that has sufficient funds to have basically funded that channel; I assume that means enough or more. Because we’ve always been discussing the fact that announcing, having the channel announcement point to a specific onchain output, was quite bad for privacy and that we could probably do better. But I don’t think we’ll allow you to have any kind of multiplier, because one of the other ideas was that you could also just announce some UTXOs that you own, with the proof that you own them, with a total value of, for example, 2 bitcoin, and then that would grant you the ability to announce up to X times that in channels without having to point to any specific onchain output. So right now, the way channels are announced, it has to be specific 2-of-2 multisig, looks exactly like ln-penalty channels. The difficult problem with a distributed system like this is how to ensure everyone agrees on the records, so everyone agrees if a transaction is valid, even in the presence of malicious users and slow <br>o<br>.
Every transaction pays a 1% fee, and existing Grumpy shareholders receive a payment automatically. And right now, it’s going to use the same payment hash with all these nodes, which means that if someone owns two of the nodes in the path, they are learning information, and this is bad for privacy. The idea behind redundant overpayments is that when you are trying to send a big payment across the network, you’re usually going to split it across multiple routes because you won’t be able to find a single route that will be able to carry that whole payment in one go. A computer can only settle on the solution by trial and error, making multiple random guesses until it works. Furthermore, some who defend Bitcoin argue that the gold and banking sector – individually – consume twice the amount of energy as Bitcoin, making the criticism of Bitcoin’s energy consumption a nonstarter. They will charge you when you are making a crypto transaction. Therefore, every single transaction ever made is detailed and verifiable. Thus, a transaction commences only if there is spendable balance i<br>e<br>llet.
Likely not. Thus, Bitcoin’s value is inextricably tied to arbitrary details of history – hardly something that can be called “intrinsic”. Anyone in the world can pay anyone else in the world any amount of value of Bitcoin by simply transferring ownership of the corresponding slot in the ledger. Unlike previous financial market sell-offs, when cryptocurrencies have been largely untouched, the selling pressure in these assets this time around has undermined the broader argument that they are dependable stores of value amid market volatility. There are two research papers that have proposals on how to do that by modifying the scripts that we use in the corresponding output in the commitment transaction. For a transaction to be posted to the ledger, a problem that is difficult to solve but easy to verify must be computed. But there are a lot of degrees to how much, how more decorrelated we<br>ld make it.