calle

Thank you for working on Bitcoin. Seriously.

Fiat money and the system of control they've built around it is terrifying and it will never loosen its grip around our necks.

If we don't save ourselves, noone will. Thank you for helping.

just sold for 21 sats, in for the tech

https://nonfungible.cash/market/86a16a8c41236edc5ba6899dcca4c8c5

the NFT is in the JPG

https://nonfungible.cash updates

• improved builtin cashu wallet
• filter market offers
• profiles support banner images https://blossom.primal.net/acb28277ccc6a13a933d030d1c109e26e8ed511eccb70c2de3a567c89a5f42b9.png

gm

www.deusaderit.com/gothicc https://blossom.primal.net/0d90ba1518e69dc1f93390e0d8b985e488d0044a575eb82e80c52c8eb1fb2602.png

bitchat 2 is available now https://blossom.primal.net/3ae0e7ca8bcbcc5bd03070e08ac46949e7d01cd6e8b5781c07e301d7123a2c4f.png

2 years ago me and the boys on a secret crypto gist on github trying to put the htlc into an ecash token so that the mint would never have to hold customer funds.

turns out it's the same problem as doing JPGs. we got it boys! https://gist.github.com/callebtc/41f8a3bb678f40d6886613e5d31342fd https://blossom.primal.net/99972a0c63060cf4185ea0bcb564b48fce3cad17ab1010bd2ca587bc1dea3ebf.png

"it would be nice if we can somehow find a way"

n o n f u n g i b l e . c a s h https://blossom.primal.net/a5867daa1d43abdeadba5da62f7a882d1f8c65805ced90aba2df2d3be155e10a.png

HELL YEAH I GOT IT

you can now login with your npub

https://nonfungible.cash/p/50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63

find my nuts on yahoo

https://tech.yahoo.com/ai/apple-intelligence/articles/send-bitcoin-offline-device-via-110823492.html

has anybody already built a free version of pocket, the article bookmarking and reading app that dissapeared?

• browser extension to save a link
• article text gets parsed automatically
• stored somewhere in the cloud or on nostr
• web, ios, android apps to read all your stored articles
• bonus: social features to share articles, follow other user's bookmarks
• bonus: text to speech via open source TTS models
• bonus: TTS transcriptions are shared between users once created

While I'm at it – another proof that nostr devs aren't serious about adoption is still the lack of key rotation.

I get it. It's a big task and can't be solved by any individual client, it needs to be addressed on a protocol level. I'm also aware of the that were put forward. But you know what? Writing markdown and pushing it to the nips repo isn't enough. It's step 0.

This is a typical issue that would require devs to come together and all pull in one direction. It likely would have needed a champion who is willing to push for this change, talk to people, explain it to everyone, and actually care. Similar to how we push for bigger changes in the Bitcoin protocol. It takes time, and it takes a serious effort. Once again, nobody has taken over that role because nobody really cared enough.

Back in the day, there were massively big users who would've loved to join nostr – but didn't do it because of a lack of key rotation. Why would anyone with so much to lose join a protocol that can permanently rekt your identity with a simple XSS bug that exposes your nsec? Nobody listened to them.

This was brought up over, and over, and over again. Nobody cared enough.

Liquid hack explained.

Liquid has confidential transactions that hide the amounts for improved privacy. A bug in how these transactions are validated caused inflation of Liquid BTC (L-BTC) and allowed hackers to empty the entire side chain.

Liquid nodes don't see the amounts of a confidential transaction, so to make sure that the transaction is still valid and doesn't cause inflation nodes check something called a balance proof and a range proof.

The balance proof establish that sum of the input amounts equal the output amounts, i.e., that "x L-BTC going in and x L-BTC going out". But there's a catch. Only relying on a balance proof isn't enough. You also need the range proof.

The range proof establishes that a hidden output amount falls within a positive range. That means a valid output must be at least 1 L-sat and at most 2^64 − 1 L-sats. Range proofs make sure that you can't mint "negative L-BTC".

Why is this even necessary? Remember, the amounts are hidden and a hidden negative amount would allow extra positive outputs to balance against it. Without a range proof, a transaction could say "I've put 1 L-BTC in, and I'm taking two outputs out: one with 4000 L-BTC and one with -3999 L-BTC)."

This is going to cause a disaster in a little bit.

Once the balance proof, the range proof, and other validations pass, a transaction is regarded as valid and can pass consensus. However, because especially the range proof is computationally expensive, Liquid nodes cache the result of a successful range proof in memory. Essentially, the node remembers "I saw this range proof before and it was valid, all good!".

In order to recognize the same range proof later on, you need to assign a label to it. This is called a cache key. This cache key is the actual cause of the bug.

