For DeFi · MEV · Bot builders

Ship the on-chain piece.
Or build it yourself.

Solidity + Rust contract dev built off a live Aave V3 liquidator on Base and Optimism. Hire us, learn from us, or both. Async only — no calls, no sales tag.

DLE Engineering

EVM contract development. Liquidation bots, MEV scaffolding, audit support. Async-first, GitHub-native, paid in stablecoins or wire.

Custom DeFi contract dev
$200/hr · $8k–$25k project · $4k/mo retainer

For projects that need a working bot, a custom contract system, or audit support. We've shipped a multi-chain liquidator on Aave V3, analyzed Critical-class bugs across Kamino / Morpho / Uniswap V4, and built MEV/arb scaffolding (Artemis pattern). We hand you running code + a runbook your team or agent can operate.

  • Turn-key liquidation bots (Aave V3, Compound V3, Morpho Blue, custom): $8k–$15k
  • Solidity contracts or small systems with full Foundry coverage: $3k–$12k
  • MEV/arb scaffolding (Artemis-style framework, no strategy logic): $12k–$25k
  • Audit support / pre-audit review: $200/hr, 8-hour minimum
48-hour quote turnaround · async over email or Signal · USDC or wire

Soroban Specialist

Stellar smart-contract development. Niche premium skill — fewer than 200 production Soroban devs globally. We've shipped one of them.

Stellar / Soroban contract work
$250/hr · $2k–$22k project

Soroban's transactional model (footprint declarations, storage TTL, fee-bump structuring) catches Rust generalists. We've shipped a 5-crate Stellar liquidator and know which SDK features are stable vs which will burn you in six months. Compatible with SDF/SCF grant deliverable formats.

  • Contract development (testnet + mainnet, integration tests, deploy scripts): $5k–$15k
  • Code review / audit (5-signal scoring, written findings, fix-review): $2k–$8k
  • Liquidation bot deployment (Blend / custom lending markets): $5k–$12k
  • EVM → Soroban migration: $8k–$22k
SDF grant compatible · async over email or Signal · USDC on Stellar OK

Liquidation Bot Playbook

14-day playbook + sanitized reference snippets to build a production Aave V3 liquidator on Base or any EVM L2. The gotchas no audit firm wrote down. Self-serve, async support, three tiers.

What it is: a structured 14-day plan with concrete acceptance criteria, sanitized Rust + Solidity reference snippets, Foundry test patterns, deploy scripts for both macOS launchd and Ubuntu systemd, and a gotchas appendix covering the two non-obvious WSS subscription bugs (Chainlink proxy → impl, QuickNode silently dropping multi-address eth_subscribe) that cost us 9.5 hours of silent failure to find.
Reader
$99

Self-serve. Written playbook + reference snippets + JSON spec for agent automation. Email support, no SLA.

Builder
$299

Reader + async Q&A over email/Signal within 30 days + one round of contract code review before mainnet. 48-hour response SLA.

Operator
$999

Builder + full deploy support for one mainnet chain + 30 days of async support + performance review at day 30. Permission to use code commercially.

Prefer USDC? Email [email protected] for crypto checkout (0.5% discount on Base).

What's not in the playbook: three alpha-grade features stay out so the playbook doesn't make a $99 buyer's bot match ours. The CEX divergence predictor (front-runs Chainlink updates by ~3-10s), the mempool-adjacent whale-piggyback strategy (grabs close-factor leftovers in-block), and the atomic batch path with multi-collateral support. These live in the DLE Engineering custom build engagement above.

Tools we publish

Proof we know what we're doing. Use them, audit them, fork them.

Aave V3 Health Factor Monitor
Live · Free · MIT

Paste any wallet address, see live HF + position breakdown + oracle freshness for Aave V3 on Base and Optimism. Read-only. Correctly resolves Chainlink AggregatorProxy → impl (the WSS gotcha we document in the playbook).

OracleFreshness
Verified contract · MIT

Stateless safe-read for Chainlink feeds — staleness + L2 sequencer-uptime + grace-period + non-positive-price guards in one call. 11 passing Foundry tests. Use it as a library reference or call the deployed address directly.