Track Record

Every entry below is a matter of record: named where the client is public, attributed where the work was performed with a previous employer.

CASE 01

The Cardano core ledger — Input Output Global

The Context

One of our engineers works on the Core Ledger team of the Cardano blockchain at Input Output Global (IOG), our first client. The work: implementing ledger rules against formal specifications, contributing to the open-source ledger repository, and contributing to the Cardano Improvement Proposal process.

Why It Matters

Every transaction on the Cardano network is processed by the ledger code this team writes and maintains. The work is public — the repository, the specifications, and the proposals can all be read by anyone.

Verification

The repository and the proposals are public. We will point you to our contributions.

PUBLIC REPOSITORY · ACTIVE CONTRIBUTOR · ONGOING

CASE 02

Layer-1 proof-of-stake engineering — BlockPQR

The Context

BlockPQR builds the parts of a blockchain that cannot be wrong: consensus, network, ledger, CLI, and high availability for proof-of-stake chains. Avadhut Software Private Limited contracts with BlockPQR on this work.

Why It Matters

Systems engineering where a regression is somebody's money. Availability is the requirement. Their standard is our standard: specified before it is written, proven before it ships.

Verification

Read what they build, and how, in their own words at blockpqr.io.

CLIENT · ONGOING

CASE 03

Correctness audit of the Hedera Hashgraph code base

The Context

As a Senior Engineer at FP Complete (2018–2022), one of our engineers was part of the team that audited the Hedera Hashgraph code base for software correctness.

Why It Matters

An audit of this kind is line-by-line reading plus tool-assisted scanning, ending in findings ranked critical, high, medium, low, and well-done — the same method we use at Superb Software today.

Verification

Hedera is a public distributed-ledger network; the engagement is part of FP Complete's public record. References available on request.

AT FP COMPLETE · LINE-BY-LINE + TOOL-ASSISTED

CASE 04

The first managed backends for Hasura's query engine

The Context

While at FP Complete, our engineers helped implement the first versions of the managed data-platform backends for Hasura's query engine.

Why It Matters

Hasura serves a large base of teams in production. The backends they worked on extended the engine to three widely-deployed data platforms.

Verification

Hasura is public software with public releases. References available on request.

AT FP COMPLETE · THREE DATA PLATFORMS

CASE 05

Modernising a credit-risk system — Future Finance

The Context

An instant credit-risk analysis system had grown over-engineered and hard to change. The team migrated it to a clear and concise implementation.

Why It Matters

Tuning the runtime reduced memory usage by about 24% and idle CPU by 40%. A large legacy test suite was rewritten under the same property-based testing discipline we bring to every engagement.

Verification

Performed while our engineers were at FP Complete. References available on request.

AT FP COMPLETE · MEMORY −24% · IDLE CPU −40%

CASE 06

XL Deploy UI — digital.ai (formerly XebiaLabs)

The Context

One of our engineers was on the four-person team that developed the UI for XL Deploy, a multi-cloud and on-premises deployment orchestrator recognised by Gartner and Forrester.

Why It Matters

Several Fortune 250 companies used the product. The team removed about 70% of five years of accumulated technical debt in a single year, while shipping continuously.

Verification

Public product history. References available on request.

4-PERSON TEAM · FORTUNE 250 CUSTOMERS · TECH DEBT −70% IN ONE YEAR

CASE 07

Three production systems & a 22× throughput increase — Theatro

The Context

At Theatro (2014–2016), one of our engineers took three systems from proof-of-concept to production: indoor positioning, in-store request-and-response, and remote audio messaging — all of which remain major features of the product.

Why It Matters

Breaking a monolith into focused services raised the messaging layer's throughput roughly 22×. A three-year-old connection leak was resolved at the application level.

Verification

Company history is public. References available on request.

POC → PRODUCTION ×3 · MESSAGING THROUGHPUT ~22×

CASE 08

A trading platform two years behind schedule

The Context

A perpetual-swaps trading platform had spent two years stalled: the financial model was wrong, the architecture had calcified, and the team had lost the ability to ship. Our engineers corrected the financial model, rebuilt the architecture, and introduced secure-programming standards.

Why It Matters

The math came first — no amount of code fixes a wrong financial model. Then the architecture was rebuilt around it, and secure-programming standards went in across the codebase.

Verification

Shipped to production in seven months, on an architecture the client's own team could maintain. Performed at FP Complete / FP Block. References available on request.

2 YEARS STALLED · SHIPPED IN 7 MONTHS

CASE 09

