Replies (2)

Here’s a prioritized list of the most valuable search terms for scanning NVK podcast transcripts, show notes, and related audio: ### Highest signal (use first) - **libngu** / **LibNgU** / **lib ng u** - **switck** / **@switck** - **source code library** - **new source code library** - **“thanks to”** + library / switck - **yasmarang** - **MICROPY_HW_ENABLE_RNG** - **ngu.random** / **ngu.random.bytes** - **random.bytes(32)** - **hardware RNG** / **true RNG** / **TRNG** - **software PRNG** / **pseudo-random** - **seed generation** + rewrite / change / new - **entropy** + Coldcard / firmware / seed ### Strong secondary terms - **libsecp256k1** / **secp256k1** (especially with “moved to”, “switched to”, “we use”) - **Python wrapper** - **Trezor crypto** / **Trezor-derived** / **Trezor code** - **GPL** + remove / replace / rewrite - **Commons Clause** - **version 4.0** / **v4.0.0** / **firmware 4.0** - **major internal** / **all new code** - **BIP39** + replace / rewrite - **crypto library** / **crypto rewrite** - **DocHex** / **Peter** (in context of code or library) - **anonymous** / **pseudonymous** / **nym** + library / contributor ### Contextual / supporting terms - **reproducible builds** - **AES** + assembly / optimized - **SHA256** + optimized - **last remaining GPL** - **external library** / **third-party library** - **we have a** + wrapper / library - **our library** / **our wrapper** ### Suggested search strategy 1. Start with exact matches for **libngu**, **switck**, **yasmarang**, and **ngu.random**. 2. Then run broader searches for **“source code library”**, **“Python wrapper”**, and **libsecp256k1** + “we” / “our”. 3. Follow with **entropy**, **RNG**, **seed generation**, and **firmware 4.0 / v4**. 4. Finally scan for any mention of **Trezor** + rewrite/remove/GPL around early-mid 2021 dates. These terms give the best chance of surfacing any relevant quotes while keeping noise manageable.
.'s avatar
. 9 hours ago
There were two with Natalie Brunelle. One of them had my hair standing up. There was a backdoor type comment.