switck/libngu: one key, two names
dylanleclair1-switck-key-attribution
https://gist.github.com/dylanleclair1/67d160af313be59851b88d1a81f0d762
- Organisation
- dylanleclair1
- Evidence role
- Independent primary analysis
- Published
- 2026-08-05
- Source changes
- 0
- Detected differences
- 0
- Unreviewed
- 0
- Copies held
- 1
Attribution argument that the pseudonymous GitHub account switck and Peter D. Gray of Coinkite are one person, resting on a 2020 public exchange read through the GitHub API and on local GPG verification said to show 58 Switck-authored commits carrying valid signatures from Gray's personal key. It then traces commit f19de05, which introduced the STM32 random-number code with the defective guard, to COLDCARD's seed generation. The gist ships a verify.sh so the signature checks can be re-run independently, which is why it is registered as primary work rather than as commentary. Its own text declines to state intent and calls the guard error an ordinary C mistake. The identity attribution, the elimination of alternative explanations and every inference drawn from the commit history are the author's claims, not verified here, and registration is not endorsement of them. This gist is the underlying artefact for the allegation preserved at reddit-switck-identity-claims. The publishing account is recorded as published; this archive does not assert who is behind it. Six revisions within 80 minutes of creation, so it is watched.
Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
Skip to content Search Gists Search Gists All gists Back to GitHub Sign in Sign up Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} Instantly share code, notes, and snippets. dylanleclair1/libngu-one-key-two-names.md Last active August 5, 2026 19:08 Show Gist options Download ZIP Star 1 (1) You must be signed in to star a gist Fork 0 (0) You must be signed in to fork a gist Embed Select an option Embed Embed this gist in your website. Share Copy sharable link for this gist. Clone via HTTPS Clone using the web URL. No results found Learn more about clone URLs Clone this repository at <script src="https://gist.github.com/dylanleclair1/67d160af313be59851b88d1a81f0d762.js"></script> Save dylanleclair1/67d160af313be59851b88d1a81f0d762 to your computer and use it in GitHub Desktop.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
Compare the screenshot or a quotation against the original while it is available.