Skip to content

BEST COMPANIES · HOW TO CHOOSE

How to choose a blockchain development company: 24 questions to ask before you sign

Choose the blockchain development company that answers four things in writing, with names: who covers the regulated roles, who controls the keys, who owns the code and how you exit the provider. This guide turns those four things into 24 questions, grouped in six blocks, for use in a request for proposal (RFP). It is published by Unknown Gravity, which also builds blockchain software: ask us the same questions you ask any other provider.

How to use this checklist

Send the questions to two or three providers before you ask for quotes, and ask for written answers with names of entities, versions and dates. Compare how each one answers each block: a vague answer is also information. If you have no candidates yet, start with our directory of blockchain development companies, which only includes companies with a checked company registration and public work.

Scope, network and token standard

  1. Which part of the product will live on-chain and which off-chain, and why?
  2. Which network will it be deployed on (Ethereum or another EVM network, XRP Ledger, Hyperledger Fabric…), and which verified contracts or public repositories does the provider have on that network?
  3. Which token standard does it propose, and why? If the token is a security, how will it limit transfers to verified investors, for example with ERC-3643?
  4. Will the contracts be upgradeable? If so, who can upgrade them, with what controls and with what notice to holders?

Regulated roles

  1. Is the token a financial instrument or a MiCA crypto-asset, and which legal advisor has analyzed it? MiCA does not apply to financial instruments (Article 2(4)(a) of Regulation (EU) 2023/1114). The legal advisor makes that call; the provider builds on it.
  2. If it is a security in Spain not admitted to trading, which entity will keep the register (the ERIR under Article 8(4) of Law 6/2023) and how will the platform integrate with it?
  3. If it is a crypto-asset, who will provide the services that require a crypto-asset service provider authorization or being an Article 60 entity (Article 59(1) of MiCA)? Will the technology provider touch your clients' funds or keys?
  4. If you will offer the token in the United States, which registered intermediaries will the platform work with: transfer agent, broker-dealer or ATS, funding portal? Acting as a broker or dealer without registration is unlawful, subject to exceptions (Securities Exchange Act, Section 15(a)), and a Regulation Crowdfunding offering can only be made through a registered broker or funding portal (17 CFR 227.300(a)). More in asset tokenization in the United States.

Custody and keys

  1. Who will hold the deployment and admin keys of the contracts? With multisig, and with what procedure if someone leaves the company?
  2. Who will hold the investors' assets: the investors themselves, an authorized custodian or your company? If your company safekeeps or controls clients' crypto-assets or keys, it provides custody (Article 3(1)(17) of MiCA) and needs an authorization.
  3. If a custodian is involved, does it have the custody service in the ESMA register, and can it operate in your country? We explain it in crypto custody companies.
  4. What happens if an investor loses access to their wallet? How is their position recovered, and who decides?

Code ownership and licenses

  1. Will you receive the source code and the repository, with its history, and from when?
  2. Which components belong to the provider or to third parties, and under what license will you use them?
  3. Will the deployed contracts be verified on the block explorer, with the same code you receive?
  4. In whose name will the domains, cloud accounts and production access be?

Audits, testing and operations

  1. Who will audit the smart contracts, on which exact version and before which deployment? Will you receive the report and the review of the fixes? (more on smart contract audits)
  2. Which automated tests and which architecture documentation are deliverables under the contract?
  3. Who will monitor the contracts in production, and what is the incident plan?
  4. If you are a financial entity, will the provider accept the clauses DORA requires in ICT services contracts (Article 30 of Regulation (EU) 2022/2554): described services, data location, incident assistance and termination rights?

Exit from the provider and budget

  1. How will the system be handed over to your team or to another provider: documentation, access, keys and infrastructure?
  2. Will there be a transition period during which the provider keeps the service running while you migrate? If the service supports a critical or important function of a financial entity, DORA requires one (Article 30(3)(f)).
  3. What does the budget include and exclude, by milestone and with acceptance criteria?
  4. What will it cost per year to maintain, operate and re-audit the system after each significant change?

Red flags

  • It promises returns, go-to-market dates or absolute security.
  • It says it "handles everything regulatory" without naming the authorized entity that will do it.
  • It does not hand over the code or the admin keys, or does not say under what license you will use its components.
  • It proposes auditing after launch, or having the audit done by the same team that writes the code.
  • It cannot show verified contracts, repositories or cases with a named client.

Frequently asked questions

What should a contract with a blockchain development company include?

At least: scope by milestone, transfer of the code and the repository, who controls the keys, an audit before production, maintenance and how you exit the provider. If you are a financial entity, also the clauses in Article 30 of DORA.

Should the technology provider handle the legal side?

No. Classifying the token and structuring the issue are for the issuer's legal advisor, and regulated services (register, placement, custody or trading) are for authorized firms. The provider should build the platform to fit with them.

Is a freelancer or a company better?

It depends on the size and risk of the project: with contracts that move value, continuity, review by someone else and the exit from the provider all matter. We compare both in freelancers or a blockchain development company.

Does this checklist work if I will issue in the United States?

Yes, adapting the regulated roles block: there, the intermediaries are the transfer agent, the broker-dealer or ATS and the funding portal, and the issuer's U.S. securities counsel defines the structure.

How we work at Unknown Gravity

Unknown Gravity is a Spanish blockchain technology company based in Málaga (Commercial Register of Málaga, sheet MA-177027). We build the platform, the smart contracts and the integrations, and we answer these questions in writing when you ask them. In the EU we work with the issuer's legal advisors and with authorized firms; in the United States, with the client's securities counsel and with registered intermediaries. We are not a broker-dealer, funding portal, transfer agent, investment adviser or law firm.

Official sources

Framework verified as of October 14, 2026. Use this checklist with us the same way you would with any other provider. Talk to us.

WHY CHOOSE US

Why choose us?
It's easy.

01

Demonstrated experience

Outstanding experience collaborating with leading companies from different countries.

02

Personalized approach

Each client has unique needs, and we create solutions that are 100% adapted to your vision.

03

Security audits

Our process includes code audits and documented residual risk.

04

Efficiency and scalability

We design platforms that grow with you, optimizing each line of code.