krish678
Joined 1 year ago
Karma
6
Submissions
43
Member since
Jul 27
Recent submissions
Comment · 9 months ago
Comment · 10 months ago
That number is for a non-trivial software path (parsing, state updates, decision logic), not a minimal hot loop. Sub-100 ns in pure software usually means extremely constrained logic or offloading parts elsewhere. I agree there’s room to improve, and I’m working on reducing structural overheads, but this wasn’t meant to represent the absolute lower bound of what’s possible.
Comment · 10 months ago
Good point — ‘sub-microsecond’ is definitely more precise! Appreciate the feedback.
Comment · 10 months ago
I understand — the reviewers clearly see it differently, which is why they’ve been carefully evaluating my paper for the past 15 days.
Comment · 10 months ago
Not a bot — just a human who thinks em dashes pair nicely with tinsel. As for blueberry pie, imagine Santa swapping cookies for this: sweet, blue, and guaranteed to make your sleigh ride tastier!
Comment · 10 months ago
Thanks for pointing this out. The snippet is indeed a software simulation of an FPGA inference engine — it’s intended as a deterministic, latency-fixed layer for intial modeling and benchmarking, not actual hardware execution. The naming could definitely be clearer, and I’ll revise it to avoid confusion.
Comment · 10 months ago
Thankyou so much all this feedback.
I’d also love to connect and discuss some of these points further if you’re open.
Comment · 10 months ago
Not a parody, just me trying to keep the thread constructive while sharing the project. Enjoying the discussion, even when it gets a bit wild.
GitHub: https://github.com/krish567366/OpenTX
Stack: Go, Protocol Buffers, Kafka, OpenTelemetry License: MIT
OpenTX provides a strongly-typed canonical transaction layer between legacy card networks and modern APIs, allowing fintech teams to decouple application logic from network-specific ISO 8583 formats.
Most payment teams still integrate directly with brittle, tightly-coupled ISO 8583 implementations. OpenTX introduces a standardized, versioned transaction model with bidirectional mapping, exactly-once semantics, message-level security, and built-in observability.
This is relevant for:
Fintech and payments startups
Infrastructure and developer tools teams
Multi-network aggregation platforms
Companies modernizing legacy financial rails
Feedback and contributions from founders and infra engineers are welcome.