The other choice, send money on Binance will move the assets for the bank. So blinded path will be some kind of superior route boost where people can decide on whether they want to use it that way or not. But it’s really the recipient’s decision to whether they want to use it or not. So, you can run Jade on non-Blockstream hardware, and now with this HWI 2.3.0 release, you can also now use HWI with those DIY devices. And now, there’s binaries built for HWI for that particular setup. First one, HWI 2.3.0, which has a few items from the release notes that I think are worth talking about. The second item from the release notes was the ability to, within the GUI, import and export PSBTs to and from a file. Mark Erhardt: I think that there is some follow-up work for this release that is coming out soon, but I don’t know exact details. So, I guess it would be nice if it worked, but I see an attack vector there too. A raft of start-ups has been hawking what they see as a revolutionary solution: repurposing blockchains, best known as the digital transaction ledgers for cryptocurrencies like Bitcoin, to record votes.
For example, at least in Eclair and in Core Lightning (CLN), whenever you read an invoice and see some route hints in there between a pair of nodes, you use those channels in priority regardless of whether you have other channels to reach that destination between the – to reach that – well, no, I don’t remember. You would just include them in your blinded path, people don’t even have to know what channel this is, but you kind of force them to go to a direction where you know that there is liquidity. Bastien Teinturier: Yeah, and in a way, blinded path will just allow you to do that again because whenever you choose your blinded path, you can choose to make them go through your friend who wants to collect some fees through exactly the channels where you need them, when you know you have a lot of inbound liquidity and want to balance the channel. And in a way, blinded path makes that easier, because with blinded path, blinded path is a way to doing some route boost without actually telling people about the channels.
Yeah, this actually didn’t work because some senders did not prioritize the channels that were in the route hint. So, you could sort of ask that people route through specific channels because that one is especially lopsided and it would move the liquidity more in the direction that would balance out the channel, which would be a good thing. But on the other hand, it could also be used, for example, to prioritize channels where you need to balance your capacities. Mark Erhardt: I think that there might also be a couple of issues here with if you, for example, have one peer that you closely work with and you want to funnel more fees to, you could always route boost them and then make sure that they collect the fees rather than other peers you have, which may be sort of a downside of prioritizing boosted peers. But if you’re trying to replicate a hash by knowing when you know the input message before the hash, the pre-image, then it’s only a 128-bit security because you sort of have to find two things that produce the same digest rather than needing to replicate one digest. What does it mean that the security of 256-bit ECDSA, and therefore Bitcoin keys, is 128 bits?
If I’m understanding the reason behind that, it’s that the reason that sipa points out here, that there are known algorithms that are more effective than just brute-forcing 256-bit keys, so that it’s technically then 128-bit security; am I getting that right? Mike Schmidt: Last question from the Stack Exchange is, “What does it mean that the security of 256-bit ECDSA, and therefore Bitcoin keys, is 128 bits? Because, if you try to replicate a hash, an exact hash, without knowing the input, I think you do have 256-bit security. Mike Schmidt: The person asking this question was also asking about seed security and was maybe mixing up this 256-bit ECDSA versus 128 versus like the security of a seed, which sometimes can be 512. So, there’s some details in the answer on the Stack Exchange there. ” So, Murch, Bitcoin uses 256-bit ECDSA but 256-bit ECDSA only provides 128-bit security. I’m not doing a great job of explaining this right now, but yes, oftentimes there is a quadratic reduction of the security due to algorithms and what sort of attack model or 바이낸스 (find more information) threat scenario you’re applying, and I think this happens to be the case here. I usually go to sipa to ask him about that sort of stuff!
