Smart contract development, from a single contract to a full protocol

We design and implement smart contracts in Solidity for DeFi protocols and blockchain products. Every engagement follows the same method, scaled to its size. We specify the invariants first, build in phases with their own tests, and hand over documented code prepared for an independent audit.

FIG. S-01 · SCALE OF ENGAGEMENTSAME METHOD
01 CONTRACT02 MODULE03 PROTOCOL
MODEL
Milestones or day rate
STACK
Solidity · Foundry · EVM L1/L2
TESTING
Unit · fuzz · stateful invariants
PRICES
Exclude VAT where applicable

01 / WHO THIS IS FOR

Who this is for

  1. Teams building a new DeFi protocol who need someone to own the smart contract layer
  2. Projects launching a token, an NFT collection or an onchain feature that want it built carefully from the start
  3. Teams with an existing codebase that needs new features, a refactor or integration with other protocols

02 / WHAT WE BUILD

What we build

B-01

DeFi protocols

Vaults (ERC-4626), lending markets, AMMs, liquidation engines and staking systems, with directed rounding, a single accounting path and solvency checks designed in from the start.

B-02

Oracles and price feeds

Chainlink and Pyth integrations with staleness, confidence and deviation checks, and custom oracle setups where no commercial oracle covers your network.

B-03

Tokens and NFTs

ERC-20 tokens with vesting or emission schedules, ERC-721 and ERC-1155 collections, and permissioned tokens following ERC-3643 (T-REX).

See Asset Tokenization
B-04

Protocol integrations

Contracts that plug into existing protocols such as Uniswap, Aave or Compound, including flash loans and leveraged strategies.

B-05

Gasless user flows

EIP-712 signed intents and EIP-7702 delegated accounts for one-click interactions where users do not pay gas.

SMALL PROJECTS WELCOME

Not every engagement is a protocol

Smaller work we take on includes

  • A token with vesting or a custom emission schedule
  • An integration with an existing ERC-4626 vault or lending market
  • Reviewing and extending a contract you already have
  • Adding tests and invariants to an untested codebase

03 / HOW AN ENGAGEMENT WORKS

How an engagement works

  1. 01ScopeA call and a short written scope with milestones, deliverables and a quote.
  2. 02SpecificationInvariants, roles, failure modes and the test plan, agreed before any code.
  3. 03Phased buildEach milestone is delivered with its own unit, fuzz and stateful invariant tests.
  4. 04Hardening and handoverStatic analysis, coverage review, documentation and NatSpec, plus support for your team during the audit.

04 / WHAT YOU GET

What you get

DELIVERABLEFORM
Solidity contracts with NatSpec documentationRepository
A Foundry test suite with unit, fuzz, stateful invariant and, where relevant, fork testsRepository
A specification with the system's invariants and failure modesDocument
Deployment scripts and a written record of the design decisionsRepository · Document

06 / FAQ

Questions about development

Which languages and tools do you use?

Solidity and Foundry, with Slither and Aderyn for static analysis. Yul where gas optimization justifies it.

Can you deploy the contracts for us?

We prepare the deployment scripts and can run testnet deployments. Mainnet deployments are done with your keys, with our support, so control of the contracts stays with you from day one.

Do you write upgradeable contracts?

When the project needs it, using standard proxy patterns, and we document the trade-offs. For many protocols an immutable deployment is the safer default.

Will the code be audited?

We prepare it for an audit and recommend one for any contract that will hold user funds, and we can handle the remediation afterwards. We do not audit our own code.