Emerging

On-chain engineering, with an honest answer about whether you need it.

We build smart contracts, wallets and on-chain infrastructure to a security standard that assumes hostile users — and we will tell you plainly when a database would serve you better.

Compose a team All disciplines

What we build

Inside Blockchain & Web3.

Smart contracts

Solidity and Rust contracts with invariant tests, fuzzing and audit preparation.

Wallet & payments

Custodial and non-custodial flows, account abstraction, stablecoin rails.

Indexing & data

Subgraphs and event indexers feeding conventional application backends.

Tokenisation

Asset tokenisation with compliance and transfer-restriction logic.

Security review

Threat modelling, static analysis and pre-audit hardening.

The stack

Tools we actually use in production.

Chains

Ethereum
Base
Arbitrum
Polygon
Solana

Contracts

Solidity
Rust / Anchor
Foundry
Hardhat
OpenZeppelin

Application

viem
wagmi
ethers.js
WalletConnect
Privy

Data & security

The Graph
Alchemy
Tenderly
Slither
Echidna

Comparison

Do you actually need a chain?

We start from the problem. Most products asking for blockchain need auditability or shared state, which cheaper tools provide.

Option	Strength	Trade-off	Choose it when
Conventional database	Cheapest, fastest, fully reversible mistakes.	Trust rests entirely on your organisation.	Almost all products, almost all of the time.
Public L2 (Base, Arbitrum)	Low fees with Ethereum-grade security and liquidity.	Public data, key management burden, immutable bugs.	Open financial products and consumer token apps.
Solana	High throughput and very low transaction cost.	Different toolchain and smaller audit talent pool.	High-frequency consumer and payment use cases.
Permissioned ledger	Shared state between known parties with privacy.	Governance overhead; often outperformed by a shared API.	Consortium settlement between distrusting partners.