use-case deliverables
concentrated-liquidity AMMs + the bots that keep them aligned.
The pool + hook contracts of spot AMM. v4 hook contracts, custom fee models, oracle integration in the pool, withdrawal-attack guards. We write the contracts that the bots above run. Concentrated-liquidity AMMs + the bots that keep them aligned — but specifically, the smart contracts layer of it.
explicit deliverables for this use-case. additional smart contracts pieces stay in scope.
concentrated-liquidity AMMs + the bots that keep them aligned.
contracts that hold the money our trading stacks move.
not what we built (we don't kiss-and-tell client work), but the shapes-of-the-problem we anchor scope against.
The pool + hook contracts of spot AMM. Specifically: v4 hook contracts, custom fee models, oracle integration in the pool, withdrawal-attack guards. We write the contracts that the bots above run.
Reference points we look at when scoping: Aerodrome veCRV-style emissions, Uniswap v4 hooks, Meteora DLMM. We don't copy them; they're shapes-of-the-problem.
spot AMM touches multiple disciplines. We split the work along service lines so each engagement has a single scope. If you need more than one side, we'll scope a second engagement (or a combined one) — but a single smart contracts pod is usually the right starting shape.
Book a call. 30 minutes, no NDA, no slide deck. We tell you what scope of work looks like or refer you elsewhere if we're not the right team.