HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
GiancarloLelli
quantum
Python2026–2026
GiancarloLelli / quantum

quantum

This repository contains the code and submission detail for the QDay prize challenge by https://www.projecteleven.com/

3Distinct people
4Mentions
0Explicit recommenders
35GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This repository contains the code and submission detail for the QDay prize challenge by https://www.projecteleven.com/

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour4 dated mentions

Observed mentions: 2026-04-24 22:45:20 UTC to 2026-04-25 20:41:42 UTC.

012026-04-24 22:00:00 UTC to 2026-04-24 23:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 24, 22:002026-04-24 23:00:00 UTC to 2026-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 00:00:00 UTC to 2026-04-25 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 01:00:00 UTC to 2026-04-25 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 02:00:00 UTC to 2026-04-25 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 03:00:00 UTC to 2026-04-25 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 04:00:00 UTC to 2026-04-25 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 05:00:00 UTC to 2026-04-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 06:00:00 UTC to 2026-04-25 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 07:00:00 UTC to 2026-04-25 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 08:00:00 UTC to 2026-04-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 09:00:00 UTC to 2026-04-25 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 25, 09:002026-04-25 10:00:00 UTC to 2026-04-25 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 11:00:00 UTC to 2026-04-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 12:00:00 UTC to 2026-04-25 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-25 13:00:00 UTC to 2026-04-25 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 14:00:00 UTC to 2026-04-25 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 15:00:00 UTC to 2026-04-25 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 16:00:00 UTC to 2026-04-25 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-25 17:00:00 UTC to 2026-04-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 18:00:00 UTC to 2026-04-25 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 19:00:00 UTC to 2026-04-25 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 20:00:00 UTC to 2026-04-25 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 25, 20:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 24, 22:002026-04-24 22:00:00 UTC2026-04-24 23:00:00 UTC101
Apr 24, 23:002026-04-24 23:00:00 UTC2026-04-25 00:00:00 UTC000
Apr 25, 00:002026-04-25 00:00:00 UTC2026-04-25 01:00:00 UTC000
Apr 25, 01:002026-04-25 01:00:00 UTC2026-04-25 02:00:00 UTC000
Apr 25, 02:002026-04-25 02:00:00 UTC2026-04-25 03:00:00 UTC000
Apr 25, 03:002026-04-25 03:00:00 UTC2026-04-25 04:00:00 UTC000
Apr 25, 04:002026-04-25 04:00:00 UTC2026-04-25 05:00:00 UTC000
Apr 25, 05:002026-04-25 05:00:00 UTC2026-04-25 06:00:00 UTC000
Apr 25, 06:002026-04-25 06:00:00 UTC2026-04-25 07:00:00 UTC000
Apr 25, 07:002026-04-25 07:00:00 UTC2026-04-25 08:00:00 UTC000
Apr 25, 08:002026-04-25 08:00:00 UTC2026-04-25 09:00:00 UTC000
Apr 25, 09:002026-04-25 09:00:00 UTC2026-04-25 10:00:00 UTC000
Apr 25, 10:002026-04-25 10:00:00 UTC2026-04-25 11:00:00 UTC000
Apr 25, 11:002026-04-25 11:00:00 UTC2026-04-25 12:00:00 UTC000
Apr 25, 12:002026-04-25 12:00:00 UTC2026-04-25 13:00:00 UTC101
Apr 25, 13:002026-04-25 13:00:00 UTC2026-04-25 14:00:00 UTC000
Apr 25, 14:002026-04-25 14:00:00 UTC2026-04-25 15:00:00 UTC000
Apr 25, 15:002026-04-25 15:00:00 UTC2026-04-25 16:00:00 UTC000
Apr 25, 16:002026-04-25 16:00:00 UTC2026-04-25 17:00:00 UTC101
Apr 25, 17:002026-04-25 17:00:00 UTC2026-04-25 18:00:00 UTC000
Apr 25, 18:002026-04-25 18:00:00 UTC2026-04-25 19:00:00 UTC000
Apr 25, 19:002026-04-25 19:00:00 UTC2026-04-25 20:00:00 UTC000
Apr 25, 20:002026-04-25 20:00:00 UTC2026-04-25 21:00:00 UTC101

What Hacker News says

4 sources
The person who won the challenge with this apparently misleading code seems to have absolutely no quantum computing background. He writes this as background about himself: > Technology leader with 10+ years in enterprise software, full-stack architecture, and cloud-native development. Background in computer science with hands-on experience across .NET, Python, Rust, and Cloud ecosystems. Currently working as Cloud GTM Specialist focused on solution architecture and sales engineering. Looking at the commit history, this looks vibe coded: https://github.com/GiancarloLelli/quantum
In Replace IBM Quantum back end with /dev/urandom
Pasting my comment from the other article here - curious to understand the degree to which I'm understanding this. ---- The article itself is maddeningly vague on exactly what happened here. At first blush, it looks like the quantum computer was just used to generate random noise? Which was then checked to see if it was the private key? Surely that can't be. The github README [0] is quite extensive, and I'm not able to parse the particulars of all the sections myself without more research. One thing that caught my eye: "The key insight is that Shor's post-processing is robust to noise in a way that raw bitstring analysis is not." "This result sits between the classical noise floor and the theoretical quantum advantage regime. At larger curve sizes where n >> shots, the noise baseline drops below 1% and any successful key recovery becomes
Read the rest
strong evidence of quantum computation." So... is one of the main assertions here simply that quantum noise fed into Shor's algorithm results in requiring meaningfully fewer "shots" (this is the word used in the README) to find the secret? Someone help me understand all this. Unless I'm missing something big, I'm not sure I'm ready to call this an advancement toward Q-Day in any real-world sense. 0: https://github.com/GiancarloLelli/quantum
In Replace IBM Quantum back end with /dev/urandom
The article itself is maddeningly vague on exactly what happened here. At first blush, it looks like the quantum computer was just used to generate random noise? Which was then checked to see if it was the private key? Surely that can't be. The github README [0] is quite extensive, and I'm not able to parse the particulars of all the sections myself without more research. One thing that caught my eye: "The key insight is that Shor's post-processing is robust to noise in a way that raw bitstring analysis is not." "This result sits between the classical noise floor and the theoretical quantum advantage regime. At larger curve sizes where n >> shots, the noise baseline drops below 1% and any successful key recovery becomes strong evidence of quantum computation." So... is one of the main assertions here simply that quantum noise fed into
Read the rest
Shor's algorithm results in requiring meaningfully fewer "shots" (this is the word used in the README) to find the secret? Someone help me understand all this. Unless I'm missing something big, I'm not sure I'm ready to call this an advancement toward Q-Day in any real-world sense. 0: https://github.com/GiancarloLelli/quantum
In Bitcoin 'Q-Day' Draws Nearer as Quantum Researcher Breaks Simplified Key

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.