Independent Vyper composition engineer for protocol teams before mainnet.
I'm Khomenkov Yuriy, building under KhomDev. My work sits where Vyper 0.4, Curve-ecosystem integrations, property testing, and deploy/runtime operations meet.
How I work
I prefer small, inspectable systems over magic. The useful pattern: map the value paths, name the trust boundaries, write the invariants, fuzz the mutating surface with Hypothesis/Titanoboa, prove risky integrations on a Sepolia or mainnet fork, then verify bytecode and runtime drift.
I don't ship isolated demos — I build composed systems where stablecoin, vault, DEX, and governance reinforce each other through permissionless routers that move value but never hold a key to user collateral.
Invariant-first
Each value path gets an explicit invariant and trust boundary before the code is treated as production-shaped.
Fuzzed, fork-proven
Hypothesis stateful suites + fork runs against real Coil and Curve contracts on Sepolia.
Open & honest
Self-reviewed in public with disclosed composition findings — audit-ready, clear about what an independent audit still adds.
Solo is a feature
You work directly with the engineer who writes the code. Escrow and milestone delivery keep it low-risk.
What backs the claims
- Four-protocol Vyper flywheel deployed on Sepolia
- 700+ tests green across the stack with stateful fuzz on external surfaces
- Internal composition review with findings, threat model, and invariant spec
- Deterministic security agents — read-only, no autonomous fund control
- Blueprint packages with explicit not-audited disclaimers
Verified credentials
What I do not sell
I do not sell unaudited code as mainnet-safe, do not claim agents control funds, and do not hide admin, oracle, solver, or deployment trust assumptions. I make those assumptions visible so teams can fix or consciously accept them.
Remote worldwide · USDC accepted · escrow available on engagements over $5k