DeFi protocol engineering
Every incentive you design will be tested by someone trying to break it for profit, usually within days of it holding real liquidity. A correctly implemented but poorly designed mechanism still fails in production, which is why we treat the economics and the code as one piece of work.
Why this work is different
A protocol is a market, and markets are played by participants who owe it nothing. The parameter choices made in an afternoon are the ones that decide whether it is resilient or merely functional on launch day.
Markets attract MEV whether or not they were designed for it. Ignoring that at design time does not avoid it, it just means someone else captures the value your users thought they had.
How we work
Mechanisms are simulated against adversarial behaviour, including extractive strategies, before they hold real liquidity. It is the same mempool-level understanding we bring to MEV infrastructure, applied at design time.
Protocol engineering sits between smart-contract work and market design, and we work across both, so the mechanism and its implementation are designed together rather than bolted onto each other.
What that means we build
Market machinery. Constant-function and concentrated-liquidity AMMs, onchain and hybrid order books, and the routing and settlement logic that connects them. Our founder has built automated market makers and exchange logic for onchain trading.
The economics as well as the code. Fee models, incentive and liquidity-mining design, and the parameter choices that decide how a protocol behaves under load.
Common questions
- What DeFi primitives do you build?
- AMMs (constant-function and concentrated-liquidity), order books, and the routing, settlement, and fee logic around them, plus the mechanism design that governs how they behave under load.
- Do you cover mechanism design or just implementation?
- Both. Fee structures, incentive and liquidity design, and parameter choices are part of the engagement, because a correctly implemented but poorly designed mechanism still fails in production.
- How do you account for MEV in protocol design?
- We design markets knowing they attract MEV, and simulate mechanisms against extractive strategies. It is the same mempool-level understanding we bring to our MEV infrastructure work.
Have something hard to build?
Tell us the hard part: the protocol, the client, the mechanism, or the system that has to hold.