LayerZero V2 · DVN config and hardening · Circle CCTP · On-chain agents · 23 chains in production
Services
Three ways to engage. All of them end with working software in production, every claim verifiable on-chain or in the repo.
Cross-chain and DeFi infrastructure
LayerZero V2 OApp, OFT, and ONFT patterns that are battle-tested in production across 7 chains. DVN (decentralized verifier network) configuration and security hardening so your bridge does not get drained. Circle CCTP including the Solana-to-EVM route most teams stall on. Concurrency that never strands funds: Postgres advisory locks, per-address chain locks, fresh-fetched nonces on every transaction. Visa settlement rails against on-chain balances.
Good fit
Good fit if: you are going multi-chain and the bridges scare you. You need OFT or ONFT done right the first time, not after a botched first attempt. You are settling card or fiat rails against on-chain balances and cannot afford a stranded transaction.
On-chain agent systems
Agents that execute real on-chain actions under proof, not chatbots that describe them. Execution layers with observability, kill-switches, and a trust contract so your users know the agent cannot lie about what it did. Every action verifiable against a confirmed transaction hash.
Good fit
Good fit if: you need an agent that acts on-chain, not one that chats about it. You are wiring LLMs to real payments, swaps, or chain state and cannot afford hallucinated execution. You want kill-switches and observability designed in from day one.
Founding-engineer product builds
Contracts, backend, database, frontend, deploy, and the operational discipline to keep it alive. I co-founded the first omnichain NFT platform (Omni-X), built the first OFT launchpad on LayerZero V2, and run a personal AI system that lets me ship at the pace of a small team. I have run this full-stack loop for 10 years.
Good fit
Good fit if: you have a funded idea and no engineering team yet. You need someone who ships the contract, the backend, the frontend, and the deploy, without a hand-off gap between each. You want a builder who has been the founder too and thinks about your runway like it is his own.
How to engage
Three steps. You can stop after any one of them and keep everything produced.
Scope call
30 min, free
You describe the problem. I tell you honestly whether I am the right builder, what the real risks are, and exactly what I would do first. No deck, no pitch.
Paid discovery sprint
1-2 weeks, fixed fee
Architecture, build plan, and a working demo slice. For a cross-chain team this means: chain selection rationale, OFT/OApp contract skeleton, concurrency model, and the hardest integration proven on testnet. You own everything produced whether or not we continue.
The build
Weekly ships
Working software you can click every week, not status decks. Every decision logged in the repo. For on-chain work: contracts verified on-chain, agent actions tied to transaction hashes, kill-switches on every live path.
Process
Scope call.
30 minutes. You describe the problem, I tell you honestly whether I am the right builder and what I would do first. No deck, no sales pitch: a technical conversation about your actual constraints.
Discovery sprint.
A short paid sprint that produces architecture, a build plan, and a demo slice. You own everything produced, whether or not we continue past this point.
The build.
Weekly ships you can click, not status decks. Every claim verifiable in the repo, every decision logged, so you always know exactly where the project stands.
Operate and harden.
Observability, kill-switches, and handoff docs. I build systems that survive me leaving, because a founding engineer who traps you is not actually helping you.
Pricing
Hourly build work
$90 / hr
A straightforward rate for design, backend, and full-stack build work. $90 per hour, billed against shipped work you can see.
Cross-chain audit
$1,000 fixed
One week
A one-week cross-chain audit. I review your LayerZero, CCTP, and DVN setup for the failure modes that strand funds or get bridges drained, and hand you a written report with the exact fixes. Fixed at $1,000. You keep the report whether or not we work together after.
Common questions
Full FAQ →You are a solo engineer. What if you disappear?
I build systems that survive me leaving. Observability, kill-switches, and handoff docs ship with every engagement, and you own the repo, the architecture, and the deploy from day one. I also run a personal AI system that documents every decision, so the context never lives only in my head.
Can one person really ship this fast?
Yes, because I am not really working alone. I pair with a personal neural net I designed that documents every decision and lets me ship at the pace of a small team. Ten years of founding-engineer work, seven of them running production systems, is the track record.
What about timezone and availability?
I am US-based on Eastern time and reply to scope requests within one business day. I take a limited number of builds at once so the one I am on gets real attention.
Who owns the code and the IP?
You do. Everything produced in a discovery sprint or a build is yours, whether or not we continue. A founding engineer who traps you is not helping you.
Building cross-chain or on-chain agents?
30 minutes: you describe the problem, I tell you honestly whether I am the right builder and exactly what I would do first.