Engagements
Research-first, blockchain-deep, builder-led. Eleven years inside protocol stacks, twenty-plus public repos, and a live ship log. We take the scoped, hard problems your team doesn't have the load to carry — audits, protocol design, embedded engineering, joint research — and ship them as code, reports, or both.
Looking to contribute or get hired? That's /work-with-us/contributors.
Pick the shape that fits the work. Scope and price come out of the discovery call — we don’t publish rate cards because every engagement is different.
A focused, time-boxed deliverable. One owner, one artefact, no ambiguity.
Typical scope: smart-contract security review, architecture review or threat model, technical due diligence for an investor, or a half-day to two-day workshop.
Ideal if… you have a contract going to mainnet next month, an investor asking for DD, or a team that needs threat-modelling before a redesign.
A defined milestone-based engagement. Real artefact at the end — protocol, audit, tool, or paper.
Typical scope: protocol design consulting with prototype, comprehensive audit plus remediation, custom open-source tooling, or a research partnership with published artefacts.
Ideal if… you're designing a new mechanism, integrating a hard piece of infra, or have a research question your team can't park a senior engineer on for two months.
Standing capacity, monthly cadence. We hold the load so you can plan against it.
Typical scope: security advisory (on-call review + incident support), monthly research output co-published with you, or a part-time embedded protocol engineer.
Ideal if… you want a senior protocol brain on tap, a research function without hiring one, or an audit partner who already knows your codebase by quarter two.
Grant-funded research and co-funded ecosystem work also available — see services for the full menu, or just ask.
Four steps from first email to kickoff. Usually three to ten business days end-to-end.
Send the form below or email krishna@kcolbchain.com. Tell us what you're trying to ship and roughly which tier fits. We reply within two business days.
30–45 minutes. We dig into the problem, the constraints, and the signal you're trying to produce. No deck, no pitch — just enough context to scope honestly.
Within five business days you get a written proposal: deliverables, milestones, timeline, price, and what we'll need from you. One round of revisions included.
Sign, 50% upfront (or first milestone for larger work), and we start. Weekly check-ins, async-first, code and reports in your repos and Drive. USDC, ETH, or wire.
30–45 minutes, async-friendly. No commitment, no sales pitch — if we’re a fit we’ll say so; if not, we’ll point you at someone better.
Send a short email — one paragraph on what you’re trying to ship and rough timing. We’ll reply within two business days with a couple of slots and a short list of what to bring.
Public artefacts and partner case studies. The full ship log lives at /reports.
Case study — coming soon
Two-week security review of a deployed lending protocol, followed by remediation support through mainnet upgrade. Findings, severity matrix, and post-fix verification published with partner consent.
Writeup landing here once the partner signs off on disclosure.
Case study — coming soon
Six-week embedded engagement with an L2 team: bridge integration, indexer hardening, and a shipped open-source tool that the partner now maintains in-house.
Writeup landing here once the artefact is fully open-sourced.
Case study — coming soon
Eight-week joint research engagement with a foundation: published paper, reproducible benchmark suite, and an EIP-track follow-up. Co-funded with a grant.
Writeup landing here once the paper is public.
Want references before booking? Ask on the discovery call — we can connect you with current and past partners under NDA.
Book a discovery call or email us with the brief. We aim to reply within two business days.
