Development
Smart contract development
Solidity contracts and the APIs around them, from a team that led four blockchain products between 2017 and 2019.
In short
We write, test and integrate Solidity smart contracts on Ethereum and EVM chains such as Polygon, Arbitrum and Base: tokens, registries, vesting and escrow, plus the wallet flows, event indexing and APIs around them. Every contract runs on testnet before mainnet, and anything holding real value gets an independent audit too.
Contracts that hold money should be boring. We write boring contracts.
Between 2017 and 2019 we led blockchain development on four products, on Ethereum and QTUM: token platforms, an exchange backend and a registry for lost and stolen property. Most of it is under NDA. The lesson from all of it: keep on-chain logic small and put everything else in normal, testable services.
Today we help teams that need a contract written, reviewed or connected to a real product, including AI products that act or settle on chain.
Every contract is fully tested, documented with its threat model and deployed to testnet before anything touches mainnet.
Around the contracts we build the parts users actually touch: wallet connection, transaction status that makes sense to a non-crypto user, event indexing so your app reads chain data from a normal database, and admin tools for the operations team. Most of your users shouldn't need to know there's a blockchain underneath.
Is this for you?
You'll get the most out of this if
- You need a token, registry, vesting or escrow contract written and tested
- Your app needs to read and write to a chain without exposing users to the mess
- You want a second pair of eyes on a contract before an audit
- You're connecting AI agents to on-chain actions
Deliverables
What you walk away with
- 01
Tested contracts
Solidity with full test coverage in Hardhat or Foundry, deployed to testnet before mainnet.
- 02
APIs in front of the chain
Node.js services that index events and wrap transactions, so your app talks to a normal API.
- 03
Audit-ready code
Clear docs and threat notes, so an external audit is faster and cheaper.
- 04
Deployment and handover
Scripts, addresses, verified source and a runbook for upgrades.
Timeline
How the project runs
Typical timings for a first live version. We confirm yours in writing after discovery.
Week 1
Design
What has to be on chain and what doesn't. Usually less than you think.
Weeks 2 to 4
Build and test
Contracts and tests, then the API layer that wraps them.
Week 5
Testnet
Run it as if it were live, with your app connected.
After audit
Mainnet
Deployment, verification and monitoring.
Usual stackSolidity, Ethereum, EVM chains, Hardhat, Foundry, OpenZeppelin, ethers.js, viem, Node.js, The Graph
Why a small studio
The person who scopes your project is the one who builds it, and the one who picks up when it breaks at 2am.
- The founder is on your project
- Hussain leads every build himself. You won't brief an account manager who briefs a developer who briefs someone else.
- Three people, the output of ten
- We build with Claude, Codex and our own agent tooling every day. A small senior team now covers what used to need a department.
- We stay after launch
- Evals before every release, a log of each AI decision, cost limits and someone on call. Month six matters more to us than demo day.
- Your repo, your cloud
- The code sits in your GitHub and runs in your AWS, GCP or Azure account from the first commit, on tools your next hire already knows.
- Projects shipped
- 115
- since 2014
- Clients served
- 53
- US, UK, EU, Middle East, APAC
- Average rating
- 5.0
- 113 of 113 rated jobs
- Years shipping software
- 18
- the founder, since 2008
FAQ
Questions people ask
Do you do security audits?
We review contracts and write them to be audit-ready, but for anything holding real value we always recommend an independent audit firm as well.
Which chains?
Ethereum and EVM-compatible chains such as Polygon, Arbitrum, Base and BNB Chain. We've also shipped on QTUM.
Can you work with our existing contracts?
Yes. We start by reading them and the deployment history, then decide with you whether to extend, migrate or leave them alone.
Should our contract be upgradeable?
Only if you need it. Upgradeable proxies let you fix bugs, but they also let someone change the rules, which users may not trust. We'll walk through the trade-off and often recommend a small immutable core with upgradeable periphery.
Why does an AI studio do Web3?
Because we did it first. Blockchain taught us to design systems where mistakes are expensive and permanent, which turns out to be good training for letting AI agents loose on real systems.
Keep exploring
Goes well with
- AI agentsAgents that read what comes in, decide what to do and do it, with a person in the loop where it matters.
- Web apps (Next.js & React)SaaS products, dashboards and portals in Next.js and React, from the first commit to launch day.
- Node.jsAPIs, real-time systems and integrations in Node.js and TypeScript that stay fast under load.
Start here
Let's scope yours.
Send a few lines about the workflow or product. You'll hear back from Hussain within a working day with questions, a rough shape and a ballpark.