When random.bytes() runs but doesn't work
The more lines of code that you change, the more comments explaining why you’re changing the code. More message and less code changes per commit is generally a good idea.Here is an example chosen randomly from some of my own work.The commit message is 235 characters, and the commit changes 15 lines of code. Setting this value to zero tells the default micropython rng code to not use the hardware RNG device and that it should use the Yasmarang RNG instead.
- ▪The more lines of code that you change, the more comments explaining why you’re changing the code.
- ▪More message and less code changes per commit is generally a good idea.Here is an example chosen randomly from some of my own work.The commit message is 235 characters, and the commit changes 15 lines of code.
- ▪Setting this value to zero tells the default micropython rng code to not use the hardware RNG device and that it should use the Yasmarang RNG instead.
Hacker News (Front Page) files mainly under programming. We currently carry 936 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Btcpp |
| Canonical URL | https://insider.btcpp.dev/p/when-randombytes-runs-but-doesnt |
| Publication time | Sun, 02 Aug 2026 02:08:26 +0000 |
| Retrieval time | 2026-08-02T03:28:55.512Z |
| Last seen | 2026-08-02T03:28:55.512Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | VTWOwmWXBs4P · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
OpEdWhen random.bytes() runs but doesn't workWhat a commit message tells us about the recent COLDCARD bugDusty DaemonAug 01, 20262232ShareThis is a guest post from noted Core-Lightning developer, ddustin, who dug into the Coldcard firmware commit history to uncover what happened and why the code failed.IntroI began investigating the Coldcard hack and was immediately shocked. I need to explain why.When we developers work on code, we organize or code changes into changesets we call “commits.” The purpose of doing so is to show a clear history of what code was changed including why and how.This is done precisely for instances like this where it appears Bitcoiner’s funds are being stolen en masse, so we can investigate and understand exactly how it could happen.Good developers write clear…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Btcpp.
Discussion
0 commentsMore from Btcpp
