Full Text
1. Introduction
Organizations increasingly depend on information that is created,
updated and exchanged across institutional boundaries. Supply chains
involve manufacturers, logistics providers, distributors, retailers and
regulators. Healthcare information may move among hospitals,
laboratories, pharmacies, insurers and patients. Academic credentials
may need to be verified by universities, employers and professional
bodies. Public records may be maintained by agencies whose systems are
not fully interoperable. In each case, participants need to establish
which information is authoritative, who changed it, when the change
occurred and whether the record can be trusted.
Traditional information systems often address these needs through
centralized databases, trusted intermediaries and bilateral data
exchange agreements. Centralized architectures can be efficient and
appropriate when one organization has legitimate authority, clear
accountability and the capacity to maintain the system. Problems arise
when several independent parties need to write to a shared record but do
not agree that one participant should control it. Reconciliation across
separate databases can be slow, costly and vulnerable to inconsistent
updates. A central intermediary may also become a single point of
failure or a source of institutional dependence.
Blockchain technology emerged as a way to maintain a shared
transaction history across a network of participants using cryptographic
techniques and a consensus process. Nakamoto (2008) introduced Bitcoin
as a peer-to-peer electronic cash system that records transactions in a
chain of blocks and uses proof of work to agree on the order of
transactions without relying on a central financial intermediary.
Although the original design was developed for digital currency, the
underlying ideas of distributed consensus, cryptographic verification
and replicated records have since been adapted to broader distributed
ledger systems.
A blockchain is commonly understood as a ledger in which records are
grouped into blocks, cryptographically linked and replicated across
participating nodes. Digital signatures can authenticate transaction
authorization, while consensus protocols help nodes agree on the ledger
state. The resulting record can be tamper-evident: changing a previously
accepted record would require overcoming the network's validation and
consensus mechanisms. This property can support auditability and shared
verification, but it does not mean that data are inherently correct or
that every blockchain is immutable in an absolute sense.
The rapid growth of blockchain research has produced a wide range of
proposals for supply chain traceability, identity management, health
information exchange, digital rights, land registration, voting,
education credentials and public administration. Some applications use
public, permissionless networks, while others use permissioned networks
in which participation is restricted to identified organizations. Smart
contracts have expanded the scope of blockchain from recordkeeping to
automated execution of agreed rules. At the same time, researchers have
highlighted limitations involving scalability, privacy, energy use,
security, governance and the mismatch between on-chain records and
real-world events (Casino et al., 2019; Yli-Huumo et al., 2016).
This article examines blockchain as an information management
infrastructure rather than treating it as a general-purpose database
replacement. It asks: (1) What technical components make distributed
ledgers function? (2) Under what organizational conditions can
blockchain improve information sharing and trust? (3) Which application
domains offer credible value? (4) What risks and limitations constrain
adoption? (5) How should institutions evaluate and govern blockchain
deployments? The review focuses on sources published by 31 December
2022, so the analysis reflects the research and technical landscape
available entering 2023.
2. Review Methodology
An integrative literature review was selected because blockchain
research spans computer science, cryptography, information systems,
supply chain management, law, public administration and organizational
governance. The subject includes foundational protocols, technical
surveys, conceptual frameworks, case studies and evaluations of
domain-specific applications. These sources use different methods and
performance measures, making a single quantitative synthesis
unsuitable.
The review scope was limited to publications available on or before
31 December 2022. Search concepts included blockchain, distributed
ledger technology, consensus mechanisms, smart contracts, permissioned
blockchain, supply chain traceability, digital identity, data
provenance, healthcare records, privacy, scalability, governance and
information management. Priority was given to peer-reviewed journal
articles and conference proceedings, foundational technical papers,
recognized standards and institutional reports with identifiable
publication details.
The selected literature was organized into six themes: architecture
and cryptographic foundations; consensus and network models; information
management capabilities; applications; security, privacy and legal
challenges; and organizational governance and adoption. Each theme was
analyzed to identify the assumptions required for blockchain to provide
value and the conditions under which a conventional database or trusted
intermediary may be preferable.
This review is integrative rather than exhaustive. It does not claim
to cover every blockchain platform or application. Instead, it
synthesizes influential sources and established research findings to
develop a practical decision framework. The article distinguishes
technical properties, such as hash-linked records and consensus, from
broader claims about trust, transparency and decentralization, which
depend on how the system is governed and used.
3. Blockchain
Architecture and Technical Foundations
A blockchain network is composed of nodes that maintain, validate or
relay transactions and ledger data. A transaction represents an
operation, such as transferring a digital asset, recording an event or
invoking a smart contract. Depending on the platform, transactions may
contain data directly, refer to external data, or update the state of a
program. Nodes verify transactions against protocol rules before
accepting them into the ledger. A block groups transactions and includes
a reference to a preceding block, commonly through a cryptographic
hash.
Cryptographic hash functions map input data of arbitrary length to
fixed-length outputs. A small change in the input is expected to produce
a substantially different hash, making hashes useful for detecting
modification. When each block contains a hash of the previous block, the
sequence forms a tamper-evident chain. If a historical block is changed,
its hash changes and subsequent references no longer match. In a
distributed network, an attacker must also contend with the consensus
process and the copies maintained by other nodes.
Digital signatures provide a mechanism for proving that a transaction
was authorized by the holder of a corresponding private key. A public
key can be used to verify the signature, while the private key must be
protected by the user or an authorized signing service. This supports
non-repudiation within the technical and legal assumptions of the
system, but a signature does not prove that the person controlling the
key is the person they claim to be. Identity proofing, credential
issuance, key recovery and revocation remain separate governance
functions.
A Merkle tree is a data structure that combines hashes of individual
records into a single root hash. It allows a node to verify that a
particular transaction is included in a block without downloading every
transaction in the block. Merkle trees are used in Bitcoin and other
systems to support efficient verification. They are especially relevant
to information management because they can provide compact proofs that a
record or document existed in a particular committed dataset at a
particular point in time.
Blockchain systems differ in how they determine which transactions
are valid and which ledger state is accepted. Consensus mechanisms
coordinate participants who may have different network conditions,
incentives or levels of trust. The design must address faulty nodes,
malicious behaviour, network partitions and conflicting transaction
histories. Consensus is not simply a voting procedure; it is a protocol
with assumptions about identity, communication, incentives and the
proportion or behaviour of adversarial participants.
Permissionless blockchains allow participants to join and validate
transactions without prior approval, subject to protocol rules. Bitcoin
and Ethereum are prominent examples. These systems can support open
participation and reduce dependence on a single administrator, but they
may face challenges involving throughput, transaction fees, public data
exposure and consensus energy use. Permissioned blockchains restrict
participation to known or approved entities. They can support higher
transaction throughput and clearer organizational accountability, but
they require governance over membership, validator selection and
administrative powers.
The distinction between public and private networks is not always
binary. Consortium or federated networks are operated by a group of
organizations that share governance responsibilities. Such arrangements
can be suitable when multiple institutions need a common record but
cannot or should not expose all information to the public. The network
may allow public verification of selected proofs while keeping
transaction details accessible only to authorized members.
Smart contracts are programs deployed on a blockchain and executed
according to protocol rules. They can encode transfers, approvals,
escrow conditions, supply chain events, access permissions and other
workflows. Szabo (1997) introduced the concept of smart contracts as
computerized transaction protocols that execute the terms of a contract.
In modern blockchain platforms, smart contracts can coordinate digital
assets and automate state transitions. However, code execution is not
equivalent to legal enforceability. A smart contract may implement a
business rule incorrectly, depend on inaccurate external data or produce
outcomes that conflict with legal obligations.
Oracles connect blockchain applications to information outside the
ledger, such as market prices, weather observations, shipping events or
identity assertions. This connection is essential because blockchains
cannot independently observe the physical world. An oracle may report
that a shipment arrived, but the ledger cannot prove that the shipment
was actually delivered unless the reporting mechanism is reliable.
Oracle design therefore becomes a trust problem involving sensors, data
providers, attestation, dispute resolution and incentives.
Blockchain data may be stored on-chain or off-chain. On-chain storage
provides shared verification and replication but can be expensive, slow
and difficult to reconcile with privacy or deletion requirements.
Off-chain storage places large files or personal information in
databases, repositories or distributed storage systems, while the
blockchain records hashes, pointers, access events or permissions. This
hybrid approach is common in information management because it preserves
the ability to verify data integrity without placing every document on a
public or replicated ledger.
4. Consensus
Mechanisms and Network Governance
Proof of work, used by Bitcoin, requires participants known as miners
to expend computational effort to propose blocks. The protocol makes
rewriting accepted history costly because an attacker must perform
substantial work and compete with the honest network. This mechanism
supports open participation without a central validator list, but it
consumes significant energy and has limited transaction throughput
relative to many centralized systems. Its security depends on economic
incentives, network distribution and the cost of controlling sufficient
mining power.
Proof of stake selects validators based partly on economic value
committed to the protocol. The mechanism aims to reduce energy use
compared with proof of work and can support different approaches to
finality and validator accountability. However, proof of stake
introduces its own design questions, including validator concentration,
stake distribution, penalties, governance and the security assumptions
of the protocol. It should not be described as automatically
decentralized or risk-free.
Practical Byzantine fault tolerance and related protocols are
commonly used in permissioned settings where validator identities are
known. Castro and Liskov (1999) introduced practical Byzantine fault
tolerance as a method for replicating services despite Byzantine faults,
under defined assumptions about the number of faulty replicas. Such
protocols can provide efficient agreement in consortium networks, but
their communication overhead and membership assumptions influence
scalability. They are generally suited to environments where
participants can be identified and governed.
Consensus selection should follow the trust and performance
requirements of the application. A public asset network may prioritize
open participation and resistance to censorship, while a regulated
consortium may prioritize known validators, transaction finality and
operational control. A supply chain network may need a balance between
participation by independent firms and the confidentiality of commercial
data. Consensus should be evaluated alongside governance, because a
technically decentralized protocol can still be controlled by a small
group of organizations or infrastructure providers.
Network governance defines who can join, who validates transactions,
how software changes are approved, how disputes are resolved and how the
system responds to compromised keys or defective smart contracts.
Governance may be encoded partly in software, but legal and
organizational agreements remain necessary. Participants should define
decision rights, voting procedures, liability, audit access, data
ownership and exit arrangements before deploying a shared ledger.
Forks occur when participants adopt incompatible versions of a ledger
or protocol. A temporary fork may arise naturally when blocks are
produced close together, while a persistent fork can reflect
disagreement about protocol rules or governance. Forks illustrate that
blockchain history is not governed by cryptography alone. Software
maintainers, validators, users and institutions make decisions about
which version to recognize. Organizations using blockchain for records
or regulated processes should establish how they will respond to network
changes and disputed histories.
Information management includes the creation, collection,
classification, storage, retrieval, sharing, preservation and disposal
of information. Blockchain can contribute to several of these
activities, but it does not replace the full information lifecycle. Its
distinctive function is to maintain a shared, verifiable history of
transactions or state changes among multiple participants. It is most
relevant where organizations need to coordinate updates and establish a
common sequence of events without relying entirely on one party's
database.
Data provenance concerns the origin, ownership, processing history
and chain of custody of information. Blockchain can record timestamps,
signatures, identifiers and references to data transformations. A
laboratory may commit a hash of a research dataset, a manufacturer may
record a production event, or a university may issue a credential whose
authenticity can later be checked. The ledger can make subsequent
alteration detectable, but it cannot establish that the original data
were collected correctly. Provenance is only as reliable as the
procedures that create and attest to each event.
Auditability is another potential benefit. In conventional systems,
administrators may modify records, and auditors must rely on access
logs, controls and organizational evidence to reconstruct events. A
replicated ledger can provide a consistent history of accepted
transactions, with cryptographic evidence of authorization and ordering.
This can reduce reconciliation effort among participants. However,
auditability depends on node independence, key security, completeness of
recorded events and the ability to interpret transaction data. If
administrators control all validators or can rewrite the application
layer, the practical assurance may be limited.
Shared data coordination is useful when several parties maintain
separate systems but need consistent status information. For example, a
shipment may pass through a manufacturer, freight company, customs
authority, warehouse and retailer. Each party may update a shared record
when custody changes. The ledger can provide a common event history and
reduce disputes about when a handover was recorded. Yet the system still
requires agreed event definitions, trusted identities, reliable data
capture and rules for correcting mistakes.
Blockchain can also support digital asset management. A token may
represent a claim, credential, access right or unit of value. Smart
contracts can enforce transfer rules and record ownership changes.
However, the legal meaning of a token depends on the rights and
obligations established outside the code. A digital token that
references a physical asset does not automatically confer legal
ownership of that asset. The legal and operational relationship between
on-chain state and off-chain rights must be explicit.
For records management, blockchain may provide evidence that a
document existed in a particular form at a particular time. A hash can
be stored on the ledger while the document remains in a controlled
repository. Later, the document can be hashed again and compared with
the committed value. This can support integrity checking, but it does
not by itself satisfy records retention, classification, access,
privacy, authenticity or archival preservation requirements. Records
professionals must determine how blockchain evidence fits within
established records management policies.
Data sharing is often described as a blockchain benefit, but
transparency must be distinguished from unrestricted visibility.
Participants may need to verify that an event occurred without seeing
the underlying commercial or personal data. Permissioned channels,
private transactions, encryption, zero-knowledge proofs and off-chain
access controls can help manage selective disclosure. These techniques
introduce complexity and may require additional trust assumptions. A
system should disclose only the information necessary for each
participant's role.
Blockchain may support trust between organizations, but trust is not
eliminated. It is redistributed among protocol developers, validators,
identity providers, oracle operators, key custodians, infrastructure
providers and governance bodies. The technology can reduce the need to
trust one party's unilateral database, but participants must still trust
the processes that admit data, manage identities and resolve disputes.
This distinction is essential when evaluating claims that blockchain
creates a trustless environment.
Supply chain management is one of the most frequently discussed
blockchain applications. Global supply chains involve multiple firms,
jurisdictions and information systems, and product histories may be
fragmented across records. A shared ledger can record production,
certification, custody transfer, inspection and delivery events. Kshetri
(2018) discussed how blockchain could improve supply chain management
through transparency, traceability and coordination. Saberi et al.
(2019) reviewed blockchain applications in sustainable supply chain
management and identified opportunities alongside implementation
barriers.
A blockchain supply chain application is most useful when the
participating firms agree on common data standards and event
definitions. Product identifiers, batch numbers, timestamps, location
information and inspection records must be consistently captured. IoT
sensors can provide temperature or location data, while authorized
organizations can sign custody events. Yet sensor tampering, inaccurate
data entry and collusion can still undermine the record. Blockchain can
preserve an event history, but it cannot independently verify the
physical condition of a product.
Healthcare information exchange presents a different set of
requirements. Medical records are sensitive, distributed among providers
and subject to strict access and retention obligations. Blockchain
proposals have explored patient-controlled permissions, audit trails,
consent management and integrity verification. Kuo et al. (2017)
reviewed blockchain applications in healthcare, while Agbo et al. (2019)
surveyed blockchain technology in healthcare. A practical design
generally keeps detailed medical records off-chain and uses the ledger
for permissions, references, integrity proofs or access events. This
avoids replicating sensitive clinical data across all nodes.
Digital identity systems can use blockchain to support verifiable
credentials and decentralized identifiers. A credential issuer signs an
assertion, such as an academic qualification or professional license,
and a holder presents it to a verifier. The verifier checks the issuer's
signature and relevant status information. The W3C Verifiable
Credentials Data Model provides a standard framework for expressing
credentials, while the Decentralized Identifiers specification defines a
mechanism for identifiers that can be resolved without relying on a
centralized registry. Blockchain may be used by some identity systems to
anchor identifiers or status information, but it is not required for
every decentralized identity design.
Academic credential verification is a focused application of digital
identity. Universities issue certificates, transcripts and
micro-credentials that employers and other institutions may need to
verify. A ledger can store a credential hash or a revocation registry,
allowing a verifier to check whether a credential was issued and whether
its status has changed. The actual credential can be held by the
graduate. This may reduce manual verification and help detect forged
documents, provided that issuing institutions maintain accurate records
and that revocation procedures are reliable.
Land and property records have also been proposed for blockchain.
Property transactions require authoritative records of ownership, liens,
boundaries and legal claims. A shared ledger could improve traceability
of updates and reduce some forms of record tampering. However, land
rights are embedded in legal institutions, historical claims, survey
systems and dispute resolution processes. If the initial registry
contains errors or excludes customary rights, recording it on a
blockchain can make the error more persistent without making it just.
Institutional reform and inclusive adjudication are prerequisites for
any technical system.
Financial services use blockchain for digital assets, settlement,
payments, trade finance and reconciliation. Distributed ledgers may
reduce the need for multiple institutions to maintain inconsistent
transaction records. Smart contracts can automate conditional transfers
and settlement processes. Yet financial applications require robust
governance, compliance, operational resilience, identity checks and
consumer protection. Public cryptocurrency networks and permissioned
financial ledgers have different risk profiles and should not be treated
as interchangeable.
Intellectual property and digital content management are additional
application areas. A creator may register a timestamped hash of a work
or record a license transaction. A blockchain can provide evidence that
a particular file or claim was registered at a given time, but it does
not prove authorship, originality or legal ownership. Copyright arises
under applicable law, and disputes may require evidence beyond a ledger
entry. Digital rights management also requires mechanisms for licensing,
payment, distribution and enforcement that operate outside the
blockchain itself.
Public administration applications include document verification,
procurement transparency, grant tracking, tax records and inter-agency
data coordination. A shared ledger may make it easier to audit
transactions among agencies and contractors. However, public-sector
deployments must satisfy legal authority, public accountability,
accessibility, privacy, data protection and long-term preservation
requirements. A public agency cannot transfer its legal responsibility
to a distributed network. Governance must specify which agency remains
accountable for the record and how errors can be corrected.
Scientific research and data management may benefit from
tamper-evident provenance. Researchers can record dataset hashes,
protocol versions, analysis events or authorship attestations. This can
support reproducibility and help establish that a dataset or analysis
file has not changed since a particular point. Blockchain does not
guarantee that the research is valid, that data were ethically collected
or that an analysis is reproducible. It can contribute to evidence
management when integrated with repositories, metadata standards,
persistent identifiers and established research integrity
procedures.
Education systems may use blockchain to record certificates, course
completion and professional development. Learners could hold credentials
and share them selectively with employers or other institutions. The
system may reduce verification delays and improve portability across
institutions. Yet education credentials require trusted issuers, clear
definitions of achievement, accessible recovery processes and mechanisms
for correcting inaccurate records. A permanent record should not prevent
correction of an error or recognition of a legitimate appeal.
7. Security, Privacy
and Technical Limitations
Blockchain security is often discussed in terms of cryptographic
integrity, but the security of an application depends on much more than
the ledger protocol. Private keys can be stolen, lost or misused. Smart
contracts can contain vulnerabilities. Interfaces and wallets can be
compromised. Consensus participants may collude or become concentrated.
Oracles can provide false information. A system can therefore have a
secure consensus protocol while the application built on top of it
remains vulnerable.
Key management is a particularly important operational challenge. A
digital signature proves that a transaction was signed by a key, but
users may lose access to keys or fail to protect them. Organizations
need secure generation, storage, backup, rotation and revocation
procedures. Hardware security modules and secure elements can protect
high-value keys, while multi-signature arrangements can reduce reliance
on one key holder. Recovery procedures must balance security with the
need to restore access when authorized users lose credentials.
Smart contract vulnerabilities can lead to unauthorized transfers,
locked assets or incorrect execution of business rules. Atzei et al.
(2017) analyzed vulnerabilities in Ethereum smart contracts and
described classes of programming errors that can be exploited. Auditing,
formal verification, testing, code review and controlled upgrade
mechanisms can reduce risk, but they cannot guarantee the absence of
defects. Organizations should define emergency procedures for pausing or
correcting a vulnerable contract and clarify who has authority to
act.
Privacy presents a structural challenge for public blockchains
because transaction data may be replicated across many nodes and remain
accessible for long periods. Pseudonymous addresses do not guarantee
anonymity. Transaction patterns can be linked to external information
and may reveal identities or commercial relationships. Storing personal
information directly on an immutable ledger can conflict with data
minimization, confidentiality and legal deletion obligations. A safer
design often stores sensitive information off-chain and places only a
cryptographic commitment or reference on the ledger.
Permissioned networks can restrict access to transaction details, but
they do not eliminate privacy risk. Consortium members may have
different legal obligations and competitive interests. Private channels,
encryption and selective disclosure can reduce exposure, but metadata
such as transaction timing, participant identity and frequency may still
reveal sensitive information. Privacy threat modelling should consider
what each participant can infer from the ledger and network traffic.
Scalability is a recurring limitation. Public blockchains may process
fewer transactions per second than centralized payment or database
systems, and transaction fees may vary with network demand. Replicating
and validating ledger data across many nodes can increase storage and
communication requirements. Layer-two systems, sharding, batching,
sidechains and alternative consensus mechanisms have been proposed to
improve performance. These approaches introduce additional complexity
and may change the trust or security assumptions of the system.
Energy consumption is especially relevant to proof-of-work networks.
The computational competition used to secure such networks can require
substantial electricity. The environmental impact depends on the energy
sources, hardware efficiency and network activity, but the resource
demand remains a major concern. Alternative consensus mechanisms,
including proof of stake and permissioned Byzantine fault-tolerant
protocols, can reduce energy requirements. Energy efficiency should be
considered at the architecture selection stage rather than after
deployment.
Data quality remains a fundamental limitation. Blockchain can make a
submitted record difficult to alter, but it cannot guarantee that the
record is accurate. This is commonly described as the oracle problem or
the problem of connecting digital records to physical reality. If a
supplier enters a false origin statement or a sensor reports manipulated
temperature data, the ledger may preserve the false information
reliably. Verification must therefore occur at data collection and
attestation points.
Interoperability between blockchains and legacy systems is another
challenge. Organizations often rely on enterprise resource planning
systems, databases, identity providers, document management platforms
and regulatory reporting tools. A blockchain deployment must integrate
with these systems without creating inconsistent copies or uncontrolled
data flows. Cross-chain interoperability adds further complexity because
different networks may use distinct consensus rules, finality models,
asset representations and security assumptions.
Legal and regulatory uncertainty can affect adoption. Questions
include whether a digital signature is legally recognized, how a smart
contract relates to a written agreement, which jurisdiction governs a
distributed network, who is responsible for a data breach and how
personal data rights apply to replicated records. These questions cannot
be resolved by protocol design alone. Organizations should obtain
jurisdiction-specific legal analysis and avoid assuming that technical
decentralization removes regulatory obligations.
Governance failure can undermine a blockchain even when its software
works as designed. Participants may disagree about membership, fees,
protocol upgrades, data correction or liability. A consortium may become
dominated by its largest members, reducing the perceived neutrality of
the network. Governance arrangements should specify voting rights,
dispute resolution, emergency powers, audit procedures and exit
mechanisms. A distributed ledger without legitimate governance may
simply move control from one database administrator to an opaque group
of validators.
8.
Adoption, Organizational Readiness and Economic Considerations
Blockchain adoption should begin with a clear problem statement.
Organizations sometimes select blockchain because it is fashionable or
because a proposal promises transparency, security and efficiency in
general terms. A more rigorous approach identifies the information
failure that needs to be addressed: duplicated records, costly
reconciliation, weak provenance, disputed event histories or dependence
on a single intermediary. The organization should then compare
blockchain with a shared database, a conventional API-based integration,
a trusted third-party service or a federated data architecture.
A useful initial test is whether multiple independent organizations
need to write to a shared record and whether they have a reason not to
rely on one party as the sole administrator. If one organization
controls the process and participants accept its authority, a
conventional database may be simpler, cheaper and easier to govern. If
participants need independent validation and a shared history, a
distributed ledger may offer value. Wüst and Gervais (2018) proposed a
decision framework to help determine when blockchain is appropriate,
emphasizing the importance of trust relationships and the need for
multiple writers.
The business case should include the full cost of implementation and
operation. Costs may include platform development, infrastructure,
transaction fees, integration, identity management, cybersecurity, legal
advice, governance administration, staff training and long-term
maintenance. Benefits may include reduced reconciliation, faster
verification, lower fraud exposure and improved auditability. These
benefits should be measured against a realistic baseline rather than
assumed from the presence of blockchain.
Network effects are important. A supply chain ledger has limited
value if only one supplier participates or if key events are not
recorded. The network becomes more useful as relevant organizations join
and contribute reliable data. However, onboarding many participants
increases governance and interoperability demands. Incentives may be
required to encourage participation, especially when smaller
organizations bear implementation costs while larger organizations
receive most of the benefit.
Organizational readiness includes data governance, process maturity,
cybersecurity capability and executive sponsorship. Blockchain does not
repair poor data standards or unclear business processes. Before
implementation, participants should agree on data definitions,
identifiers, event validation, access roles and dispute procedures. They
should also identify the legal entity responsible for each record and
the process for correcting inaccurate information.
Pilot projects should test a narrow use case with measurable
objectives. A pilot might track a product batch, verify a credential or
record a document hash. Evaluation should measure processing time,
reconciliation effort, data completeness, user adoption, transaction
cost, system availability and error resolution. The pilot should also
test failure scenarios, such as a compromised key, inaccurate input,
validator outage or participant withdrawal. A successful demonstration
is not sufficient evidence of production readiness.
The exit strategy should be considered before deployment.
Organizations need to know how data can be exported, how a participant
can leave the consortium, what happens if the platform provider fails
and how records will remain accessible over time. A long-lived public
ledger may continue to exist even if an application closes, but the
associated interfaces, keys or off-chain repositories may not.
Preservation planning must cover both ledger data and the systems
required to interpret them.
9.
Proposed Decision Framework and Reference Architecture
The review proposes a decision framework with seven assessment
dimensions. First, multi-party coordination: do several independent
organizations need to write to a shared record? Second, trust
distribution: is there a justified reason not to rely on one central
administrator? Third, audit and provenance: is a tamper-evident shared
history materially valuable? Fourth, privacy: can required
confidentiality be achieved through a suitable network and storage
design? Fifth, performance: can the chosen platform meet throughput,
latency and availability requirements? Sixth, governance: can
participants agree on membership, upgrades, disputes and liability?
Seventh, economics: do the benefits justify the total cost compared with
simpler alternatives.
A blockchain should be considered only when the answers indicate a
genuine distributed coordination problem. If a centralized authority is
trusted and efficient, a conventional database may be preferable. If
participants require shared verification but sensitive data must remain
private, a permissioned or hybrid design may be appropriate. If open
participation and public verifiability are central requirements, a
public blockchain may be considered, subject to performance, privacy and
cost constraints.
Figure 1. Decision pathway for blockchain suitability
Identify the information coordination problem
↓
Are there multiple independent writers?
↓
Is a single trusted administrator acceptable?
↓
If yes: assess conventional database or federated integration
If no: assess shared ledger requirements
↓
Define privacy, performance, legal and governance constraints
↓
Compare public, permissioned and hybrid architectures
↓
Pilot, measure benefits and risks, then decide whether to scale
A reference architecture for information management can contain five
layers. The application layer supports business processes such as
credential verification, product traceability or document provenance.
The smart-contract layer encodes permitted state transitions and
validation rules. The ledger layer maintains transaction history and
consensus. The integration layer connects the blockchain to enterprise
systems, identity services, oracles and off-chain repositories. The
governance and security layer defines membership, keys, access,
upgrades, audit and dispute resolution across the system.
In a hybrid architecture, large or sensitive information remains in
an off-chain repository under established access controls. The
blockchain stores a cryptographic hash, timestamp, identifier,
permission reference or event proof. When a user requests a document,
the repository authenticates the user and provides the content. The user
can independently calculate the hash and compare it with the ledger
commitment. This arrangement can provide integrity evidence without
exposing the entire document to all network participants.
Table 1 compares broad blockchain deployment models for information
management.
10. Discussion
The review shows that blockchain's strongest information management
contribution is the coordination of a shared history among parties that
do not fully trust one another's databases. Hash-linked records, digital
signatures and consensus can make changes traceable and allow
participants to verify the order and authorization of transactions.
These properties can reduce reconciliation and improve auditability in
carefully selected settings. They are not substitutes for accurate data
collection, identity proofing or institutional accountability.
A central finding is that blockchain should be evaluated against the
problem of trust distribution. If an organization already has authority
over a process and participants accept its database, a distributed
ledger may add cost without meaningful benefit. If independent
organizations need to write to shared records and no neutral
administrator is available, a consortium or public ledger may be useful.
The distinction helps separate substantive applications from
technology-led projects that use blockchain without a clear operational
need.
A second finding concerns the relationship between immutability and
information governance. Tamper-evident records can strengthen evidence,
but information systems also need correction, retention, privacy and
lawful disposal. A permanent ledger may preserve a record that should
later be corrected or restricted. Hybrid storage, off-chain personal
data and carefully designed revocation or supersession processes can
reduce conflict, but they do not remove the need for legal and
records-management analysis.
A third finding is that the quality of a blockchain application
depends on the quality of its surrounding institutions. Smart contracts
cannot resolve disputes over the meaning of a delivery event, the legal
status of a credential or the ownership of a physical asset unless the
parties have already agreed on those matters. Oracles, identity
providers and data-entry procedures remain trust points. Governance must
therefore be designed as carefully as the protocol.
A fourth finding is that technical decentralization does not
guarantee equitable participation. Validator concentration, control over
software upgrades, infrastructure dependence and unequal implementation
costs can create new power imbalances. Smaller suppliers or public
institutions may be required to join a network whose rules are set by
larger participants. Governance should make decision rights, costs and
benefits visible and should provide a process for challenging unfair
arrangements.
Finally, blockchain adoption should be evidence-based. Pilot projects
should compare the distributed ledger with a credible non-blockchain
baseline. Evaluation should include not only transaction speed but also
data quality, user participation, reconciliation effort, governance
cost, privacy risk and long-term maintainability. The appropriate
outcome of an evaluation may be to reject blockchain. A technology
selection process is successful when it chooses the most suitable
architecture, not when it guarantees adoption.
11. Research Gaps and
Future Directions
One priority is stronger empirical evaluation of blockchain
deployments. Many publications describe potential benefits or prototype
architectures, but fewer provide long-term evidence about operational
performance, governance cost, user adoption and measurable improvements
over conventional systems. Future studies should use comparative
designs, document baseline processes and report both positive and
negative outcomes. Research should distinguish production systems from
laboratory prototypes and proof-of-concept demonstrations.
A second priority is interoperability across platforms and
institutions. Real information ecosystems rarely operate on one
blockchain. Research is needed on cross-ledger verification, common
identity frameworks, standardized event schemas and secure exchange with
legacy databases. Interoperability mechanisms should be evaluated for
their security assumptions and failure modes rather than treated as
neutral connectors.
A third priority concerns privacy-preserving verification.
Zero-knowledge proofs, selective disclosure, confidential transactions
and privacy-enhancing cryptography may allow participants to verify
claims without revealing underlying information. These techniques can be
computationally demanding and difficult to integrate with existing
business processes. Research should assess practical performance,
auditability, usability and regulatory compatibility.
A fourth priority is governance for consortium networks. More
empirical work is needed on membership rules, voting structures,
software upgrades, liability allocation, dispute resolution and
participant exit. Researchers should examine how power is distributed in
practice and whether smaller participants can influence network rules.
Governance frameworks should be evaluated across different sectors and
legal environments.
A fifth priority is the integration of blockchain with IoT and
trustworthy data capture. Sensor-based records can improve traceability,
but physical devices can be compromised, miscalibrated or placed
incorrectly. Future work should combine device identity, secure
hardware, sensor attestation, trusted execution and independent
inspection. Research should also examine how disputes are handled when
sensor readings conflict with human evidence.
A sixth priority concerns sustainable consensus and infrastructure.
Proof-of-work energy use has motivated alternative consensus models, but
energy comparisons should consider security, decentralization, hardware,
network scale and operational context. Research should measure the full
lifecycle impacts of blockchain infrastructure and compare distributed
ledger designs with conventional database systems that provide similar
functionality.
A seventh priority is legal interoperability. Cross-border
applications may involve different rules for digital signatures, data
protection, consumer rights, financial regulation, records retention and
jurisdiction. Technical standards should be accompanied by legal and
institutional analysis. Research should investigate how distributed
records can support evidence and accountability without creating
uncertainty about the responsible authority.
Finally, research should examine blockchain in low-resource contexts.
Applications in land administration, agricultural supply chains,
educational credentials and public records may be relevant where records
are fragmented or verification is expensive. Yet unreliable
connectivity, limited technical support, uneven digital identity
coverage and unequal access can undermine adoption. Future work should
evaluate whether blockchain improves inclusion and institutional
performance in practice, rather than assuming that decentralization
automatically benefits underserved communities.
12. Conclusion
Blockchain technology offers a distinctive approach to information
management when multiple independent parties need to maintain and verify
a shared history of transactions or events. Cryptographic hashes,
digital signatures, replicated ledgers and consensus mechanisms can make
records tamper-evident and reduce dependence on one party's database.
Smart contracts can automate agreed state changes, while hybrid
architectures can combine on-chain integrity proofs with off-chain
repositories for large or sensitive information.
The review has shown that blockchain is not a universal database
replacement and does not automatically guarantee truth, privacy,
identity or trust. Its practical value depends on accurate data capture,
secure key management, appropriate consensus, reliable oracles,
interoperable systems and legitimate governance. Applications in supply
chains, healthcare, digital identity, education, public administration
and research data management are promising where the coordination
problem is real and the participating institutions can agree on shared
rules.
The proposed decision framework encourages organizations to assess
multi-party writing, trust distribution, audit needs, privacy,
performance, governance and total cost before selecting blockchain. It
also emphasizes the need to compare distributed ledgers with
conventional databases and federated architectures. In many cases, a
simpler system will provide better performance and easier
accountability. Where blockchain is justified, a hybrid design that
keeps sensitive information off-chain and records verifiable commitments
on-chain may offer a practical balance.
Ultimately, blockchain should be treated as an institutional and
technical arrangement rather than as a cryptographic product alone. The
quality of the resulting information system depends on the rules,
responsibilities and relationships among its participants. Its
contribution to information science will be strongest where distributed
verification solves a clearly defined problem and where technical
integrity is matched by trustworthy data practices, privacy protection
and accountable governance.
Table 1. Comparison of blockchain deployment
models
| Model |
Participation |
Strengths |
Main concerns |
| Public permissionless |
Open participation under protocol rules |
Open verification, broad participation, reduced dependence on a
single administrator |
Public data exposure, fees, throughput, consensus energy and
governance complexity |
| Private permissioned |
Controlled by one organization |
Clear administration, restricted access, predictable
performance |
Centralized control may reduce the need for a blockchain |
| Consortium or federated |
Approved group of organizations |
Shared control, known validators, suitable for inter-organizational
workflows |
Membership disputes, governance capture, coordination overhead |
| Hybrid |
Combination of on-chain proofs and off-chain systems |
Balances verification with confidentiality and scalable storage |
Integration complexity, off-chain dependencies and key
management |
References
Agbo, C. C., Mahmoud, Q. H., & Eklund, J. M. (2019). Blockchain
technology in healthcare: A systematic review. Healthcare, 7(2), Article
56. https://doi.org/10.3390/healthcare7020056
Atzei, N., Bartoletti, M., & Cimoli, T. (2017). A survey of
attacks on Ethereum smart contracts (SoK). Principles of Security and
Trust, 164–186. https://doi.org/10.1007/978-3-662-54455-6_8
Casino, F., Dasaklis, T. K., & Patsakis, C. (2019). A systematic
literature review of blockchain-based applications: Current status,
classification and open issues. Telematics and Informatics, 36, 55–81.
https://doi.org/10.1016/j.tele.2018.11.006
Castro, M., & Liskov, B. (1999). Practical Byzantine fault
tolerance. Proceedings of the Third Symposium on Operating Systems
Design and Implementation, 173–186.
https://www.usenix.org/legacy/events/osdi99/full_papers/castro/castro.pdf
Crosby, M., Pattanayak, P., Verma, S., & Kalyanaraman, V. (2016).
Blockchain technology: Beyond bitcoin. Applied Innovation Review, 2,
6–19.
https://j2-capital.com/wp-content/uploads/2017/11/AIR-2016-Blockchain.pdf
Gatteschi, V., Lamberti, F., Demartini, C., Pranteda, C., &
Santamaría, V. (2018). Blockchain and smart contracts for insurance: Is
the technology mature enough? Future Internet, 10(2), Article 20.
https://doi.org/10.3390/fi10020020
Glaser, F. (2017). Pervasive decentralisation of digital
infrastructures: A framework for blockchain enabled system and use case
analysis. Proceedings of the 50th Hawaii International Conference on
System Sciences, 1543–1552. https://doi.org/10.24251/HICSS.2017.186
Hou, H. (2017). The application of blockchain technology in
E-government in China. Proceedings of the 26th International Conference
on Computer Communication and Networks, 1–4.
https://doi.org/10.1109/ICCCN.2017.8038519
Kshetri, N. (2018). 1 Blockchain’s roles in meeting key supply chain
management objectives. International Journal of Information Management,
39, 80–89. https://doi.org/10.1016/j.ijinfomgt.2017.12.005
Kuo, T.-T., Kim, H.-E., & Ohno-Machado, L. (2017). Blockchain
distributed ledger technologies for biomedical and health care
applications. Journal of the American Medical Informatics Association,
24(6), 1211–1220. https://doi.org/10.1093/jamia/ocx068
Li, X., Jiang, P., Chen, T., Luo, X., & Wen, Q. (2020). A survey
on the security of blockchain systems. Future Generation Computer
Systems, 107, 841–853. https://doi.org/10.1016/j.future.2017.08.020
Lu, Y. (2019). The blockchain: State-of-the-art and research
challenges. Journal of Industrial Information Integration, 15, 80–90.
https://doi.org/10.1016/j.jii.2019.04.002
Nakamoto, S. (2008). Bitcoin: A peer-to-peer electronic cash system.
https://bitcoin.org/bitcoin.pdf
Ølnes, S., Ubacht, J., & Janssen, M. (2017). Blockchain in
government: Benefits and implications of distributed ledger technology
for information sharing. Government Information Quarterly, 34(3),
355–364. https://doi.org/10.1016/j.giq.2017.09.007
Queiroz, M. M., & Wamba, S. F. (2019). Blockchain adoption
challenges in supply chain: An empirical investigation of the main
drivers in India and the USA. International Journal of Information
Management, 46, 70–82.
https://doi.org/10.1016/j.ijinfomgt.2018.11.021
Saberi, S., Kouhizadeh, M., Sarkis, J., & Shen, L. (2019).
Blockchain technology and its relationships to sustainable supply chain
management. International Journal of Production Research, 57(7),
2117–2135. https://doi.org/10.1080/00207543.2018.1533261
Swan, M. (2015). Blockchain: Blueprint for a new economy. O’Reilly
Media.
https://www.oreilly.com/library/view/blockchain/9781491920480/
Szabo, N. (1997). Formalizing and securing relationships on public
networks. First Monday, 2(9). https://doi.org/10.5210/fm.v2i9.548
Treiblmaier, H. (2018). The impact of the blockchain on the supply
chain: A theory-based research framework and a call for action. Supply
Chain Management: An International Journal, 23(6), 545–559.
https://doi.org/10.1108/SCM-01-2018-0029
Wang, Q., Li, R., Wang, Q., & Chen, S. (2021). Non-fungible token
(NFT): Overview, evaluation, opportunities and challenges. arXiv.
https://doi.org/10.48550/arXiv.2105.07447
Wüst, K., & Gervais, A. (2018). Do you need a blockchain? 2018
Crypto Valley Conference on Blockchain Technology, 45–54.
https://doi.org/10.1109/CVCBT.2018.00011
Yli-Huumo, J., Ko, D., Choi, S., Park, S., & Smolander, K.
(2016). Where is current research on blockchain technology? A systematic
review. PLOS ONE, 11(10), Article e0163477.
https://doi.org/10.1371/journal.pone.0163477
Zheng, Z., Xie, S., Dai, H.-N., Chen, X., & Wang, H. (2017). An
overview of blockchain technology: Architecture, consensus, and future
trends. 2017 IEEE International Congress on Big Data, 557–564.
https://doi.org/10.1109/BigDataCongress.2017.85
Zheng, Z., Xie, S., Dai, H.-N., Chen, W., Chen, X., Weng, J., &
Imran, M. (2020). An overview on smart contracts: Challenges, advances
and platforms. Future Generation Computer Systems, 105, 475–491.
https://doi.org/10.1016/j.future.2019.12.019
World Wide Web Consortium. (2022). Verifiable credentials data model
v1.1. https://www.w3.org/TR/vc-data-model/
Narayanan, A., Bonneau, J., Felten, E., Miller, A., & Goldfeder,
S. (2016). Bitcoin and cryptocurrency technologies: A comprehensive
introduction. Princeton University Press.