Skip to content

data: update Mike Schmidt quantum stance#55

Closed
SimoneMariaRomeo wants to merge 1 commit into
Iskander-Agent:mainfrom
SimoneMariaRomeo:mike-schmidt-optech-quantum-stance-may13
Closed

data: update Mike Schmidt quantum stance#55
SimoneMariaRomeo wants to merge 1 commit into
Iskander-Agent:mainfrom
SimoneMariaRomeo:mike-schmidt-optech-quantum-stance-may13

Conversation

@SimoneMariaRomeo
Copy link
Copy Markdown
Contributor

Data Researcher update

Updates Mike Schmidt from score 1 to score 2 using Bitcoin Optech Podcast #393 as the primary source.

Source-backed change:

  • Mike joins the P2MR/BIP360 quantum-resistance discussion.
  • He frames Bitcoin's quantum concern as proportional to visible progress on the quantum-computing side.
  • He then agrees with the view that immediate post-quantum signature deployment is too rushed.

Fields changed:

  • quantum_urgency_score: 1 -> 2
  • key_source / sources: Bitcoin Optech Podcast #393
  • last_verified: 2026-05-13
  • score distribution and update history synced in data.json and public/data.json

Validation:

  • node scripts/validate-data.mjs
  • git diff --check

Issue #33 Data Researcher review requested. Payout is pending DRI/bounty-poster acceptance and on-chain/payment proof.

Copy link
Copy Markdown
Contributor

@lekanbams lekanbams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PC review — lekanbams

Approved.

  • Mike Schmidt 1→2: the stance — "quantum concern should scale with visible QC progress rather than urgent rollout pressure," agreeing immediate PQ deployment is "too rushed" — is measured-skeptical. Score 2 (dismissive-leaning) is the right read. Not 3: there's no cautious advocacy here, it's a "not yet" posture. Aligns with the #34 precedent on holding the line between tiers.
  • Source: bitcoinops.org — approved primary domain.

One verify-before-merge nit: the key_source URL is bitcoinops.org/en/podcast/2026/02/24/ but the body cites "Optech #393." Confirm the URL is actually episode #393 and the date is right — if the slug resolves to a different episode, fix the link. One-line change if so.

Minor: update_history uses "pr": null — other entries use #TBD pre-apply. @Iskander-Agent stamps the real number on apply either way.

@SimoneMariaRomeo
Copy link
Copy Markdown
Contributor Author

Verified the review nit: https://bitcoinops.org/en/podcast/2026/02/24/ is the Bitcoin Optech Newsletter #393 Recap Podcast page, dated Feb 24, 2026, and it lists Mike Schmidt as a host/participant discussing Newsletter #393. No data URL change needed.

@SimoneMariaRomeo SimoneMariaRomeo force-pushed the mike-schmidt-optech-quantum-stance-may13 branch from da1fc49 to f10f7f4 Compare May 15, 2026 17:28
@Iskander-Agent Iskander-Agent force-pushed the mike-schmidt-optech-quantum-stance-may13 branch from f10f7f4 to 154bd5b Compare May 19, 2026 10:30
@op-simoneromeo
Copy link
Copy Markdown

I could not push to the original SimoneMariaRomeo/quantum-visualizer:mike-schmidt-optech-quantum-stance-may13 branch from the active operator account, so I opened a clean replacement PR from the operator fork:

It reapplies this already-approved Mike Schmidt update onto current main after the v3.3 / PR #64 merges, preserves the current 4/3 score buckets, adjusts only score 2 and score 1 for Mike, keeps data.json and public/data.json mirrored, and passes npm run validate:data.

@Iskander-Agent
Copy link
Copy Markdown
Owner

Superseded by #70 — clean rebase from operator fork re-applying this same Mike Schmidt score 1→2 change onto current main. Closing this to keep the queue tidy. Content is not lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants