News for hackers. Stuff that matters.
Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by stuartjohnson12 on Monday December 15, 2025 @11:45AM (#46276865)
Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by krish678 on Monday December 15, 2025 @12:08PM (#46277199)
Thanks for checking this out! The “marketing-style” log was intentionally illustrative — showing the before vs. after of institutional-grade logging. The real framework uses multi-layer hardware/software timestamps, cryptographic manifests, and offline verification to produce fully auditable latency measurements. The snippet you linked is just the “before” example; everything in use follows the “after” model. That, was from intial times.
Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by stuartjohnson12 on Monday December 15, 2025 @12:53PM (#46277906)
If you're going to ask ChatGPT to write your response for you, I'll do the same.

---

Great question! It's worth noting that your response exhibits several hallmarks of AI-generated content, including but not limited to:

Bullet-point formatting where none was needed

Buzzword density that feels a bit elevated

Phrases like "fully reproducible, evidence-based" that have a certain... flavor to them

I hope this helps! Let me know if you have any other questions.

Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by krish678 on Monday December 15, 2025 @01:42PM (#46278529)
For what it’s worth, I care more about whether the claims can be independently verified than how the explanation is phrased. The project stands or falls on measurements, artifacts, and reproducibility, not on who typed a comment or how conversational it sounds.

If you spot something technically incorrect or unverifiable in the repo itself, I’m genuinely happy to discuss that.

Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by stuartjohnson12 on Monday December 15, 2025 @01:52PM (#46278654)
You do realise you didn't actually commit any code, right?
Re:Show HN: Sub-microsecond (890 ns) trading execution resea... by krish678 on Tuesday December 16, 2025 @12:23AM (#46285082)
Clarifying, since this is a fair concern:

The full C++ execution core is intentionally not published yet. What’s public in this repo is the measurement, instrumentation, logging structure, and research scaffolding around sub-microsecond latency — not the proprietary execution logic itself.

I should have stated that more explicitly up front.

The goal of the public material is to show how latency is measured, verified, and replayed, rather than to ship a complete trading engine. I’m happy to discuss methodology or share deeper details privately with interested engineers.

Appreciate the pushback — it’s valid.