Skip to content

Smart contracts and Web3 features, built carefully

Solidity smart contracts on Ethereum and EVM chains, wallet connection and sign-in, tokens and NFTs inside a web or mobile app, and dashboards built on on-chain data. Everything is tested, built on audited libraries and deployed to a testnet first. And if you don't need a blockchain at all, we'll say so.

We reply within one working day. 020 3540 5048

Problems you shouldn't have to live with

  • You're not sure you need a blockchain

    The pitch sounds right, but nobody has said plainly what a chain does here that a normal database can't. Building the wrong thing is the most expensive mistake in this space.

  • Code you can't patch later

    Once a contract holds value, a bug is a loss, not a ticket. Most contracts can't be changed after deployment, so the testing has to happen before mainnet, not after.

  • Wallets put ordinary users off

    Seed phrases, gas fees and network switching lose people before their first transaction. A Web3 product still has to feel like a normal app to the people using it.

  • Rules you find out about too late

    UK financial promotion rules for cryptoassets and Apple's rules for crypto apps both limit what you can build and say. Learning that after the build is expensive.

How we solve it

  1. 1

    A straight answer first

    A short scoping stage works out whether anything needs to be on-chain and which parts. Most products end up hybrid: ownership or settlement on-chain, everything else in a normal database. If the honest answer is that you don't need a blockchain, we say so and quote the simpler version.

  2. 2

    Smart contracts in Solidity

    Contracts for Ethereum and EVM-compatible chains such as Base, Arbitrum, Optimism and Polygon, built on OpenZeppelin's audited libraries for tokens (ERC-20, ERC-721, ERC-1155), access control and upgrades. Tested with Hardhat or Foundry and deployed to a testnet before anything goes near mainnet.

  3. 3

    Wallet connection and sign-in

    WalletConnect and browser wallets for connecting, and Sign-In with Ethereum (EIP-4361) so people can use their wallet as their account. Where the audience isn't crypto-native we design the flow so the wallet stays in the background as far as the product allows.

  4. 4

    Tokens and NFTs inside your app

    Balances, minting, transfers and gated areas inside web and mobile apps, built around what Apple and Google allow an app to do with them, so the feature you plan is one that passes review.

  5. 5

    On-chain data dashboards

    Indexers, using The Graph or one we run for you, feeding Next.js dashboards: holders, treasury, activity and the metrics your team or community needs to see, as readable charts rather than block explorer links.

  6. 6

    Security as a process, not a promise

    Tests for every function and failure case, static analysis, audited libraries rather than hand-rolled ones, a testnet deployment you can try, and an independent audit recommended before mainnet for anything holding value. We are not auditors, and we won't let that sentence get lost.

Technologies we use

Solidity Hardhat Foundry OpenZeppelin ethers.js viem wagmi WalletConnect Sign-In with Ethereum The Graph Next.js Swift Kotlin Node.js

Before you build

What to know before you build on a blockchain

Four things we go through with every client in the first call. None of them is a reason not to build; all of them change what you should build.

  1. 1

    When you don't need a blockchain

    A blockchain earns its place when several parties who don't trust a single operator need to agree on a record, when users hold assets they can take elsewhere, or when the public has to be able to verify what happened. If one company controls the data and nothing needs to be transferable, a normal database is cheaper, faster and far easier to change. Loyalty points, internal records and most marketplaces fall into the second group. We'll tell you which group your idea is in before you spend anything.

  2. 2

    How we keep contracts safe

    We write automated tests for every function and every way it can fail, run static analysis, and build on OpenZeppelin's audited contracts rather than writing token or access-control code from scratch. Every contract is deployed to a testnet first, where you can use it with test funds.

    For any contract that will hold real value, we recommend an independent audit before mainnet, by a firm whose job that is. We are developers, not auditors: we'll help you brief the auditor and fix what they find, but we don't certify our own work.

  3. 3

    UK rules on promoting cryptoassets

    Since 8 October 2023 the FCA's financial promotions regime has applied to cryptoassets. Promoting a qualifying cryptoasset to UK consumers is a criminal offence unless the promotion is made or approved by an FCA-authorised firm, or falls within an exemption, and approved promotions carry prescribed risk warnings and a cooling-off period for first-time investors. That covers websites, apps and social posts.

    We build the software. You are responsible for the regulatory position of anything you promote or sell through it, and we don't advise on that: speak to a solicitor who specialises in financial regulation before you launch.

  4. 4

    Apple's rules for crypto apps

    App Store Review Guideline 3.1.5 sets out what a crypto app may do: wallets may store virtual currency only if the developer is enrolled as an organisation; apps may not mine on the device; exchange features are allowed only through an approved exchange and only in regions where the app has the licences to offer them; ICOs, crypto futures and similar must come from established banks, securities firms or other approved financial institutions; and apps may not pay out cryptocurrency for tasks such as downloading other apps or posting to social networks.

    Separately, an app may show NFTs a person owns, but owning one can't unlock features in the app, and selling NFTs or NFT services inside the app goes through In-App Purchase. We design iPhone features around these rules from the start so the version you build is the version Apple approves.

After launch

Keep it working after launch

Websites and apps need looking after once they're live. Ongoing development is the plan most people choose after this, at from £1,500 a month.

Already have an app or site that needs looking after?

Questions we get asked

Often not, and we'll tell you. A blockchain makes sense when several parties who don't trust a single operator need a shared record, when users hold assets they can take elsewhere, or when the public must be able to verify what happened. If one company controls the data and nothing needs to be transferable, a normal database is cheaper, faster and easier to change.

Ready to talk about your project?

Let's talk about your project and the best way to approach it. No commitment and no pressure, just a conversation about what's possible.