
A real-money gaming platform with a server-side provably-fair engine, a full affiliate subsystem, crypto cashier and identity verification — roughly 180k lines across fifty bounded contexts.
Most of what I have built is under client confidentiality or too infrastructure-heavy to keep running in public. So each system is written up by its engineering instead: how it is put together, the decisions that shaped it, and a walkthrough of the flows that matter.
Every note uses the same sections and the same diagram language, so very different systems can be compared.
Scale figures are read off the repositories: files, lines, modules and services. No rounded-up numbers.
Systems are described generically. No client names, brands, credentials or private endpoints.

A real-money gaming platform with a server-side provably-fair engine, a full affiliate subsystem, crypto cashier and identity verification — roughly 180k lines across fifty bounded contexts.

A four-service prediction market where users trade outcome shares on-chain, with an AI evidence pipeline proposing resolutions for human sign-off.

A forecasting game bolted onto real DeFi liquidity: users predict price outcomes, a worker fleet scores them against oracle data, and a dedicated reward engine distributes the results.

A white-label peer-to-peer trading engine that other operators embed into their own products, exposed entirely as APIs their backends consume.

A layer-one node that speaks to half a dozen foreign chains natively, with post-quantum signatures and zero-knowledge primitives built into the base layer rather than bolted on.

A standalone slot provider: operators integrate over an API, games run inside a sandboxed iframe, and outcomes are decided server-side by renderer-agnostic math packages.

An operator platform built around a tree of administrators rather than a flat admin role, where balances move by manual credit and debit between levels instead of through a payment gateway.

A local-first tutoring platform where uploaded course material becomes searchable knowledge, and lesson generation runs as a resumable graph rather than a single prompt.

A decision-support system for legal research where every answer traces back to a content-addressed snapshot of an official source, and an ingestion policy gate decides what is allowed into the corpus at all.

A Go control plane that drives existing local AI coding CLIs through a plan → work → verify → retry workflow, with shared agent profiles that live outside the repositories being worked on.

A client SDK family that hides six blockchain ecosystems and two signature generations behind one interface, so application code does not have to know which chain or which cryptography it is talking to.

A browser extension wallet where keys never leave an isolated background context, and accounts can be bound to post-quantum signature schemes.

An internal platform that turns a whole multi-service development environment into one configuration file, so onboarding a developer is a clone and a command rather than a day of setup.

A Solidity suite covering prediction pools, bonding-curve pricing, staking and reward distribution, deployed through a declarative pipeline with a tracked address registry.

A research harness for binary-outcome trading strategies, built specifically to disprove them — it optimises for expectancy, ships a coin-flip control, and places no real orders.

A campaign platform where users complete on-chain and social quests to earn allocations, with layered anti-abuse so the rewards reach people rather than scripts.

A working demonstration of software agents paying each other per API call, with cryptographic identity, an enforced spending allowance and a receipt for every transaction.

A client application demonstrating private transaction flows inside a permissioned subnet, where activity stays confidential between members and only a periodic rollup reaches the public chain.

A buy-now-pay-later and subscription rail for autonomous agents, where the credit relationship stays private inside a permissioned subnet while settlement is publicly verifiable.

Three subgraphs that turn raw contract events into a queryable API, so applications can ask questions the chain itself answers slowly or not at all.

A small, deliberately narrow HTTP service that verifies and looks up on-chain identity attestations — hardened well beyond its size because it sits on an authentication path.