I build execution systems — software that turns a trading idea into orders that actually reach a venue, and the tests that prove it behaves before real money moves. That is the spine of this profile: Rust and C++20 engines, order books and venue adapters written from measurement rather than documentation, with strategy work spanning prediction markets, crypto, forex, NSE options, index futures and betting exchanges.

Onchain, that same discipline applied to protocols — lending, real-world asset tokenization, NFT marketplaces, game economies and security tooling, with contracts deployed to Monad, Sepolia, Solana and Base mainnet. Including x402 agent payments, where software pays software per call in real stablecoin with no account in between.

AI — an MCP service with a schema-validated LLM pipeline behind a paid endpoint, autonomous onchain agents, and trained models: a RandomForest with committed weights, a Keras LSTM, a hand-rolled PPO actor-critic.

Products — a GST-compliant commerce backend with containerised CI, live client sites, and a real-time platform for live entertainment formats.

I also keep early-stage work public instead of hidden: product concepts, system teardowns, media and writing projects that are scoped but not built. Every one of those says so at the top of its page, because a profile is only useful if you can tell the difference.

Product concepts of my own, in development. Each says plainly what is built and what is only scoped — none is presented as shipped.

Reimplementations of established consumer platforms — chosen because rebuilding a product at scale is the fastest way to meet the problems its engineers solved.

Independent system teardowns and architecture proposals for consumer-scale products. Unsolicited analysis from public information — no affiliation with any company named.

Writing, production and post — plus the software side of live formats. Most is direction rather than delivered work, and each page says so.

Each portfolio separates what has been independently executed from what a repository reports about itself, and self-declared limitations are preserved rather than hidden — if a system says it is at phase 10 of 16, that line stays in.

Where a README's numbers didn't match the code, I corrected them in both directions: one project claimed 91 end-to-end tests and has 68; another claimed 230 and has 269.

Repositories that contain a design document and no implementation say so in a banner at the top, and are never listed as built work.

If you want to check something rather than take my word for it, every featured project lists the clone-and-run command that reproduces its numbers.

All repositories are mapped in the complete repository map — every one labelled as built code, a design specification with no implementation, or learning/archived work.

Working in: Rust · C++20 · TypeScript · Python · Solidity · Go

📫 pranaygaurav4555@gmail.com