that blog was dope 🎶

Wow. Runs

wow. i dont write code that sloppily for my side projects, let alone at work, let alone on software this critical. “runs” unbelievable.

Crypto and stocks can be overwhelming, but Craig's education-first mindset changed everything. Guided by patience, technical analysis, and disciplined execution, my portfolio grew from $30K to $120K in less than two weeks. Every trade had a purpose, every investment had a plan, and every result refl...

Even if the code analysis is correct, i wouldn't blame the developer: the process failed in this case. Who reviewed and approved this code? What kind of guardrail and testing the change was submitted into? Why the implementation wasn't reviewed by an expert cryptographer

Not to justify things, but this was in front of everyone's eyes for 5 years. Therefore I assume: a) nobody looked at it, b) some looked at it and didn't bother to further investigate, c) some looked at it, investigated, and the findings were quietly buried. I.e., it was known but inconvenient to ac...

One thing I appreciate about paul is that he teaches patience and risk management instead of chasing quick profits. That mindset completely changed the way I approach trading, and I've seen much better consistency because of it. https://blossom.primal.net/fd85235345f2e61f76349123d3c7ec3c8c86568d...

https://primal.net/e/nevent1qqsdvndzsa9tgr7vur4uweqahs8l5xvfd49s80a20l0p7rjs8qeg29csyw07x

This is troubling: From here, I assume in a bout of frustration, he set `MICROPY_HW_ENABLE_RNG` to 0, which would have resolved the compiler error.

We were all trusting that someone had verified. Meanwhile, the whole thing was a clown car built by the intern who knew how to write Python but not C.

Working with Craig has been one of the most rewarding experiences in my trading journey. He doesn't encourage shortcuts or unrealistic expectations. Instead, he teaches discipline, market understanding, and proper risk management. Thanks to his guidance, I grew my $30,000 investment into $90,000. If...

Brutal.

Fake it till you make it gone wrong 🙈

nostr:npub1rtlqca8r6auyaw5n5h3l5422dm4sry5dzfee4696fqe8s6qgudks7djtfs is everywhere https://image.nostr.build/9d3b5fba56605fb410d001fed802b0e2c1293cdf6065b098a1cef6b663f11b3c.jpg

I read the entire article. My first pass opinion: Hardware Wallet Co's should not even be using hardware that offers a low / fake entropy option to a C Programmer. Use the correct entropy source or your compile fails. There should be no "fallback" option, e.g. yasmarang or whatever.

So we all trusted someone checked the software. What other critical software is running out there we all trust and no-one really checked?

Holy fucking shit. If this isn't negligence I don't know what is.

What I dont understand is, in an industry so focused on security, how did this go unnoticed? I mean, it looks to me like basic software engineering principles were neglected, so why was that not noticed? It might very well be that its a "hindsight is 20/20" kind of thing, but it just doesnt seem li...