Skip to content
Shreyas K S
SOFTWARE ENGINEERING, IN PRACTICE

Built from curiosity.
Written from experience.

I’m Shreyas, a co-founder and software engineer.
I build systems and write about Rust, operating systems,
and the decisions behind the code.

From a bug to a blog postAn anime-inspired Shreyas investigates duplicate jobs after a timeout. He checks an AI retry suggestion against a server commit whose reply was lost, adds a stable request key and atomic server-side deduplication, and writes up the lesson. A new idea starts the cycle again. retry.trace JOBS POST /jobs → timeout retry → 2 jobs same key → 1 job server: committed; reply lost server: atomic dedup + enqueue timeout + replay FAIL PASS INVARIANT / FIELD NOTES A timeout isn't a rollback. DRAFT SAVED Did it commit? DB? AI Try this? Backoff + retry Already committed? DUPLICATE! ; ?
01 / THE TECHNICAL JOURNAL

Some things stay invariant.

Visit INVARIANT ↗
[ ≡ ]INVARIANTLATEST ARTICLE↗
Three panels, one per clause: a seal landing on a document nobody read; the page shown beside the different page that was signed; fifty signed authorisations of which one matched, above a validity window that stayed open for three hours and fifty minutes.
Systems / Correctness

The Key Agreed

On 29 October 2026 billions left Binance across ten networks, or eleven, in twenty minutes, or three hours. The firms watching disagree. What none of them dispute is that every signature was valid.

Read the article ↗
Systems / Correctness

Nothing Starts Clean

PHP workers, keep-alive sockets and startup snapshots are all reused because starting fresh is slow. Three CVEs and a platform breach from one October week, and what each one inherited from whoever was there...

44 min read
Systems / Correctness

Success Means Verified

A crypto library, a cross-chain bridge, and an AI agent all reported success they had never verified. Three ways the wiring between a check and its success signal comes apart—and the rules that hold it toget...

40 min read
02 / SELECTED WORK

From architecture to implementation.

All projects ↗
01 / OPEN SOURCE↗

toon-rust

Built TOON’s Rust implementation from the format specification, separating parsing and validation from a typed Serde API and interactive tools.

Rust · SerializationRead the story →
02 / OPEN SOURCE↗

Arkeo

Rearchitected an outdated Cosmos application and guided its rewrite, updating the SDK foundation, validator rewards, deterministic processing, and network-specific signing.

Go · Cosmos SDKRead the story →
03 / OPEN SOURCE↗

DIVE

Turned recurring blockchain deployment problems into Kurtosis workflows for nodes, contracts, and bridges, with ordered setup and reuse of running infrastructure.

Go · Starlark · KurtosisRead the story →
04 / OPEN SOURCE↗

DAW Buddy

Shaped the desktop architecture and built tools for music producers, including project search, key and tempo matching, waveform trimming, and missing-sample detection.

TypeScript · Electron · Audio toolsView on GitHub ↗
03 / THE REST OF THE PICTURE

Off the clock.

a little more room to think ↴
Notes

Why I built shrys.xyz

On making engineering decisions understandable, learning from first principles, and keeping a record worth returning to.

2 min read