Engineering
Build settlement infrastructure that holds real capital, and be the person who found the rounding error before the threshold did.
What you’ll do
Take primitives from reference implementation to audited production. Work across smart contracts, off-chain sequencing and the settlement paths that connect them, on systems where correctness is not negotiable and the failure mode is somebody’s capital.
Own things end to end. The engineer who builds a settlement path is the engineer who instruments it, monitors it and gets paged by it.
What we look for
Strong systems engineering — distributed systems, consensus, or high-performance infrastructure. Solidity or a comparable contract language is expected, but we care considerably more about how you reason about failure than which language you reason in.
A specific kind of paranoia. The bugs that matter here do not announce themselves; they look like rounding until they look like a liquidation cascade. We want people who go looking.
Comfort with audits, formal methods and adversarial review as normal parts of shipping rather than a gate at the end.
How we work
Small teams, long horizons, no artificial deadlines on things that hold money. Code review is thorough and impersonal. We open-source what we can, on the reasoning that a primitive nobody can inspect is not really infrastructure.
Applying
Write to Labs@kolkheti.org with something you have built, written or broken. We would rather read one thing you care about than a full CV.