anyone who joins in writing obituaries about the first example of a new technology but had the knowledge to potentially be able to build one is a coward.
this is why bitcoin wins. this is why lightning wins.
the people who are building it have courage, which means they have a heart and a soul.
the rest are just thin wisps projecting an image.
everywhere is just a few hundred yards off trail for a tomb raider advencha
zaps keep coming to my WoS, i don't think it's ded
they are selections, and distractions for the plebs to think they had a say.
nothing to see here, just more evidence that everyone in charge is a psychopath.
i was just thinking this this morning, looking at the increasing definition and size of my musculature and feeling the ache of having done the work to make it that way.
ok, when i need to quote myself because you didn't read what i wrote i know i don't need this conversation any further.
it may be that now but probably that also means the difficulty will now rise a lot to slow it down.
This attack isn't easy. Pulling it off involves:
- opening two channels with the victim.
- routing a payment through them.
- successfully replacement-cycling the victim's htlc-timeouts for Ξ blocks.
- without the victim discovering the htlc-preimage transaction.
jumping right on ahead to "omg, rare, extremely difficult attack that everyone knows about now means change bitcoin" is pretty ridiculous.
soundbites about how bitcoin and lightning are busted are beyond ridiculous in the light of the conditions laid out above. ONLY ONE OF THEM HAS TO BE BLOCKED. Unless I'm mistaken, when it says "open two channels" this means "with one key". SNIP, straight away easy to prevent. straight away, everyone who has something at stake is already sorting through their channels and force closing everything that is suspect looking just for that minimal element.
and since i know a bit about the signatures and ciphers and ECDH it smells to me like an error in the use of elliptic curves.
maybe it will require a substantial, minor version bumping change that is not backwards compatible but i don't think anyone is gonna be a hard sell on a well hammered out solution.
thanks nostr:nprofile1qqstm0smm0ymyk5d38v0mtctuxsdekphhtykj86e0zffqwjlmkrwylcpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshsuj20g3 for dropping the link, i hadn't followed that account on this new nym yet.
i told you it made me feel like shit.
thanks for illustrating that i'm not the only one in a bad mood tonight.
this HTLC thing is gonna get more intense.
but let me be very clear about something:
the email on the bitcoin dev mailing list does not explain in ANY WAY how the vulnerability can be exploited
it makes allusions to linux kernel vulnerabilities, which have nothing to do with anything
they are saying the problem is in the mempool, but this can only affect channel closures, and will have little material effect on processing payments because they either go, or they don't, and if one of the hops in a path publishes a malicious channel close then again, the payment will just fail at most.
we aren't hearing anything from actual devs who build the systems, nor the inventors, only people who are clear opponents and competitors to bitcoin.
this is psychological warfare, it smells fishy af in my opinion.
inflating the image of potency of something is a classic psywar technique, and we already have the word FUD for creating doubt to make people feel bad.
it only makes me feel mad, and i don't want to hear another word about HTLC vulnerability until someone actually explains because what is in the email is basically so vague as to be useless, and i actually have read the paper and i understand a reasonable amount about how the atomicity of lightning payments works and anything involving the bitcoin blockchain implicitly only affects channel closure.
it may well be that this vulnerability has to do with splicing.
but anyone who understands how the protocol works and how splices go off on a second and Nth level beyond on-chain transaction would get it when i say that splicing is something that probably should not be widely used at this point.
anyhow, FUD warning. they are coming for your zaps, people. it's not going to work, as far as i can tell this is a social engineering attack, with a thin wisp of a partial vulnerability, at best, in an uncommon aspect of LN protocol.
2 glasses of dry red wine with 550g of spit roasted beef, 500ml of lager beer an hour later.
nah, it was ok in that i didn't have my busted tooth go apeshit but this afternoon i'm extra sensitive to the cold and irritable and this is the only thing that is different between yesterday and all of the last 2 weeks.
i'm not ok with any at all, i don't want to feel like this, it's like being kicked in the nuts by an invisible man.
you also probably drink coffee, or even energy drinks. those also have gone out the window for me now 3 weeks. half a teaspoon of instant coffee the day before yesterday made evening suck.
i'm done with them all.
drugs are only for medical events and even then, if you have to use them twice in a year you have a diet and lifestyle problem. maybe an environment problem.
last night there was alcohol.
tonight i have a great disturbance in my happiness.
there will not be alcohol again, not even to "have the full espetada" experience.
i'll bring spring water.
for example:
i see you have the same fun comment spammer as me.
100% - the hardware should be completely open. it's so low requirement, really, a commodore 64 could do the job.
for the node, but not for the wallet.
there's been plenty of disagreement with the monolithic build of bitcoin core in this matter, but you can always just not use it.
even mere hundreds of kilometres away...