He Took Credit for My Post-Quantum Cipher — Then the BBC Asked Him to Write the 1,847-Line Algorithm Live on Camera
Dr. Aris Thorne was in the university’s B-level server room on a Monday in January at 11:40 PM when the algorithm finally ran clean.
The algorithm was called SIEVE-9.
It was a post-quantum lattice encryption cipher built to resist attacks from NIST Category 3 quantum computers — the next generation of quantum hardware that would render current RSA and elliptic curve encryption obsolete.
The development had taken two years and four months.
The algorithm was 1,847 lines of Python.
She had written all of them.
She had written the lattice basis initialization — the mathematical foundation that defined the security geometry of the cipher.
She had written the key generation protocol — the function that produced cryptographic keys without a pattern that a quantum algorithm could exploit.
She had written the noise parameter logic.
The noise parameter was the hardest part.
In a lattice cipher, the noise parameter determines simultaneously the security margin and the performance ceiling.
Too little noise: the cipher is fast but theoretically breakable.
Too much noise: the cipher is theoretically secure but computationally impractical.
The balance function had taken six months.
She had worked through it with the Rotring 800 mechanical pencil on A4 paper before writing a single line of code.
The pencil had been in her shoulder bag since graduate school.
She had carried it into the server room every Monday night for two years.
The lead was 0.5mm B grade — soft enough to write dense mathematical notation without pressing hard.
She had replaced the lead cartridge three times in two and a half years.
She had replaced the eraser tip once.
The pencil itself was the same pencil.
The barrel was dented slightly on the left side where she had dropped it on concrete in her second year.
The mechanism still extended and retracted the lead cleanly.
She had checked it before every session.
The 14-page mathematical proof of the noise parameter balance function had been drafted over nine sessions.
Each session: server room, Monday night, A4 pad on the desk, pencil moving across paper, mathematical notation building left to right, the proof accumulating page by page.
Session 9 had concluded at 2:40 AM.
She had photographed each page with her phone.
She had transcribed the proof into the code comments on the Tuesday morning.
She had committed the code.
—
Simon Croft was her department head.
He was 56 and had been a cryptographer for 28 years.
He had attended the biweekly status meetings.
He had contributed two architectural suggestions in months 2 and 4.
He had contributed one note on the key generation logic in month 7.
He had not touched the code.
He had supervised the project.
He had signed off on every deliverable.
He had submitted the paper.
The paper said: Authors — Prof. Simon Croft, Dr. Aris Thorne.
She had accepted this.
She had known what it would mean.
She had not known what it would mean when the BBC called.
—
Simon had been in the server room on the night the algorithm ran clean.
He had been there for the 8 PM Monday meeting.
The meeting had been scheduled for one hour.
It had run until 11:40 PM because the final clean run required four more debugging iterations than projected.
When the terminal showed: SIEVE-9 v1.0 — No errors. Encryption verified. Decryption verified. Post-quantum resistance confirmed at 128-bit security margin.
Simon said: “We did it.”
Aris was at the keyboard.
She had been at the keyboard since 8:15 PM.
She looked at the terminal.
She looked at the pencil on the desk beside her keyboard.
She said: “The algorithm runs.”
She had not said “we.”
He had not noticed.
He was looking at the terminal.
She was looking at the pencil.
The pencil barrel was worn at the grip.
The dent on the left side was there.
The 0.5mm B lead was almost spent — she had been working through the last session’s calculations on the A4 pad while running the debugger between iterations.
She set the pencil down.
She saved the run log.
She closed the laptop.
She went home.
—
The paper was accepted by IEEE Transactions on Information Theory in March.
Simon had forwarded her the acceptance email.
He had typed: “Congratulations! Our moment!”
She had read “our moment.”
She had looked at her pencil.
She had put it in her bag.
She had gone to the server room.
She had run the algorithm one more time.
She had watched the terminal.
SIEVE-9 v1.0 — No errors.
She had closed the laptop.
She had gone home.
(Drop “ARIS” in the comments if you want to see what happened when the BBC asked Simon to write the cipher live on air.) 👇
She had known in October.
She had known that “Authors — Prof. Simon Croft, Dr. Aris Thorne” would be read as his paper.
She had submitted it because she was 35 and she was new to the department and Simon had been in the field for 28 years and she understood the cost of objecting.
She had made a choice too.
She had made a different kind of choice than Simon’s.
She had chosen to work within the structure and trust that the work would be visible.
The work had become visible.
Not in the way she had anticipated.
But it was visible now.
The terminal was showing: SIEVE-9 v1.0 — No errors.
She had closed the laptop.
She had gone home.
The BBC interview was recorded in April.
The program was “Science Horizons — The Future of Digital Security.”
The segment was 20 minutes on post-quantum cryptography.
The producer had reached out to Simon because Simon was the named first author and the department head and the person whose faculty profile appeared first in the university’s research directory.
Simon had agreed.
He had asked Aris if she wanted to attend.
She had said yes.
She had attended as a non-speaking researcher.
She had sat in the second row of chairs off camera.
The segment had aired in May.
Simon had spoken for 18 minutes.
He had used accurate vocabulary.
He had described “our algorithm.”
He had described “our approach to the noise parameter problem.”
He had described “the breakthrough in the key generation logic.”
He had described, accurately, what the algorithm did.
He had not described, accurately, who had done it.
He had not known the difference was visible until the BBC producer called him six weeks after the first segment aired.
—
The producer’s name was Cassandra Pierce.
She had received several emails from the cryptographic research community after the first segment aired.
The emails pointed to the IEEE paper.
The paper listed the authors in alphabetical order: Dr. Aris Thorne, Prof. Simon Croft.
Wait — she re-read the paper.
The authors were: Prof. Simon Croft, Dr. Aris Thorne.
Croft first.
The acknowledgments section said: “The lattice reduction function, noise parameter balancing logic, and key generation protocol were developed by Dr. A. Thorne. Prof. Croft provided architectural consultation during the initial development phase.”
Cassandra had read “architectural consultation.”
She had read “lattice reduction function, noise parameter balancing logic, and key generation protocol.”
She understood programming well enough to know that if you listed the three central functions of an encryption algorithm and attributed them to one person, that person had written the algorithm.
She called Simon.
She said: “We’d like to do a live follow-up segment. In the follow-up, we’d like to demonstrate the cipher. We’d like you to reproduce the core encryption function on camera.”
Simon said: “Reproduce it.”
She said: “Write it. On a laptop, live on air. Our editor wants to show viewers what post-quantum code actually looks like. 40 lines from the core function. Anything from the SIEVE-9 encryption routine.”
Simon looked at his desk.
He said: “I can certainly discuss the logic on camera.”
She said: “We’re specifically interested in the live demonstration. Our tech editor has suggested it would be the most engaging format for a general audience. A researcher writing encryption code in real time.”
Simon said: “When would this air?”
She said: “Live. Not recorded. The segment is part of our live programming on Thursday night.”
Simon said: “I see.”
He said: “Can I call you back?”
She said: “Of course.”
He put the phone down.
He looked at his computer.
He had 1,847 lines of SIEVE-9 source code on his hard drive.
He had read it.
He had reviewed it.
He had approved it before submission.
He had read “lattice reduction” and understood what it meant.
He had not written it.
He had never written lattice cryptography code.
He had not written Python professionally in six years.
He could write Python.
He could not write SIEVE-9 Python in front of a camera without the source file.
He was understood in the field.
He was not understood at a keyboard with an empty editor.
He looked at the phone.
He picked it up.
He called Aris.
He said: “The BBC wants a live follow-up. They want to see the code written on camera.”
She said: “Forty lines from the encryption function.”
He said: “You heard.”
She said: “I was in the room when you took the call.”
He was quiet.
He said: “Can you do it?”
She said: “Yes.”
He said: “Then I think you should be the one to appear.”
She said: “Okay.”
He was quiet again.
He said: “I’ll call Cassandra back.”
He called Cassandra.
He said: “Dr. Aris Thorne will be doing the live segment. She’s the primary author of the encryption function. She’s the appropriate person to demonstrate it.”
Cassandra said: “We’re happy to have Dr. Thorne.”
She said: “Can I ask — is she available to speak to our pre-segment researcher tomorrow?”
Simon said: “I’ll have her call you.”
He put down the phone.
He looked at his desk.
He had a 400-page draft on quantum resistance protocols.
He had been working on it for 18 months.
He had written it himself.
He had not used Aris’s code.
He had used her ideas.
He had attributed them properly in the footnotes.
He looked at the footnotes.
He called his editor.
He said: “I want to revisit the co-author conversation for the quantum resistance monograph.”
—
She had heard him take the call.
She had been at the secondary workstation in the research lab.
He had been in his office with the door ajar.
She had heard: “Live demonstration.” She had heard: “Write the encryption function.”
She had heard him say: “I can certainly discuss the logic on camera.”
She had heard the pause.
She had heard: “Can I call you back?”
She had known what the pause meant.
She had known before he said “can I call you back” that the next call would be to her.
She had turned back to her screen.
She had waited.
Three minutes later his door had opened and he had walked to her desk and said: “The BBC wants a live follow-up. They want to see the code written on camera.”
She had said: “Forty lines from the encryption function.”
He had said: “You heard.”
She had said: “I was in the room when you took the call.”
She had not said: and I knew.
She had not needed to.
The live segment was Thursday evening in June.
BBC Two. “Science Horizons.” 9 PM.
Cassandra Pierce met her in the lobby at 7:30 PM.
She said: “Thank you for agreeing to do this on short notice.”
Aris said: “It’s fine.”
Cassandra said: “The segment is 12 minutes. David will introduce you, describe the cipher briefly. Then he’ll ask you to write the encryption function. We need 40 lines from the core routine — not the key generation, not the noise parameter, just the main encryption loop. Is that accessible from memory?”
Aris said: “Yes.”
Cassandra said: “You won’t have the source file.”
Aris said: “I know.”
Cassandra said: “If you need to slow down, that’s fine. The editor can cut. But if you can do it at pace, that’s stronger.”
Aris said: “I’ll do it at pace.”
Cassandra looked at her.
She said: “Have you done live television before?”
Aris said: “No.”
Cassandra said: “Just look at the keyboard, not the camera. It’ll be fine.”
—
The studio had a main presenter desk, a floor-to-ceiling visualization screen behind it, and a secondary workstation at stage left.
The workstation had a standard university-spec laptop.
Aris set the Rotring pencil on the desk beside the laptop.
She did not need it tonight.
She had it.
The producer saw it.
She said: “Is that for calculations?”
Aris said: “Habit.”
The producer looked at it.
She said: “Actually, could we keep it in frame?”
Aris said: “Fine.”
The segment ran at 9:22 PM.
David Kamara said: “Tonight’s final segment is live. Dr. Aris Thorne, computational cryptographer at the University of Edinburgh, will write the core encryption function of SIEVE-9 from memory. SIEVE-9 is the post-quantum cipher developed at Edinburgh that has drawn significant attention from the cryptographic research community. Dr. Thorne is the algorithm’s primary author. Dr. Thorne.”
He had said “primary author.”
He had read the pre-segment briefing document.
The briefing document had been prepared by Cassandra’s researcher.
The researcher had read the IEEE acknowledgments.
The acknowledgments said: “The lattice reduction function, noise parameter balancing logic, and key generation protocol were developed by Dr. A. Thorne. Prof. Croft provided architectural consultation during the initial development phase.”
The briefing document said: “Note: Dr. Thorne appears to be the primary developer of the cipher despite appearing as second author on the paper.”
David had read the note.
He had said “primary author” without checking with the segment producer first.
He had said it because the acknowledgments made it obvious.
Aris heard “primary author.”
She turned to the keyboard.
She had the pencil to the left of the laptop.
She started typing.
—
She typed from the function header.
She typed the lattice initialization block.
She typed the element selection loop.
She made one error in line 19 — a misplaced colon in the conditional statement.
She caught it on the next line when the structure didn’t close correctly.
She backspaced two characters.
She corrected it.
She continued.
She typed the encryption transformation block.
She typed the output formatting.
She typed the verification call.
She typed the final return statement.
She stopped.
David said: “Can you run it?”
She said: “Yes.”
She typed: python sieve9_live.py
She pressed Enter.
The terminal ran.
The output appeared: SIEVE-9 Core Encryption — No errors. 128-bit security margin confirmed.
David said: “That ran.”
She said: “Yes.”
He said: “You wrote that from memory.”
She said: “Yes.”
He said: “How many lines is the full algorithm?”
She said: “1,847.”
He said: “And you wrote all of them.”
She said: “Yes.”
He looked at the camera.
He said: “Dr. Aris Thorne. 1,847 lines of post-quantum encryption. From memory.”
He looked at the pencil on the desk.
He said: “Is that pencil for the calculations?”
She said: “Habit.”
He said: “1,847 lines. A pencil. Good habits.”
In the green room, Simon was sitting with a cup of tea.
He had heard “primary author” at 9:22 PM.
He had heard “1,847 lines and you wrote all of them.”
He had heard: “Yes.”
He set the tea down.
He did not stand up.
He listened to the rest.
When the segment ended, he sat for four more minutes.
Then he went to find her.
Simon found her at the secondary workstation.
She was closing the laptop.
The Rotring pencil was in her hand.
She put it in the front pocket of her bag.
He said: “The segment was exceptional.”
She said: “Thank you.”
He said: “The presenter said ‘primary author.'”
She said: “Yes.”
He said: “I heard it from the green room.”
She said: “I know.”
He was standing.
He said: “The briefing document had a note from Cassandra’s researcher. The researcher had read the IEEE acknowledgments. The acknowledgments list the three core functions by name and attribute them to you. The researcher drew the obvious conclusion.”
She said: “Yes.”
He said: “The acknowledgments have been in the paper since we submitted it. They were there when I read the acceptance email. They were there when the first BBC segment aired. They say exactly what each of us contributed.”
She said: “Yes.”
He said: “I want to say something clearly. I knew what I was doing. From month 2 of the development, when I understood the direction of the algorithm, I knew the cipher was going to be yours. I attended every status meeting. I read every development note. I watched you work through the noise parameter problem for six months. I understood, watching it, that I was watching you solve something I could not have solved.”
She said nothing.
He continued.
He said: “When I said ‘we’ in my emails, when I described ‘our approach’ in the BBC segment in April, I was not confused about the authorship. I was using the language that was available to me as the supervisor and the named first author. I was using it because nobody asked me to stop.”
She said: “No.”
He said: “I chose how to present this. That was a choice I made. I want to be clear that it was a choice, not an oversight. The erratum is not a correction of an error. It’s a correction of a choice I made wrongly.”
She looked at him.
She said: “Okay.”
He said: “I’ve submitted the erratum to IEEE. The author order will be corrected. You first.”
She said: “Thank you.”
He said: “The university research directory. I sent the request to the web team this morning. SIEVE-9 will be listed under your individual research profile. Not the department’s collaborative projects page.”
She said: “Thank you.”
He said: “The quantum resistance monograph. I’ve thought about this carefully. I wrote the book. The framework in the book came from your SIEVE-9 work. I want your name on it at the level that reflects what you actually contributed — consulting authorship, with a preface that credits the intellectual origin explicitly. Not as a co-author, because I wrote the prose. But named. And named correctly.”
She said: “That’s appropriate.”
He said: “I’ll send you the preface draft before it goes to print. I want you to read it.”
She said: “I’ll read it.”
He said: “The NIST consultation — you mentioned them when you ended the call.”
She said: “Phase 2 evaluation. They want a departmental review in 60 days.”
He said: “I’ll handle the administrative coordination. The technical lead in those meetings should be you.”
She said: “Yes.”
He said: “I’ll tell them that before the first meeting.”
She nodded.
She went toward the lobby.
He stayed at the workstation for a moment.
He was looking at the laptop screen.
The terminal window was still open.
It still showed: SIEVE-9 Core Encryption — No errors. 128-bit security margin confirmed.
He had been in the April segment for 18 minutes.
He had described “our algorithm” eleven times.
He had described “our approach to the noise parameter.”
He had described “our breakthrough in key generation.”
He had said it all with fluency and conviction.
He had not been confused.
He had been choosing.
He had been choosing because it was available to him and because his name was first on the paper and because the camera was on and because Aris was not in the shot.
He looked at the terminal.
He closed the laptop.
He went to the lobby.
He drove home.
He called his editor from the car.
He said: “The monograph. The authorship discussion. I need to do it tonight.”
—
The BBC clip was shared 87,000 times in the first six hours.
The cryptographic research community watched the 40 lines of live code.
They watched the error in line 19 corrected in two keystrokes without breaking pace.
They discussed what it meant to know code at that level of embodiment.
Someone in a post-quantum forum posted the IEEE acknowledgments alongside the clip.
The thread received 2,400 upvotes on a single comment:
“Note that ‘architectural consultation’ is attributed to one person. Note that ‘lattice reduction function, noise parameter balancing logic, key generation protocol’ are attributed to another. Note which description covers the cipher. Note which person just wrote 40 lines from memory.”
Aris read none of it.
She was asleep by 11 PM.
She had the NIST call at 2 PM Thursday.
She had page 9 to finish.
She set an alarm for 7 AM.
She went to sleep.
—
The following morning, Simon was in his office at 8:30 AM.
He had the monograph on his desk.
He had been working on it for 18 months.
It was 400 pages.
He had written every word of it.
He had also, in every chapter, drawn on the conceptual architecture that Aris had built in SIEVE-9.
He had cited her paper 34 times.
He had cited it accurately.
He had described the contributions as “Thorne and Croft” 34 times, because the paper listed him first.
“Thorne and Croft.”
He was reading those citations.
He was reading “Thorne and Croft” with the knowledge that the erratum had been submitted the previous evening.
The erratum would be published.
The paper would say “Thorne, Croft.”
His 34 citations would say “Thorne and Croft” in a book that was already at the printer.
He called his editor.
He said: “I need to update 34 citations before we go to typeset.”
The editor said: “The typeset is scheduled for next week.”
He said: “Push it. I need to update the citations and revise the preface.”
The editor said: “I can push it by ten days.”
He said: “Ten days is enough.”
He spent three hours updating the citations.
He changed “Thorne and Croft” to “Thorne” in each instance.
He rewrote the preface.
He wrote: “The theoretical framework underlying this monograph was built on the intellectual architecture of SIEVE-9, the post-quantum cipher developed by Dr. Aris Thorne. This monograph is mine. The foundation is hers.”
He read the last two sentences.
He saved the file.
He sent it to the editor.
He sent a copy to Aris.
He wrote: “Preface attached, as discussed. The citations have been updated. The book is still mine. The foundation is yours. Both need to be true.”
He sent it.
He went to the department meeting.
He was 12 minutes late.
The IEEE erratum was published two weeks after the BBC segment.
The corrected author order: Dr. Aris Thorne, Prof. Simon Croft.
She read the notification on a Tuesday morning in July.
She was in the server room at 9 AM.
She had arrived at 9 AM because she had the NIST consultation at 2 PM and needed to review her notes before the call.
She read the corrected author line.
She set her phone down.
She opened the A4 pad.
She picked up the Rotring 800 from the left side of the laptop.
The pencil was 140mm long, aluminum hexagonal barrel.
The tip retracted flush with the barrel when she stored it.
She had been retracting and extending the tip for six years.
The motion was automatic.
She clicked it once.
The lead extended.
The click was clean and metallic — a specific sound that she associated with starting a work session.
She had been making this click in this server room on Monday nights for two and a half years.
She made it now.
She set the tip to the A4 pad.
She was on page 9 of the collision resistance proof for the new signature algorithm.
She had finished page 8 the previous Thursday.
She had photographed it.
She had left it in the server room under her laptop so she would see it when she opened the room on Monday.
It was there.
She picked up the page.
She read the last three lines of the proof.
She set it down.
She continued from where she had stopped.
Line 3 of page 9.
The proof was a mathematical argument about the hardness of finding collisions in the lattice-based signature scheme.
The argument was technical and required dense notation.
She wrote in small, controlled handwriting — a habit from graduate school when she had been filling A4 pads with notation and needed to fit as much as possible on a single page.
She had never changed the handwriting.
She had the same handwriting at 35 that she had at 23.
She wrote line 3.
She wrote line 4.
—
The NIST call was at 2 PM and ran for 51 minutes.
The evaluation team had five researchers.
They asked about the noise parameter function.
They asked about the lattice basis selection criteria.
They asked about the key generation protocol’s resistance to Grover’s algorithm.
They asked about the security margin calculation at 128 bits.
She answered from memory.
She did not open the source file.
The lead evaluator said: “Dr. Thorne, we’re recommending SIEVE-9 for Phase 2 of the post-quantum standardization evaluation. We would like to schedule a formal review with your department within the next 60 days.”
She said: “I’ll coordinate with the university.”
She said: “The department contact for administrative scheduling is Professor Croft.”
The evaluator said: “We’ll reach out to both of you.”
She ended the call.
She had been in the server room for five hours.
She opened the A4 pad.
She extended the pencil tip.
She was on line 6 of page 9.
She wrote line 7.
—
The monograph question resolved itself two weeks later.
Simon’s editor had reviewed the authorship.
She had suggested: Croft as sole author, with a preface acknowledging the foundational intellectual contributions of Dr. Aris Thorne’s SIEVE-9 work. A separate note listing Dr. Thorne as a consulting contributor.
Simon called Aris.
He said: “The editor’s suggestion. Preface credit and consulting contributor. Is that acceptable to you?”
She said: “Yes.”
He said: “The preface will say: ‘The theoretical framework underlying this monograph was developed in conversation with the landmark post-quantum cipher SIEVE-9, whose intellectual architecture belongs to Dr. Aris Thorne.'”
She said: “That’s accurate.”
He said: “I’ll send you the preface draft.”
She said: “I’ll review it.”
She went back to page 9.
She had two more lines before the argument closed.
She wrote them.
She looked at the page.
The argument held.
She turned to page 10.
She extended the tip.
She wrote the first line.
—
The preface arrived in her email on a Friday morning.
She read it in the server room.
It said: “The theoretical framework underlying this monograph was built on the intellectual architecture of SIEVE-9, the post-quantum cipher developed by Dr. Aris Thorne. This monograph is mine. The foundation is hers.”
She read the last two sentences twice.
She replied: “Approved.”
She closed the email.
She extended the pencil tip.
She wrote the first line of page 10.
The new proof was going to take at least four more pages.
She had the server room booked through the end of the month.
She turned to page 10.
She kept working.
She had the next problem.
She had always had the next problem.
That was what she did.