The way this cache key was constructed allowed two different transactions to collide on their cache key. Essentially, one valid transaction (1 L-BTC in, 1 L-BTC out) had the same cache key as an invalid transaction (1 L-BTC in, 4000 L-BTC out).

Here's the hack: the attackers submitted the valid transaction (1 L-BTC in, 1 L-BTC out) first. Liquid nodes verified this transaction successfully, created a cache key called REKT and stored it in their cache. Then the attackers carefully crafted a second invalid transaction with (1 L-BTC in, 4000 L-BTC out) that created the same cache key REKT.

Instead of validating the second transaction and realizing that it printed money out of thin air, Liquid nodes found it in their cache and said "hey I saw this transaction before, everything is fine" and that caused the inflation.

The attackers then took their 4000 L-BTC and withdrew 4000 BTC onto the Bitcoin base chain.

I'm amazed someone would buy this crap but hey, I'm all for it, hope the price goes up a little more

I'm probably in nostr's top 0.01% users but this is one of the reasons I come back less frequently than I used to.

you can talk about permissionlessness as much as you want, but you can also simply choose not having to deal with a bunch of assholes on a daily basis.

nostr is full of reply-guy psychopaths that you can't block and there isn't a single client where muting works reliably, let alone across apps

10 likes gets you into the primal 24h trending list now!

gm

gm

Gm

, just curious, do you sometimes still write Bitcoin stuff?

runs on nostr https://blossom.primal.net/f39f5c3637dce519ffa0f77cd08ca7120fa0febd2c37d9a49f5f4f788280df52.png

anyone still here?

gm

starting in 5 mins!

Without Lightning, none of the Layer 2s make sense.

Without it, every Layer 2 would be a useless silo and a centralization vector.

Maybe Lightning was Bitcoin's Layer 3 all along.

CLN action priority list:

• restart with —offline
• if you can’t, turn off
• if you can’t, pray

If you can, restart with --offline.

If you can't, I would turn it off instead of doing nothing.

Restart your CLN node with --offline and keep an eye out for updates.

Note that shutting it down for too long can expose you to force closure risk. Starting it with --offline will still observe the chain for malicious channel closures.

this too shall pass 🟥

🟥 URGENT: Critical vulnerability in Core Lightning

Blockstream developers urge users to shut down CLN Lightning nodes right NOW!

Please let everyone know!

nostr on the front page of Hacker News

and of course it's funny

https://news.ycombinator.com/item?id=49399722

insane

can you use this for your brain?

we're all bitcoin red team

https://divine.video/u/tacobell

has an npub omfg

cashu .me is now fully integrated with the latest version of npub .cash – that means your lightning address now works across all mints

settings -> Lightning address -> choose your mint

thank you

nuts on the radio

why humans should not code in c: we're finding memory-safety vulnerabilities in c projects that are prevented by default in many other languages.

in the past, finding a simple buffer overflow wasn't enough. you'd need a highly skilled hacker to turn the vulnerability into a working end-to-end exploit.

today, that's a single prompt.

gained a ton of new insights working in bitcoin red team 🟥 that i wish i could share without vague posting. but this is what i got anon.

• we’re experiencing a massive collision between decades of human open source slop against 2 weeks of kimi k3 (not good)
• everything is broken, bitcoin is burning
• bitcoin is becoming stronger through this
• bitcoin is the obvious first target but the rest of the world will follow shortly
• sometimes old things need to burn so new things can grow on healthy soil
• humans should never code in c (just stop)
• lightning is complicated and is more broken than the average (sorry)
• verification is free. we used to complain about slop PRs. then about slop security audits. if you can’t handle the information overload, stop complaining and use AI to sort through it.
• those projects that started AI audits months ago are in a completely different position than those who didn’t
• projects need their own AI audit pipeline going into the future
• the burden for a developer to keep software safe and secure is pretty stressful and not for everyone. it has become a lot more stressful now.
• unmaintained projects are most probably broken, don’t rely on them. i’d rather one-shot it myself with a modern AI
• multiple concurrent, diverse human approaches have proven to be the best vulnerability search method
• external red teaming will probably have to continue forever
• we’ve basically completed a basic scan of virtually the entirety of bitcoin open source. the low hanging fruit is done.
• we’ve reported a ton of real critical and high vulnerabilities. project maintainers across the board have validated our findings.
• response speed is very different across projects and shows how healthy each project is. i recommend acting fast these days.
• red team etiquette matters. if you don’t disclose responsibly, boast on twitter about your findings on a particular project, or make indications about the nature of particular findings, you’ve disqualified yourself as a serious security researcher. trust is the most important factor in this game. if you lose it, it’s very hard to win it back.
• did i mention that humans should not code in c?