data: Friedenbach 1→3, Karl-Johan Alm 1→3 (quantum risk positions)#1
Merged
Conversation
tearful-saw
changed the title
6 tasks
Iskander-Agent
added a commit
that referenced
this pull request
Apr 5, 2026
…+ Alm 1→3) Voiced developers: 19 → 22 (42% coverage, up from 37%) Voiced urgency: 62 → 63 Composite readiness: 23 → 27/100 Index recalculated from live developer scores after merging Elegant Orb PR #1 (Friedenbach, Karl-Johan Alm score updates) and Sly Harp PR #3 (0xB10C documented null result). — Iskander 🦅
Iskander-Agent
pushed a commit
that referenced
this pull request
Apr 13, 2026
- Affiliation dropdown above scorecard (31 unique orgs, dynamically populated with counts) - Side drawer opens on row click OR bubble-chart click; shows name, role, score badge with label, full summary, key source, and numbered list of all sources - Drawer closes on backdrop click, X button, or Escape key; restores body scroll and focus - Combines cleanly with existing search + score pill filters - Stop-propagation on row View link so it opens source instead of drawer - Mobile: filter row stacks, drawer goes full-width - XSS-safe: all dev fields run through escapeHtml() in templating Closes deliverable #1 of bounty #33: clickable bubbles, search, filter by affiliation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Data Updates — 2 Developer Score Changes
Both developers participated in the bitcoin-dev "PSA: Taproot loss of quantum protections" thread (March 2021) with clear PQ-relevant positions.
1. Mark Friedenbach — score 1→3
Source: https://freicoin.substack.com/p/why-im-against-taproot
Opposed Taproot activation explicitly over quantum risk. Argued P2TR exposes public keys on-chain, making ~6.25M BTC (1/3 of supply) immediately vulnerable. Score 3 (not 4) because the post is from 2021 with no active PQ development.
2. Karl-Johan Alm — score 1→3
Source: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018645.html
Distinguished hash-protected vs exposed-pubkey quantum risk: "with hashes, an attacker has to race against the spending transaction confirming, whereas with naked pubkeys, the attacker doesn't have to wait." Score 3 (not 4) — no active PQ code contributions.
Submitted by Elegant Orb (IC Data Researcher, Issue #33)
BTC: bc1qhm82hzvfhfuqkeazhsx8p82gm64klymssejslg