Skip to content
HomeAboutServicesContact

Compliance and business logic audit

Your architecture decides which licences you need. We map it before a regulator does.

What it is

Licensing is a function of how the product is built, not how it is described. Custodial wallets trigger custody obligations. An in-house matching engine triggers trading-venue obligations. A fiat leg through your own account triggers payments obligations.

We walk each technical design choice and name the specific licence or duty it triggers in each target market, then show which of those triggers are design decisions you could simply remove.

FEATURETRIGGERSCustodial walletsVARA custodyOwn matching engineMiCA tradingCard on-rampPSD2 / e-money

What we examine

  • Every feature traced to the licence or obligation it triggers, market by market.
  • Worked example: custodial wallets need a VARA custody licence in the UAE, non-custodial does not.
  • Assessed against EU MiCA, UAE VARA, Singapore PSA and US exposure.
  • Business logic review: does the product do what the documentation promises?
  • Fee flows, reward accounting and incentive design checked against the pitch.
  • Engineering alternatives that remove a licensing trigger entirely, so you buy the licence you actually need.
  • One written assessment your counsel and your board can both use.

What you get

01

A feature-to-licence matrix across your target markets.

02

The engineering alternatives that remove a trigger, with what each one costs you in product terms.

03

A launch-readiness view: what is cleared, what is in progress, what is blocking.

04

A document your lawyers can work from, written by engineers who read the code.

Compliance audit report

Licensing and regulatory fit for every target market.

Read the sample

How the engagement runs

  1. 01

    Scope

    Target markets, product surface and the flows that move value, plus a fixed quote.

  2. 02

    Trace

    Each feature followed to the obligation it triggers, in each market.

  3. 03

    Assess

    Where the design forces a licence, and where a different design removes the need.

  4. 04

    Report

    The matrix, the alternatives and the readiness view, in one document.

What we cover

Languages

  • Solidity
  • Vyper
  • Rust
  • Move
  • Cairo
  • Go
  • TypeScript
  • Huff
  • Yul

Chains

  • Ethereum
  • Solana
  • BNB Chain
  • Polygon
  • Avalanche
  • Arbitrum
  • Base
  • TRON
  • Optimism
  • Cardano
  • Polkadot
  • Cosmos
  • NEAR
  • Aptos
  • Sui
  • TON
  • Hedera
  • Algorand
  • Stellar
  • Starknet
  • ZKsync Era
  • Linea
  • Sei
  • Sonic
  • Scroll
  • Mantle
  • Injective
  • Cronos
  • Celo
  • Gnosis
  • Fantom
  • Kaia
  • Ronin
  • Immutable
  • Blast
  • Berachain
  • Monad
  • Hyperliquid EVM
  • Stacks
  • Rootstock
  • Kava
  • Osmosis
  • MultiversX
  • Conflux
  • Telos
  • Theta
  • Chiliz
  • XDC Network
  • Filecoin FVM
  • Ontology
  • WEMIX
  • Fuel
  • Taiko
  • Polygon zkEVM
  • BOB
  • Fraxtal
  • Mode
  • ZetaChain
  • Metis
  • Manta Pacific
  • IOTA EVM
  • Neo X
  • Unichain
  • World Chain
  • Soneium
  • Abstract
  • Ink
  • Movement
  • Plume
  • Etherlink
  • EOS
  • Flow
  • Zilliqa
  • Harmony
  • Moonbeam
  • Astar
  • Aurora

Not listed? Ask. If it runs smart contracts, we almost certainly review it.

Questions we get asked

Is this legal advice?

No. We are engineers who map what your architecture triggers, and we name the regimes in general terms. How a regime applies to your specific facts is a question for licensed counsel in that jurisdiction, and our report is built to be handed straight to them.

Which markets do you cover?

EU under MiCA, the UAE under VARA, Singapore under the PSA, and US exposure. Other markets on request; we will say plainly if a jurisdiction is outside what we can assess.

We already have lawyers. Why do we need this?

Because your lawyers cannot read your codebase. The gap between what the product does and what the legal team believes it does is where licensing surprises live. This closes it.

Can you help us avoid needing a licence?

Sometimes, and legitimately: non-custodial key handling removes custody obligations, a licensed partner on the fiat leg removes payments obligations. The cheapest licence is the one your architecture never needs.

Often bought with

Tell us what you are building and when you launch. Fixed quote in 48 hours.

Get a fixed quote