July 28, 2026 · 9 min read · RelayLink Engineering
The network decision is the most expensive one to reverse in a blockchain project. It determines who can participate, what data is visible, how transactions are paid for and which compliance obligations apply. Here is the framework we use with clients.
Public networks such as Ethereum and its layer-2 ecosystems are open to anyone. They offer the strongest guarantees of neutrality and censorship resistance, a large developer ecosystem and mature tooling.
Permissioned networks such as Hyperledger Fabric and Corda restrict participation to known organisations. Consensus is typically cheaper, data can be private between specific parties, and governance is contractual.
Many production systems are hybrid: private data and high-volume operations run on a permissioned network, while proofs, hashes or settlement events are anchored to a public chain for independent verifiability. This is often the right answer for enterprises that need both privacy and public proof.
| Question | Leans public | Leans permissioned |
|---|---|---|
| Who must participate? | Anyone | Known organisations only |
| Who may read the data? | Public by default | Restricted per participant |
| Who pays for transactions? | End users or the product | The consortium |
| What compliance applies? | Product-dependent | Sector regulation, data residency |
| What is the trust anchor? | Open consensus | Contractual governance |
We start from the process, not the technology: who exchanges what with whom, where disputes originate and which records must be independently verifiable. The output is a written recommendation with the trade-offs made explicit — including the option of not using a blockchain at all, when a shared database is the honest answer.
Evaluating blockchain for an enterprise process? Our audit produces a network recommendation, architecture and delivery plan. Book a discovery sprint.