Up In Arms About Bitcoin?
Download and install mining software: You’ll need to download and install mining software to connect your mining rig to the Bitcoin network and start mining. They would need to control a majority of the network to do this and insert it at just the right moment. So, we really need the protocol to be request response, where we can always have an opportunity to share nonces before we actually sign the transaction. And since this is request response as well, this makes it easy to share nonces for MuSig to taproot funding outputs. So in the end, you have two transactions that are negotiated with just one request and response, one where the initiator is paying the fee, 바이낸스 KYC 인증 – Recommended Looking at – one where the non-initiator is paying the fee, and each of them chose the fee they are ready to pay. And then the other party can either just reject that entirely by disconnecting, or can either also accept the fee that was proposed, or propose another fee inside the range that was proposed. And the other party can also say, “I want a transaction too, here is the fee I’m ready to pay. So, whenever you say that you want to mutual close your channel, the only one who is going to pay the fees for that is the party who initially opened that channel, so they don’t have an incentive, they really don’t want to overpay the fee.
So, if I’m the initiator and I want to close the channel, I’m going to say, “I’m closing that channel with that fee that is taken from my output. I will pay that fee. But if you play that game, the channel initiator will just blacklist you and you have to come up with a new node ID if you want to have channels with them, because force closing on someone is just, yeah, not a gentleman’s agreement. So initially, the first version of Lightning had a protocol for mutual closing channels that is still heavily in use, where we thought that having dynamic negotiation of a fee was a good idea. “. And you can have many rounds of exchanges like that, where it goes back and forth between the nodes, until you decide on what fee you want to apply to a mutual closing transaction. The first item that we have in the news list here is Simplified LN closing protocol. It sounds like this simplified protocol is two rounds. Mark Erhardt: I really like that the person that wants to close the channel now has to pay for it, because it always baffled me that the person that started the channel also had to pay the closing fee.
Why is the fee for the commitment transaction paid by the opener of the channel? Yeah, I don’t understand why the balance is not – well, I guess in the initial balance all of the balance is on the side of the opener and that’s why they have to pay the fees. And please just give me a signature where you won’t pay anything and I’m going to pay that fee so that we can RBF the mutual cost transaction”, which is also a good improvement because before that, I don’t think we had any way to do RBF right now. But the issue is that since this is automated, actually in implementations, it’s already decided from the start what fee you’re going to accept and what fee you’re going to reject, so this negotiation was not actually very useful, and it created a lot of issues between those that couldn’t agree on fees.
Nothing is latency sensitive here, so this really isn’t an issue. And Rusty Russell proposed this on the Lightning-Dev mailing list, and there’s also a PR open with some changes and unfortunately due to time-zone restrictions, Rusty isn’t able to join us to talk about his proposal. Rusty’s proposal was that instead of creating one transaction and trying to negotiate the fees on it, we would actually create two transactions, one for the channel initiator, one for the non-channel initiator, where each one decides how much fees they’re ready to pay and what fees are taken from their output. So, when you have a channel non-initiator, maybe you have more of an incentive to force close than to mutual close because this way it’s going to be the channel initiator that will pay the fees. Mark Erhardt: And this will always terminate, because the person that wants to close the channel, of course, already says, “Hey, I want to pay this amount and it’ll be taken from my portion of the channel”. And honestly, the communication is really not an issue here, because you are actually closing that channel, you’ve already decided that you want it to close it, so you’re not relaying any Hash Time Locked Contracts (HTLCs) on it.