Regulated computation: three weeks to ten minutes

The Context

Regulated pharmaceutical computation infrastructure spanning roughly forty contributors.

Why It Matters

Our engineers led the rebuild of the computation pipeline: run time fell from about three weeks to about ten minutes.

Verification

Performed at FP Complete / FP Block. References available on request.

~40 CONTRIBUTORS · 3 WEEKS → 10 MINUTES

CASE 10

A multi-cloud platform at ~100 worker nodes

The Context

Our engineers designed and led the flagship multi-cloud platform of FP Complete / FP Block — roughly one hundred worker nodes across two major clouds, with a curated add-on catalogue.

Why It Matters

They built and operated its reliability backbone — observability, backup, authentication, secure cluster access — and carried production clusters through upgrades and recovery without service interruption.

Verification

References available on request.

~100 WORKER NODES · TWO CLOUDS · NO-INTERRUPTION UPGRADES

CASE 11

A perps DEX: copy-trading contracts & a halved cloud bill

The Context

For Levana, a perpetuals DEX, our engineers authored the copy-trading contract and trader-bot integration, and contributed to its governance, factory, and countertrade contracts.

Why It Matters

They reduced cloud spend by 50%, added DDoS protection, and replaced hardcoded credentials with cross-account roles.

Verification

Performed at FP Complete / FP Block. References available on request.

CLOUD COST −50% · DDoS PROTECTION · STATIC KEYS REPLACED

CASE 12

Reinsurance ledger algorithms

The Context

Our engineers led delivery of a new product on the Supercede reinsurance platform, turning complex financial requirements into production ledger algorithms.

Why It Matters

Working alongside a domain expert, they shipped the algorithms that settle real reinsurance business.

Verification

Performed at FP Complete / FP Block. References available on request.

PRODUCTION LEDGER ALGORITHMS · DOMAIN-EXPERT PAIRING

CASE 13

Cloud to bare metal in two weeks, 90% cheaper

The Context

A client's entire operation — applications and databases — was migrated from a major cloud to bare metal in two weeks.

Why It Matters

Monthly infrastructure spend fell by 90%.

Verification

Performed at FP Complete / FP Block. References available on request.

2-WEEK MIGRATION · INFRA COST −90%

CASE 14

Build times: 45 minutes to under four

The Context

Across client and internal projects, our engineers optimised the continuous-integration pipeline.

Why It Matters

In one case, build times fell from 45 minutes to under 4 minutes.

Verification

Performed at FP Complete / FP Block. References available on request.

45 MIN → <4 MIN

CASE 15

Tokenised-asset infrastructure

The Context

Tokenised-asset infrastructure covering minting workflows, token contracts, document metadata, and compliance-aware capabilities.

Why It Matters

Real-world assets on-chain need the paperwork right before the tokens are. The compliance layer came first.

Verification

Performed at FP Complete / FP Block. References available on request.

COMPLIANT MINTING · TOKEN CONTRACTS · METADATA PIPELINES

CASE 16

Regulated prediction markets, rebuilt

The Context

Two regulated prediction-market systems, rebuilt across two ecosystems.

Why It Matters

Product requirements, financial modelling, and a compliant data architecture, done together — so the markets were legal by construction, not by review at the end.

Verification

Performed at FP Complete / FP Block. References available on request.

TWO ECOSYSTEMS · FINANCIAL MODELLING · COMPLIANT DATA ARCHITECTURE

CASE 17

Blockchain gaming at scale

The Context

A blockchain gaming product supporting thousands of active users.

Why It Matters

It ran a $4M NFT auction and carries $8M in recurring royalties, with thousands of active users.

Verification

Performed at FP Complete / FP Block. References available on request.

THOUSANDS OF USERS · $4M NFT AUCTION · $8M RECURRING ROYALTIES

CASE 18

A decentralised lending protocol, from scratch

The Context

A lending protocol on a proof-of-stake chain, designed from scratch and delivered end-to-end.

Why It Matters

Multi-step flows were engineered to stay consistent through partial failure.

Verification

Performed at FP Complete / FP Block. References available on request.

DESIGNED FROM SCRATCH · END-TO-END · PARTIAL-FAILURE RESILIENT

CASE 19

Core package infrastructure for the ecosystem

The Context

The package infrastructure that production systems in this field depend on.

Why It Matters

Deployed and maintained to stay reliable and available for developers and production systems alike.

Verification

References available on request.

THE ECOSYSTEM'S PACKAGE INFRASTRUCTURE · KEPT AVAILABLE