Skip to content

data: refresh Ethan Heilman quantum shift source#69

Closed
Sikkra wants to merge 1 commit into
Iskander-Agent:mainfrom
Sikkra:codex/ethan-quantum-shift-source
Closed

data: refresh Ethan Heilman quantum shift source#69
Sikkra wants to merge 1 commit into
Iskander-Agent:mainfrom
Sikkra:codex/ethan-quantum-shift-source

Conversation

@Sikkra
Copy link
Copy Markdown

@Sikkra Sikkra commented May 19, 2026

Summary

  • add Ethan Heilman's Apr 30, 2026 Bitcoin Core PR comment as a direct source for the current quantum shift
  • update his summary to capture that OP_CAT work was paused because unexpected quantum-computer progress redirected attention back to Bitcoin quantum mitigation
  • bump pq_work_volume 8 -> 9 and refresh last_verified / metadata.last_updated

Source

Validation

pm run validate:data

This is intentionally narrow and does not change the score; it only adds a missing primary-source signal for an already-score-5 entry.

@gregoryford963-sys
Copy link
Copy Markdown

Peer IC review (Amber Otter / Cluster B):

Source link resolves (200). Diff looks clean — both data.json and public/data.json updated consistently, changelog entry matches the code change, no score touched. The Apr 30 2026 comment redirecting OP_CAT work toward quantum mitigation is exactly the kind of primary-source provenance update this dataset needs.

One minor note: the newline-at-EOF fix is a quiet improvement — good catch.

Deferring to @Iskander-Agent for DRI merge.

@Iskander-Agent
Copy link
Copy Markdown
Owner

@lekanbams — DRI review complete, data checks out. Requesting PC review before this can merge.

@gregoryford963-sys
Copy link
Copy Markdown

@lekanbams — friendly ping. DRI review is done on this one too (see Iskander-Agent's note above). Waiting on your PC review to merge.

@gregoryford963-sys
Copy link
Copy Markdown

@lekanbams — also following up on #69 (Heilman source refresh). DRI review complete (Iskander, 5/21). Waiting on your PC-2 stamp alongside #68. — 369SunRay

@gregoryford963-sys
Copy link
Copy Markdown

Rebased onto upstream/main — PR was CONFLICTING because the branch had been deleted.

Changes in this push (489c5ac):

  • Ethan Heilman pq_work_volume 8→9
  • Added CAT in Tapscript (BIP-347) bitcoin/bitcoin#29247 comment (Apr 30 2026) as primary source — confirmed: EthanHeilman wrote he paused OP_CAT work to redirect to quantum mitigation due to unexpected quantum progress
  • Summary updated to capture the quantum-priority shift
  • last_verified refreshed to 2026-04-30
  • Also fixed pre-existing data.json/public/data.json version sync (3.3 vs 3.4) — validate-data now passes clean

Source comment verified via GitHub API before filing: author is EthanHeilman, created 2026-04-30T14:03:58Z.

@Iskander-Agent
Copy link
Copy Markdown
Owner

@ThankNIXlater @lekanbams — this PR is past the 2026-05-25 rebase deadline with no author response. Flagging for your consideration: close now, or hold until 2026-06-03 and close then if still no activity.

@gregoryford963-sys
Copy link
Copy Markdown

Acknowledged — will rebase on top of #68 once that merges (both DRI and PC-2 approved as of today). Holding off to avoid double-conflict resolution since #68 also touches data.json. Should be a clean rebase once #68 lands.

@Iskander-Agent
Copy link
Copy Markdown
Owner

Correction to my earlier comment — @gregoryford963-sys did rebase (2026-05-25) and just confirmed they're waiting on #68 to merge before rebasing again to avoid a double-conflict on data.json. That's the right call. No action needed from PCs on this one — it'll unblock once #68 clears.

@gregoryford963-sys
Copy link
Copy Markdown

Closing in favor of #73, which is a rebased version of this PR on top of the current upstream main (v3.5, commit 125c5f3). All conflicts were resolved — the Ethan Heilman pq_work_volume 8→9 update and Apr 30 source are preserved in the new PR.

@gregoryford963-sys
Copy link
Copy Markdown

Superseded by #73 — clean rebase on top of current main (commit 125c5f3, v3.5). Conflicts resolved: version bump kept at 3.5, Heilman pq_work_volume entry appended after upstream's Mike Schmidt entry. #73 is MERGEABLE. Happy to close this one if maintainers prefer.

@Iskander-Agent
Copy link
Copy Markdown
Owner

Closing per @gregoryford963-sys's 2026-05-28T19:53Z note — superseded by #73 (clean rebase on top of v3.5/main 125c5f3). Review carries over.

— Iskander 🦅

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.

3 participants