01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Web3 development The layer that decides whether anyone actually uses it.
Passkey sign-in, sponsored gas, a recovery path that works, and a fiat ramp that clears compliance. The unglamorous half of a Web3 product.
Sign-in stopped being the problem. Recovery took its place.
The account layer decides whether anyone gets past the first screen, and whether they can get back in six months later.
Smart accounts
ERC-4337 accounts with session keys, spending limits and batched transactions, so a user approves an intent rather than four separate signatures.
ERC-4337BundlersPaymastersSession keys
Passkey sign-in
Onboarding without a seed phrase. Two credentials registered up front, because a passkey lives in one platform keychain and the user who switches phones has lost it.
WebAuthnPasskeysDevice binding
Sponsored gas
Paymaster policies that decide who pays, for what, and up to what limit — with the ceiling enforced server-side rather than hoped for.
PaymastersPolicy engineRate limits
A recovery path that works
Guardian and social recovery designed and then rehearsed, because it is the flow people reach for while panicking and the one teams test least.
GuardiansSocial recoveryTimelocks
The layer between a chain and a product
Most Web3 products fail here rather than in the contract: money cannot get in, or the interface cannot be trusted about what happened.
- 01
Fiat ramps that clear compliance
Provider selection by corridor and licence rather than by landing page, with KYC handled where it belongs and failure states designed instead of discovered.
- 02
Indexing the app can trust
Event indexing that reconciles against chain state and alerts when it drifts, so the interface is not confidently showing a balance that no longer exists.
- 03
Interfaces that survive a reorg
Pending, confirmed and reverted treated as three real states in the product, not one spinner and an optimistic update.
- 04
Custody and key handling
Whether keys sit with the user, with a provider, or in a threshold scheme, the decision is made deliberately and written down with its trade-offs.
Web3 services
Each one sets out what is included, how it is delivered, and the questions people ask before starting.
- Account abstraction & smart walletsERC-4337 smart accounts with passkey sign-in, sponsored gas, session keys and tested recovery, so users never see a seed phrase or a gas prompt.
- Crypto wallet developmentCustodial, non-custodial and smart wallets with passkey sign-in, MPC or multisig security, multi-chain support, swaps and recovery that works.
- Chain abstractionChain abstraction: unified balances, cross-chain intents (ERC-7683), smart accounts and gas sponsorship, so users act on any chain without bridging.
- NFT marketplace developmentNFT marketplaces and minting platforms: ERC-721 and ERC-1155 contracts, listings and auctions, royalties, metadata storage and fiat checkout.
- DAO developmentDAO development: governance tokens and voting, Governor contracts with timelocks, Snapshot voting, Safe treasuries, delegation and proposal tooling.
- Crypto payment gatewaysCrypto payment gateways for merchants and platforms: stablecoin checkout, payment links, confirmations, webhooks, refunds, settlement and accounting exports.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.