Decentralization is an operating model and a legal problem at the same time. A protocol with no issuer, no company and no operator is genuinely difficult to regulate — and equally difficult to bank, to contract with, or to make accountable when something goes wrong.
We work the seam between the two. What the token actually does, who controls what, how governance decisions become legally effective, how the treasury is held and by whom, and where the regulatory perimeter falls once the system has real users and real value.
The engagements span protocols designing a legal wrapper, DAOs that need to transact with the ordinary world, and web3 businesses that have to be legible to banks, exchanges and institutional counterparties.
- You are launching a protocol or DAO and need a structure that can hold assets, contract and transact.
- Your token design and your decentralization claims do not match what the team actually controls.
- A bank, exchange or institutional partner needs to understand what your entity is and who is accountable.
- Governance, treasury or upgrade authority is concentrated in a way that creates regulatory exposure.
Decentralization is a spectrum
Almost nothing is fully decentralized on day one, and the degree of control exercised by the founding team is exactly what regulators look at. We make the control map explicit rather than assumed.
Governance needs a legal counterpart
An on-chain vote is not executable in most legal systems. Something off-chain has to hold assets, sign contracts and be answerable — and that design is where most web3 structures fail.
Treasury is the concentration point
A protocol treasury is a large, publicly visible pool of value. How it is held, who can move it and under what authority is both the security question and the regulatory one.
- Control and decentralization assessment, with the regulatory implications named
- Token design review and its securities position across target markets
- DAO or foundation legal wrapper, governance architecture and delegation model
- Treasury custody, multi-signature and authority design
- Compliance framework appropriate to the protocol’s real risk profile
- Exchange, banking and institutional counterparty onboarding support
- 01
Map control
Who can upgrade, pause, mint, move treasury or change governance — mapped factually, because that map is what determines the legal position.
- 02
Design the wrapper
Foundation, association, trust or company structures, chosen for what the protocol needs to do rather than for what is fashionable.
- 03
Token and governance
Token mechanics tested against securities regimes, and a governance model where on-chain decisions have an off-chain counterpart that can act.
- 04
Treasury and custody
Authority, multi-signature, key management and the legal basis for holding protocol-owned value.
- 05
Become legible
The documentation, policies and counterparty-facing answers that let banks and exchanges onboard you.
Structure and control review
A written assessment of your control map, token position and structural options, with the exposure named.
Wrapper and governance build
Full structural design — wrapper, governance, treasury authority — implemented and documented.
Counterparty readiness
Preparing the legal file and answers that banks, exchanges and institutions require to onboard a protocol.
- Projects whose decentralization claim is marketing rather than architecture — the control map always tells the truth.
- Teams seeking a structure that gives them full operational control while claiming none of the accountability.
If it holds assets, signs contracts, employs contributors or faces counterparties, it effectively needs one — because otherwise there is no party who can be contracted with or held responsible. A foundation or association wrapper usually provides that without destroying the decentralized governance model.
In some designs and markets, yes — and the analysis is about the promises and the control, not the label. What we caution against is assuming that adding a governance vote or a "utility" description removes the securities question. Frequently it does not, and the safer course is to design for the answer rather than hope for it.
Through a legal wrapper that a bank can actually onboard, plus a clear answer to who controls funds and how. Banks do not onboard protocols; they onboard entities with governance, policies and accountable officers. Building that is usually the unglamorous work that unlocks everything else.
Treasury design is where security and regulation meet. We set the custody model, the signing authority and the legal basis for holding protocol value, then document it so counterparties and auditors can rely on it rather than taking it on trust.