What enterprises ask before they commit to a chain
Gagan Mac, Circle
Moment at 45:48Episode 4 · TradFi Goes Onchain: Who's Building the New Financial System?
Enterprise Blockchain Development
In short
Enterprise blockchain is about getting compliance, custody, and audit trail right. We build institutional blockchain systems, permissioned ERC-3643 tokens, on-chain compliance, and institutional custody on public and permissioned networks, with real regulated delivery behind us: the DEX core for Swarm Markets, a BaFin-licensed DEX at launch, and a UNICEF and ITU deployment (Giga).
Reviewed by Renat Khasanshyn, Chief Executive Officer at ProtofireLast reviewed: October 2026
$2B+
secured on the Safe deployments we built across 120+ EVM networks
250+
projects since 2016
95+
protocols
1M+
developers (Solhint)
Trusted by teams building on-chain
Enterprise blockchain is not the same problem as a consumer dApp. A bank, an asset manager, or a public institution needs the compliance, custody, and audit trail regulators and boards require, on a network their counterparties will actually use. The engineering is in getting identity, permissions, controls, and reporting right, so that value only moves between eligible parties and every action is provable after the fact.
Protofire has shipped 250+ blockchain projects since 2016, and the regulated end of that record is real, not aspirational. We built the DEX core and subgraph for Swarm Markets, a BaFin-licensed decentralized exchange at launch where only KYC-verified wallets can trade tokenized securities.
We built the on-chain monitoring for Giga, a UNICEF and ITU initiative connecting schools across countries, a government-grade deployment measured in tens of thousands of sites. We build on the permissioned Polymesh security-token chain, and we engineer institutional credit systems on Aave.
We maintain Solhint, the Solidity linter used by 1M+ developers, so the contracts an institution relies on hold to the standard the ecosystem checks against.
We build the enterprise system you need: permissioned ERC-3643 tokens, compliance enforced in code, institutional custody and governance, and the assurance and operations around them, on the public or permissioned network your use case requires. Take the full build or the specific layer that is blocking your compliance sign-off.
The enterprise blockchain stack we build, from compliance to custody
Enterprise systems live or die on the layers around the token: who is eligible, who can approve, and what can be proven later.
01
Compliance
KYC, AML, and Travel Rule screening plus on-chain identity (ONCHAINID), enforced in the contracts rather than bolted on after deployment.
02
Permissioned tokens
ERC-3643 security tokens with transfer rules, whitelists, and role-based controls, so only eligible parties can hold or move value.
03
Custody & governance
Safe multisig and MPC-custodian integration, policy and approval matrices, and treasury controls sized for an institution.
04
Network
Public EVM chains and permissioned, regulated chains such as Polymesh, chosen for the compliance and counterparties the use case requires.
05
Assurance & ops
Proof of Reserve, monitoring, indexing, and 24/7 operations under SLA, plus the audit trail regulators and boards expect.
01
What enterprise blockchain development covers
Most enterprise use cases need a token only eligible parties can hold. We build permissioned tokens on ERC-3643 (the T-REX standard), with on-chain identity through ONCHAINID, whitelists, and transfer rules that enforce eligibility in the contract itself.
Our regulated-venue experience is first-hand: we built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified participants can trade, working underneath Swarm's own permissioning layer. The permission logic has to be correct and hardened before it reaches an audit. Benefits: eligibility enforced in code, not policy, on-chain identity and transfer rules, built for a venue that launched under BaFin licenses.
We wire KYC, AML, transaction screening (KYT), sanctions, and Travel Rule checks into the product and enforce them on-chain, integrating the screening providers you already use. Our compliance work is grounded in regulated venues: we built the DEX core and subgraph for a KYC-gated venue that launched under BaFin licenses, and we design for regimes like MiCA rather than retrofitting them.
The goal is a system where an ineligible transaction is blocked at the contract level. Benefits: KYC, AML, and sanctions enforced on-chain, screening providers of your choice, designed for MiCA and BaFin-grade scrutiny.
An institution cannot hold assets behind a single private key. We deploy and customize Safe smart-account infrastructure for multisig control, and we integrate Fireblocks or an MPC custodian for institutional key management, without ever holding your funds.
On top of that we build the governance an organization needs: policy and approval matrices, scoped permissions, and treasury controls, so who can approve what is defined and provable. We deployed Safe on 120+ EVM networks, where it secures $2B+. Benefits: multisig and MPC custody, policy and approval matrices, treasury controls sized for an institution.
Enterprise blockchain does not mean one architecture. We build on public EVM networks when composability and liquidity matter, and on permissioned, regulated chains such as Polymesh when the use case demands built-in identity and securities rules. Our public work includes the Polymesh explorer built on the Polymesh SDK.
We choose the network your compliance and counterparties require, rather than defaulting you onto an architecture that strands you or that we cannot support in production. Benefits: public or permissioned, chosen for your compliance, not our convenience, real experience on regulated chains.
Regulators, auditors, and boards need to verify what happened. We build Proof of Reserve attestation for backed assets, the oracle and indexing layers that make on-chain state queryable and auditable, and 24/7 managed operations under SLA.
We built the on-chain monitoring for Giga, a UNICEF and ITU initiative tracking school connectivity across tens of thousands of sites, so operating a system at institutional scale is something we have done, not just designed. Benefits: Proof of Reserve and audit trail, monitoring and indexing for oversight, 24/7 operations under SLA.
02
How an engagement works
1
Scope & compliance design
A discovery that maps the regulatory requirements, the eligible parties and permissions, the custody model, and the network choice, and turns them into an architecture that a compliance team can sign off. Deliverable: a scoped architecture and compliance-control plan.
2
Build & integrate
The permissioned token and compliance contracts, the custody and governance layer, and the assurance and data plumbing, built, integrated with your existing systems and screening providers, and hardened ahead of an external audit.
3
Deploy & operate
Deployment on the chosen network, handover, and an option to keep us on for 24/7 managed operations, monitoring, and reporting once the system is live.
03
What institutions come to us for
A permissioned, KYC-gated token on ERC-3643
Compliance (KYC, AML, sanctions, Travel Rule) enforced on-chain
A regulated trading or settlement venue
Institutional custody, multisig, and treasury governance
Government or public-sector on-chain systems
Institutional-grade infrastructure, assurance, and 24/7 operations
04
Enterprise blockchain we have actually shipped
Protofire is a blockchain development company with 250+ projects across 60+ networks and 95+ protocols since 2016, and the regulated, institutional end of that work is first-hand. We built the DEX core and subgraph for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets can trade tokenized securities.
We built the on-chain monitoring for Giga, a UNICEF and ITU initiative connecting schools across countries. We build on the permissioned Polymesh security-token chain, and we engineer institutional credit systems on Aave.
We build permissioned tokens and on-chain compliance, we deployed Safe on 120+ EVM networks, where it secures $2B+, and we integrate Fireblocks and MPC custodians for institutional key management. We maintain Solhint, the linter used by 1M+ developers, so the contracts an institution relies on hold to the standard the ecosystem sets.
“Only eligible parties can hold the asset, only authorized signers can approve, and every action is provable after the fact.”
Open source we’ve shipped
The Protofire repositories behind this page
Public vs permissioned networks for enterprise
| Dimension | Public EVM | Permissioned (e.g. Polymesh) |
|---|---|---|
| Access control | At the token and identity layer (ERC-3643) | Built into the protocol |
| Liquidity and composability | Deep | Limited to the network |
| Compliance | Enforced in the contracts | Enforced at protocol and contract level |
| Best for | Regulated products needing liquidity and tooling | Securities use cases needing native identity rules |
FAQ
What is enterprise blockchain development?
Enterprise blockchain development is building on-chain systems that meet the compliance, custody, and audit requirements an institution operates under, rather than a consumer application. Most of the engineering is in identity and eligibility (who is allowed to hold or move value), permissions and approvals (who can authorize what), controls (limits, freezes, sanctions screening), and the audit trail that proves every action after the fact. For a bank, asset manager, fund, or public body, those layers are the product. Protofire builds them as delivered systems, permissioned ERC-3643 tokens, compliance enforced on-chain, institutional custody, and the assurance around them, drawing on real regulated work such as the DEX core we built for Swarm Markets, a BaFin-licensed DEX at launch, not a reference architecture.
Do you build on private, permissioned, or public chains?
We build on whichever fits the requirement, and we help you choose rather than defaulting to one. Public EVM chains give you composability, liquidity, and a deep tool ecosystem, and are often the right choice even for regulated products when access is controlled at the token and identity layer. Permissioned, regulated chains such as Polymesh have securities rules and identity built into the protocol, which suits some institutional securities use cases; we have built on Polymesh directly. The decision is driven by your compliance obligations, your counterparties, and where liquidity and assurance actually sit, not by a preference for a particular architecture. We scope that choice with you in the design phase and are candid about the trade-offs of each. The networks institutions use today, public, institution-run and private, are compared in our guide to how an institution chooses a chain, and Canton work is described on Canton Network development.
How do you handle compliance, KYC, and regulation?
By enforcing it in the contracts, not around them. We wire KYC, AML, transaction screening, sanctions, and Travel Rule checks into the product and enforce eligibility on-chain, so an ineligible party cannot hold or move a restricted asset in the first place. We integrate the screening and identity providers you already use rather than imposing new ones, and we build with regimes like MiCA and licensing frameworks like BaFin's in mind, having built for a venue that launched under BaFin licenses. Permissioned tokens use ERC-3643 with on-chain identity (ONCHAINID) so compliance rules travel with the asset. That venue is Swarm Markets, where we built the DEX core and subgraph underneath Swarm's own KYC and permissioning, so the approach is grounded in a real regulatory bar rather than a generic checklist.
Have you delivered regulated or institutional blockchain systems?
Yes, and they are nameable, public references, not anonymized claims. We built the DEX core and subgraph for Swarm Markets, a BaFin-licensed decentralized exchange at launch for tokenized securities, where only KYC-verified participants can trade. We built the on-chain monitoring for Giga, a UNICEF and ITU initiative tracking school connectivity across tens of thousands of sites in multiple countries, a government-grade deployment. We build on the permissioned Polymesh security-token chain and engineer institutional credit systems on Aave. We deployed Safe on 120+ EVM networks, where it secures $2B+, with zero vulnerabilities across our delivered projects. Enterprise blockchain is not a category we are entering; it is one we have already delivered in, under real regulatory and public-sector scrutiny.
How do you handle institutional custody and governance?
An institution needs keys held and actions approved the way its risk model requires, which a single private key cannot provide. We deploy and customize Safe smart-account infrastructure for multisig control, and we integrate Fireblocks or an MPC custodian for institutional key management, without ever taking custody of your funds ourselves. On top of custody we build governance: policy and approval matrices, scoped permissions, and treasury controls, so authority is explicit and every approval is provable. We deployed Safe on 120+ EVM networks, where it secures $2B+, so this is operational experience rather than a design exercise. The exact model, who holds keys, who approves what, and under which limits, is scoped with your risk and compliance teams.
Can you integrate with our existing systems and banks?
Yes; enterprise work is mostly integration. We connect on-chain systems to the off-chain world an institution runs on: your screening and identity providers, your custody, your reporting and reconciliation, and your data systems, through the oracle, cross-chain, and indexing layers we build and operate. We are a core contributor to Chainlink and ran a top-3 indexer on The Graph from 2020 to 2024 (by indexing rewards), so the data and connectivity layer that ties a blockchain system into existing infrastructure is a core strength, not an afterthought. We scope the integration surface in the design phase and build to fit your systems rather than asking you to rebuild around ours.
Discussed on The Protocol Roundtable
All episodesGet a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
Budget
I accept the
Privacy PolicyI agree to receive new research announcements as well as information about Protofire services and special offers
An NDA is available from the first message and can cover anything you share. How it works