Colour theme
Book a consultation

How blockchain works and when a business needs it

Learn how shared blockchain records work and assess participants, permissions, corrections, privacy and operating costs before choosing a business use.

A phone, laptop, glasses and calendar beside the word blockchain on a desk.

A blockchain is a way for a network to maintain a shared record. It may be useful when several organizations need to agree on changes and the rules for accepting them. Many business processes can also use a conventional database with permissions and an audit trail.

Before buying or building anything, describe who needs to write, verify and read the record. That requirement gives you something concrete to compare.

Understand the shared record

Transactions are grouped into blocks. Cryptographic hashes connect blocks to earlier records, helping make changes detectable. Participants follow a consensus process to accept updates. Consensus rules differ: some networks use proof of work, others use different approaches. Mining isn’t a requirement for every blockchain.

NIST’s blockchain overview describes these building blocks and the limits of claims about immutability. A blockchain can be tamper evident and resistant without being impossible to change under every circumstance.

A ledger entry is only as accurate as the information put into it. A supply-chain entry saying a shipment was inspected still needs reliable evidence from the inspection.

Know who participates and governs

Public, permissionless networks and private, permissioned networks have different participation rules. Neither removes the need to understand who sets rules, operates infrastructure and resolves disputes.

For example, Hyperledger Fabric’s documentation describes a permissioned platform with identified participants and configurable policies. That differs from assuming anyone can publish or read every business record.

Ask a supplier to name the participating organizations, the rules for accepting changes and who’s responsible for what. What happens if one participant leaves, loses a key or stops operating its systems? Who can approve a software change, and how do the other participants accept it?

Check privacy before putting records on a ledger

Hashing and digital signatures don’t by themselves encrypt a record. Public visibility, access restrictions and encryption are separate design questions.

Request a data-flow diagram showing exactly what enters the ledger and what stays elsewhere. Use fictional information during evaluation. Don’t put customer, employee or health records into a pilot because the product calls itself secure.

Have the people responsible for privacy and records management assess access, retention and correction requirements. Keeping an attachment outside the ledger still requires a review of the identifiers or references recorded inside it.

Plan corrections and automated actions

Business records need a way to address mistakes. Ask how an incorrect entry is corrected, how the correction is displayed and what later decisions already relied on it.

Some platforms run code called smart contracts when specified conditions are met. That code needs testing, limits on what it’s allowed to do and a process for failures or changes. It can run without error and still apply the wrong rule or act on bad information.

For a shipment pilot, test a duplicate submission, an incorrect quantity, a disputed acceptance and an unavailable participant. Check the resulting records and the human handoff in each case.

Compare the full operating cost

Include integration, identity management, hosting, support, transaction charges where applicable, upgrades, key recovery and exit. Resource use depends on the network’s design; don’t assume every implementation has the same mining costs.

Compare the proposed design with a shared application or database meeting the same requirements. Measure the work needed to reconcile records and handle disputes in both options. Base any claim of faster transactions or lower costs on those measurements.

Decide what a pilot must prove

Write down the problem, required participants, sample workflow, acceptance criteria and budget before development. Include a usable export and a process for ending the pilot.

If the participating organizations haven’t agreed on governance and correction rules, settle those questions first. IT consulting can help frame the requirement and compare the implementation options.


Featured Image Credit