<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Comprehensive Reference Model for Blockchain-based Distributed Ledger Technology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andreas Ellervee</string-name>
          <email>andrease@ut.ee</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Raimundas Matulevicius</string-name>
          <email>raimundas.matulevicius@ut.ee</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicolas Mayer</string-name>
          <email>Nicolas.Mayer@list.lu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Computer Science, University of Tartu</institution>
          ,
          <country country="EE">Estonia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Luxembourg Institute of Science and Technology</institution>
          ,
          <addr-line>5 Avenue des Hauts-Fourneaux, L-4362 Esch-sur-Alzette</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Blockchain is a distributed, transactional database that is shared across all the nodes participating in the network. This is the main technical innovation of Bitcoin and it acts as a public ledger for the transactions. However, this technology lacks standardisation and uniform understanding. This is due to a few studies, that would provide a comprehensive model of the blockchain and the distributed ledger technology. In this paper we compare four blockchain technology platforms and focus on their business level properties including actors and roles, services, and processes and data model. Our comparison results in a reference model, which could potentially guide the business analysts, system analysts and software developers when developing new blockchain platforms or their supported implementations. Accuracy of the proposed reference model is validated by considering it against selected blockchain technologies.</p>
      </abstract>
      <kwd-group>
        <kwd>Blockchain technology</kwd>
        <kwd>Reference model</kwd>
        <kwd>Distributed ledger</kwd>
        <kwd>Bitcoin</kwd>
        <kwd>Etherum</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The rst implementation of the blockchain technology, i.e. Bitcoin, was
introduced in 2009 [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Since its release, the popularity of bitcoins and
cryptocurrencies has only kept growing, because customers have started to value the
convenience and security of digital currencies, enabled by the blockchain technology.
In the traditional banking systems, the ledger is a centralised party (e.g., the
bank), which stores all the transactions. Blockchain, which serves as the
decentralised public ledger, can also be applied to other elds, such as healthcare,
insurance, data veri cation and others.
      </p>
      <p>
        Di erent businesses have developed various implementations using the
blockchains. However, only limited analysis [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] exists on the conceptual explanation
and understanding of the blockchain technology. In this paper we consider how
to unify this understanding and propose a comprehensive reference model to
characterise the blockchain technology. Our proposed model is developed and
its accuracy is validated by considering actors, services, processes, and data
of the existing blockchain platforms. Being presented in ArchiMate, BPMN and
UML modelling languages, the proposed reference model could potentially guide
business analysts, system analysts and software developers when engineering
applications using blockchain technology, developing new blockchain technology
platforms, analysing and comparing existing blockchain solutions.
      </p>
      <p>In Section 2 we give an overview of the state of the art of the blockchain
technology. Based on it, in Section 3 we present the reference model for the
blockchain technology. Section 4 describes how the accuracy of our proposal is
validated. Finally, Section 5 concludes the study and presents some future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>State of the Art</title>
      <p>In this section, rst we will de ne scope and discuss study background. Next we
will survey the blockchain technologies following the scoped properties.
2.1</p>
      <sec id="sec-2-1">
        <title>Scope and Background</title>
        <p>
          Blockchain acts as a distributed public ledger. It is a digital record of transactions
and ownership, that is replicated among all of the participants of a peer-to-peer
network. A consensus algorithm ensures that each node owns the same copy
of the ledger as the other nodes. Technically, it is a back-linked ordered list of
blocks, where each block contains transactions [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Each time a transaction is
made, it is broadcasted to the network. If it is valid, it gets added to a block.
When new block is published to the network, all participants (nodes) will run
algorithm to validate the block. Majority of the nodes have to agree that the
new block is valid and if so, it will be added to the blockchain. Once a block
of data is recorded on the blockchain ledger, data becomes more secure as the
blockchain grows [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
        </p>
        <p>
          There are two main types of blockchains: public and private. Bitcoin has a
public ledger i.e., a public blockchain, where anyone is allowed to contribute [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
There is no need for a third authority to grant permissions. Private blockchain is
a network where all the participants are known and trusted [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] and the consensus
process is managed by a pre-selected set of participants [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. In our study we
consider both public and private blockchains along the following properties:
{ Platforms - we are considering implementations of the blockchain
technology that introduce di erent approaches to privacy and smart contracts.
{ Actors - we want to know who the actors are and what roles they play in
the given blockchain technology.
{ Services - what services are provided by the blockchain platform? Who
interacts with the services (business level)?
{ Processes - what are the underlying processes to services? How do network,
transaction and mining/consensus processes work?
{ Data models - what are the entities that hold information? What are the
relationships between them?
        </p>
        <p>
          Blockchain technology platforms can be separated into four groups [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] as
illustrated in Table 1. For our study we have selected one blockchain platform
of each group. Some others could have been chosen, but we decided to select the
most widespread, based on our current knowledge. They can be characterised as
follows:
{ Permissionless - Fully public blockchains, where anyone can read and write.
{ Permissioned blockchain technology allows to de ne di erent
permissions on di erent users on the network. There can be di erent permissions
for reading data, creating transactions, validating blocks, creating new ones
and others.
{ Blockchains with Smart Contracts enable \smart contract" like
capabilities and allow building business logic and business process mechanism
into the chain.
{ Blockchains with transactions only are built for transaction capabilities.
        </p>
        <p>They support transferring value from one account to another.
Blockchain technology relies on a decentralised network of individual nodes, but
nodes have di erent purposes and di erent roles. Table 2 shows an overview of
actors who are present in the analysed blockchain platforms.</p>
        <p>
          For each platform, there exists a notion of a Client and a Miner or someone
who builds and agrees upon which transactions are included in a block [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]
[
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Client interacts with the blockchain (exchanges or adds value by creating and
broadcasting transactions). In Ethereum an Externally Owned Account (EOA) is
equivalent to the physical actor; and Contract Accounts (CA) can be understood
as a system user which acts upon a request by an EOA or by another CA.
Since CA is created by an EOA and interacted with by EOA and that they
are autonomous agents living inside the execution environments [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], we do not
consider CA as a separate actor.
        </p>
        <p>Miners deal with validating transactions and building new blocks. Since
Chain Core is a private blockchain, it has Blockchain operators, who are either
block generators or signers. Fundamentally, a Blockchain operator is a miner,
because miner's tasks in a blockchain environment are to create new blocks, sign
them, validate them and submit them to the blockchain.</p>
        <p>In conclusion, blockchain technology has two primary actors at the business
level:
{ Human actor who interacts with the blockchain by creating transactions.</p>
        <p>This actor can be called a \User".
{ Human or system actor responsible for veri cation and validation of
transactions, building new blocks, signing new blocks and publishing new blocks
to the blockchain. This actor supports trust between the parties involved. In
case of public blockchains \proof of work" is provided by the mining software
(system), but, for example in Chain Core there exist Blockchain operators
(human) who decide on the consensus. This actor can be labelled as \Block
generator".
2.3</p>
      </sec>
      <sec id="sec-2-2">
        <title>Comparison of Services</title>
        <p>In this section we will compare services used by actors de ned in the previous
section. The services are summarized in Table 3.</p>
        <p>Firstly, every platform provides a service to create and broadcast transactions
to the network. This is an essential service because transactions dictate the state
of the blockchain and add new data to the blockchain.</p>
        <p>
          MultiChain and Chain Core have the notion of assets, which is a type of
value, that is issued on the blockchain [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Bitcoin and Ethereum both have
their native currencies, bitcoin3 [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] and ether [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] respectively. MultiChain and
Chain Core allow creation of di erent assets.
        </p>
        <p>
          Bitcoin and MultiChain focus on transactions and exchanging value. Ethereum
and Chain Core also rely on state and smart contracts. Ethereum provides a
service to create a new contract, that can be submitted to the network; and Chain
Core supports the use of smart contract while issuing assets, by de ning business
3 Bitcoin (with upper B) stands for protocol, the software and community, bitcoin
(with lower b) stands for a unit of currency
rules for issuing (issuance program [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]) new units of given assets and also rules
for spending the assets (control program [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]).
        </p>
        <p>
          Since MultiChain and Chain Core are both designed to support private
blockchains, they support services to manage permissions. MultiChain provides
services for granting and revoking permissions to and from speci c users [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Chain
Core allows Blockchain operator to manage connections via network tokens.
        </p>
        <p>
          All platforms except Chain Core are proof-of-work-based mining solutions.
Mining in Bitcoin and Ethereum is publically available for anyone, while in
MultiChain user needs to have permission to perform mining (or if everyone on
the blockchain are known users, mining can be turned o alltogether [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]). In
Chain Core, federated consensus [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] is applied by Block generators and signers.
Block generator will use services like gathering valid transactions, generate block
and publish a block. Block signers, who validate and sign the block, use block
validation services and block signing services.
        </p>
        <p>In conclusion, common services among the technologies are creating
transactions, validating blocks and mining / creating blocks. Additionally,
permissioned blockchains provide services to manage permissions. Overall, it depends
on the features o ered by a blockchain, e.g., with Bitcoin being the most generic
blockchain, the number of provided services is di erent compared to Chain or
MultiChain. Features like assets, smart contracts and permissions add additional
services to the commonly o ered ones.
2.4</p>
      </sec>
      <sec id="sec-2-3">
        <title>Comparison of Processes</title>
        <p>Every platform has a network discovery process, which consists of 4 main
steps - Peer discovery ( nding peers to connect to, either user already knows the
IPs or acquires them), Handshake (version check, establishing connection,
providing ownership of private key), Network discovery ( nding neighbouring peers
and letting the network know that a new node has connected) and
Synchronization (downloading the latest block data from the network).</p>
        <p>
          In Bitcoin and Ethereum, new node connects to a known peer, they verify
that both are running the same version of the software and have the same, latest
and longest chain of blocks. In case of di erences, new node will download the
previous blocks up to the latest one. MultiChain expands the Handshake process
[
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] introduced in Bitcoin, by verifying that the connecting node's public address
is on the permitted list and by receiving a proof of the ownership of the private
key. In Chain Core, the Block Generator will provide Block Generator's URL, a
network token and the blockchain ID to the connecting node.
        </p>
        <p>
          Creating the transaction in Bitcoin requires user to enter value and the
receivers address. The transaction is then signed by the user and broadcasted to
the network (to neighbouring nodes). The neighbouring nodes check the
transaction for validity. If valid, they will propagate it forward to other peers [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ].
MultiChain adds additional metadata to the transaction, specifying asset name
and transaction type (issuing or spending assets, granting permissions etc.).
Similarly the transaction is constructed, signed and broadcasted to the network.
In Chain Core, transactions issue new assets or spend existing assets. Issuing
new assets or spending assets have to comply with the rules de ned in the
issuance program or in the control program [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Ethereum also supports regular
value transactions. The input parameters for the transaction are similar to
Bitcoin and MultiChain (i.e. amount and the address of the receiver). Additionally
Ethereum supports creating contracts and calling contract functions, which is
an additional metadata added to a transaction.
        </p>
        <p>
          Another common process is the Mining process (Block generation
process). Mining is based on the proof-of-work. A miner will build a new block,
add collected unveri ed transactions and metadata, and calculate the
computationally exhaustive proof-of-work for the block. If he is the rst one to solve the
task and mine the block, he can submit the block to the network and receive
a reward for that work. In Ethereum, the mining process also requires a state
transition process, since it keeps a state of the blockchain. In the state transition
process, transactions are validated and in case of contracts, code execution is also
performed. When all the state transition functions are valid, miner in Ethereum
will provide the proof-of-work for the block. In MultiChain, proof-of-work [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] is
optional and mining is permissioned. MultiChain introduces mining diversity to
vary the miners creating the blocks.
        </p>
        <p>
          Chain Core introduces a Chain consensus process [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. When a new
transaction is submitted, it will be transferred to the Block generator who will add
it to the new block. After certain periods, Block generator will construct the
block and send it to block signers, who will validate the block, sign it and send
it back to the Block generator. The Block generator can only submit the block
if the required block signers have signed the block, according to the consensus
program [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>
          Bitcoin and Ethereum introduce the block validation process which is
performed by every node once the miner broadcasts a new block. Since in the
public blockchains the miners are anonymous, there has to be a guarantee that
the miner has indeed produced a valid block. In Bitcoin, this is called a
`consensus' if all the nodes validate the new blocks against the same rules. In Ethereum,
the validation is similar, but additionally it includes the state transition process,
which each node has to perform before accepting the block [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>The four platforms provide similar general processes: Network discovery,
Transaction creation, Block generation and submission (Mining and Chain
consensus process) and Block validation. Conceptually, the processes may be similar,
but the inner work ow di ers from one technology to another.
2.5</p>
      </sec>
      <sec id="sec-2-4">
        <title>Comparison of Data models</title>
        <p>
          All four blockchain technologies introduce a Block, a Block header and
Transactions. Bitcoin, MultiChain and Chain Core also include Transaction Inputs and
Transaction Outputs (UTXO). Ethereum relies on the state replication, where
each new block's state is the outcome of the transactions that were included in
the block. Ethereum has chosen not to use the Input-Output transaction method,
because it does not support multi-stage contracts or scripts that could keep an
internal state [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>Ethereum has the notion of Accounts, which are either user accounts or
virtual contract accounts, that hold the balance, contract code and internal
storage. In Ethereum case, all this data is stored on the blockchain.</p>
        <p>With the addition of Assets, Chain Core keeps an Asset entity containing only
the asset ID. The assets are tied with certain programs (i.e. Issuance program,
for issuing new assets, or Control program, for spending assets). The Consensus
program is used by Block generator to verify that a block is ready to be submitted
to the network.</p>
        <p>
          To conclude, the main set of entities are the Block, Block Header and
Transactions. The Input-Output transactions are de facto Bitcoin solution to prevent
double-spending, but there are several arguments about the use of unspent
transaction outputs and their scalability [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], so in case of Ethereum, to enable the
multi-stage smart contracts, UTXO's are not used.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>A Reference Model for Blockchain Technology</title>
      <p>
        4 http://www.opengroup.org/subjectareas/enterprise/archimate-overview
{ Transaction creation - Transactions allow Users to add information to the
blockchain. Transactions can be used to create assets, spend assets, create
smart contracts, call functions on smart contracts, manage permissions etc.
{ Transaction submission - Transaction submission support signing and
broadcasting the transaction to the network.
{ Block validation - Block validation is a general service used by the nodes
to validate the newest blocks that have been added to the blockchain.
{ Block generation - Block generation is broken down into smaller services
that are used di erently depending on the type of consensus. A miner in
a public blockchain would use the block generation services, but in Chain
Core, one party creates the block and other parties sign the block [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
{ Blockchain access - Blockchain access is speci c to private and
permissioned blockchains, where administrative nodes grant access to known
parties. Can also be used to create network tokens for nodes.
      </p>
      <sec id="sec-3-1">
        <title>Processes</title>
        <p>The reference model (Figure 1) includes four processes: Network discovery
process, Transaction process, Consensus process, and Block generation process. We
expand these processes using the BPMN modelling language.5</p>
        <p>Network discovery process (Figure 2) consists of four subprocesses - Peer
Discovery, Handshake, Discovering additional peers and Synchronization.
Process begins by acquiring an IP of the known peer or blockchain (IP is known from
the last session or is acquired from an outside source). Once connected, private
blockchains will perform a check if the user is allowed to connect via its public
IP or a network token. If permitted, a handshake process is carried out to verify
versions and check that both nodes have the same blockchain with the latest
blocks. Next, the connected node's IP will be propagated to the network. Once
the network is discovered the connecting node will synchronise its blockchain if
any di erences in terms of the latest block is observed.</p>
        <p>Transaction process (Figure 3) starts creation of a new transaction.
Relevant metadata are added depending on the transaction type (e.g., standard
transfer of funds, creating assets, deploying smart contract, etc.). In the case
of private blockchains, there will be a permission check: (i ) whether the speci c
user is permitted to create the transaction, (ii ) whether the receiver is permitted
to receive funds, (iii ) whether the network permits transfer of funds or creation
of speci c type of transactions, etc. If the transaction is permitted (or in case of
public blockchains, the creator signs the transaction), it will be broadcasted to
the network, i.e., to the neighbouring nodes.</p>
        <p>Consensus process (Figure 4) is performed by each node when a new
block has been broadcasted. Each blockchain de nes its own \Consensus rules",
according to the type of the validated blocks and transactions. If validated, the
nodes will append the new block to the blockchain; otherwise it will be rejected.</p>
        <p>
          During the Block generation process (Figure 5), rst, a new block is
created; next, the previous block's metadata is added. In case of the
permissioned blockchains, permission changes have to be applied in order to avoid
5 http://www.bpmn.org/
unwanted actions performed by users, who do not have permission. Next, all
transactions will be validated against the consensus rules on the blockchain. In
public blockchains, the block generators (i.e., miners) will provide a proof of the
work (i.e., proof-of-work or proof-of-stake etc.) and will be rewarded for their
work. In private blockchains, the consensus process might be part of the block
generation process. Once the block is constructed, it is submitted to the network
and propagated to all the nodes.
The data model is presented in Figure 6. The model shows that keeping the
state of the blockchain is preferred here in comparison to the Input-Output
type transaction logic. Since UTXOs are stateless [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], they are preferred for
issuing assets or performing standard transfer of value (assets or cryptocurrency).
However, since smart contracts are powerful, keeping the state of the blockchain
supports complex logic better than UTXOs.
        </p>
        <p>State contains accounts, which have balance and address. In case of contracts
(marked with grey box in Figure 6), they also have to keep the executable code
and storage speci c to the given account. Accounts are linked to transactions and
ko
r
w
t
e
N
Create new</p>
        <p>block
Add previous
block metadata</p>
        <p>Unverified
transactions</p>
        <p>Col ect
unverified
transactions</p>
        <p>Apply
permission
changes
each transaction changes the state of the blockchain (balance changes, contracts
function calls etc.). Block and Block Header are standard and essential to every
blockchain platform. Block contains transactions; the block's metadata is kept
in the Block Header.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Validation</title>
      <p>To validate the reference model we investigate its accuracy by comparing it to
the existing blockchain solutions. Firstly, we compare the reference model to
the four implementations that were used to build it. We de ne a Delta (i.e.</p>
      <p>) metric, which represents the di erenc between the reference model and the
models of the considered blockchain technologies. Secondly, we select four new
blockchain platforms and calculate the Delta value for them. Our goal is to show
that using the reference model we are able to capture business perspective of all
selected blockchain technologies.</p>
      <p>Delta de nition. Finding the delta for the four initial Blockchain
technologies (Figure 7), we will compare actors, services, processes and data models
separately. The overall will be the sum of all deltas ( = actors + services +
processes + datamodels). = 0 means they have the same entities. &gt; 0 means
the uni ed model has more entities. &lt; 0 means that the reference model is
missing some entities, that the comparable model has. Finding the delta for
the four new Blockchain technologies (Figure 7), we will also compare actors,
services, processes and data models separately, but we will only take into
evaluation if the given entity exists or is present in the newly presented technology.</p>
      <p>= 0 means they have the same entities. &gt; 0 means the reference model has
more entities.</p>
      <p>Results for the values are presented in Table 5. The goal of accuracy
validation was to get a value as close to 0 as possible for initial four technologies
as well as for four new technologies that were not used as a basis of building the
model. From the results we can see that the initial four technologies are covered
almost accurately by the reference model, with subtle di erences in Data models
(e.g., four di erences - Bitcoin and MultiChain do not support Accounts and
State). We consider this result acceptable, because of the di erences that smart
contracts introduce to the data model (see Figure 6).</p>
      <p>As for the four technologies that were not part of the initial building of
the model, we found di erences in the data models (e.g., ve entity di erences
CryptoNote and NXT do not keep the blockchain state, Hyperledger Fabric does
not have Block Header, Tendermint misses account representation), Networking
process (one entity di erence - Block synchronization) and Consensus process
(e.g., one entity di erences - Transactions in Hyperledger Fabric are veri ed and
endorsed before reaching the miner). This result is also considered acceptable,
due to the fact that the new blockchain technologies are di erent from the initial
four technologies, but still perform well under the de ned blockchain properties.</p>
      <p>Threats to validity. The accuracy validation was done by the rst author
of this paper with the technologies in hand. Thus, another validation approach
might conceive di erent results, either by de ning the Delta di erently or by
selecting di erent implementations of the technology. We did not constructed
conceptual models for platforms which were not used to create the reference model.
These were assessed following their documentations. Potentially we could miss
some concepts from the comparison. However this is less likely as the majority
of the entities were in fact captured as shown in Table 5.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Concluding remarks</title>
      <p>This paper gives an overview of the disruptive blockchain platforms: Bitcoin,
MultiChain, Ethereum and Chain Core. Each of them presented a di erent
approach to networking, transactions, mining, validation, security and permissions.
The comparison resulted in the reference model, that aims to represent the
domain of the blockchain technology. The model contributes to the explicit
understanding of the technology and its work processes. The paper also presents a
brief overview of validation performed on model with the corresponding results.
The results re ect that the reference model performed well to cover the known
blockchain technologies, such as Cryptonote, NXT, Hyperledger and
Tendermint. The results potentially indicate how to develop this fast growing
technology further and in a more secure way by expanding its disruptive nature to other
application domains.</p>
      <p>
        When it comes to standardisation of the blockchain technology and its
presentation it in an uni ed way, there exist some study that thrive towards this
goal. In [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] the technology is de ned using three layers - Essential,
Infological and Datalogical layer. The information is presented in the UML model and
explains the general overview. However it lacks details to de ne relationships
between actors and processes. In our work we have used di erent notations to
present the reference model. We hope that it would guide the business analysts
and help them to communicate with the developers. Additionally, we explicitly
present the link between the users and processes and expand these processes
by showing targeted private and public activities. Finally, the accuracy of our
proposal is validated with respect to other blockchain platforms, which were not
used to create the reference model.
      </p>
      <p>
        This type of research on the blockchain technology is a rst and hopefully a
basis to future research. This being said, we plan to further validate the model
via security assessment [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], by aligning the reference model to ISSRM6. This
alignment (using ArchiMate and BPMN) will help us observe what actors are
a ected, what services are they using and what processes implement those
services. Then, using BPMN representations it will possible get a details of the
a ected processes. This can be achieved thanks to the reference model.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Allaby</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>The Trust Trade-O : Permissioned vs Permissionless Blockchains</article-title>
          .
          <source>Fjord (Oct</source>
          <year>2016</year>
          ), https://www.fjordnet.com/conversations/ the-trust
          <article-title>-trade-o -permissioned-vs-permissionless-blockchains/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Antonopoulos</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          :
          <string-name>
            <given-names>Mastering</given-names>
            <surname>Bitcoin: Unlocking Digital Crypto-Currencies. O'Reilly Media</surname>
          </string-name>
          , Inc., 1st edn. (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Buterin</surname>
          </string-name>
          , V.:
          <article-title>On Public and Private Blockchains (</article-title>
          <year>2015</year>
          ), https://blog.ethereum. org/
          <year>2015</year>
          /08/07/on-public-and
          <string-name>
            <surname>-</surname>
          </string-name>
          private-blockchains/
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Buterin</surname>
          </string-name>
          , V.:
          <article-title>Thoughts on UTXOs by Vitalik Buterin</article-title>
          , CoFounder of Ethereum (
          <year>2016</year>
          ), https://medium.com/@ConsenSys/ thoughts-on
          <article-title>-utxo-by-vitalik-buterin-2bb782c67e53#</article-title>
          .
          <year>s3c7dtmxp</year>
          , [Online; accessed 10-January-2017]
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Chain:
          <article-title>Chain Protocol Whitepaper</article-title>
          .
          <source>Tech. rep.</source>
          , https://chain.com/docs/protocol/ papers/whitepaper
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>David</given-names>
            <surname>Moskowitz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Tim</given-names>
            <surname>Swanson</surname>
          </string-name>
          , R.C.
          <article-title>: A Gentle Introduction to Blockchain Technology (</article-title>
          <year>2015</year>
          ), https://bitsonblocks.net/
          <year>2015</year>
          /09/09/ a
          <article-title>-gentle-introduction-to-blockchain-technology/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ellervee</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Comprehensive Reference Model for Blockchain-based Distributed Ledger Technology (</article-title>
          <year>2017</year>
          ), http://kodu.ut.ee/ andrease/ellervee blockchain reference model.html
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Ethereum</surname>
            :
            <given-names>A</given-names>
          </string-name>
          <string-name>
            <surname>Next-Generation Smart</surname>
          </string-name>
          Contract and Decentralized Application Platform (
          <year>2016</year>
          ), https://github.com/ethereum/wiki/wiki/White-Paper, [Online; accessed 6-October-2016]
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Greenspan</surname>
            ,
            <given-names>D.G.</given-names>
          </string-name>
          :
          <article-title>Bitcoin network | Wikipedia, The Free Encyclopedia (</article-title>
          <year>2015</year>
          ), http://www.multichain.com/download/MultiChain-White-Paper.pdf, [Online; accessed 12-December-2016]
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. de Krui , J.:
          <article-title>Understanding the Blockchain Using Enterprise Ontology (</article-title>
          <year>2017</year>
          ), https://www.list.lu/ leadmin/ les/Event/sites/tudor/ les/Training Center/OTHERS/VMBO2017 paper 5.pdf
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kuhlman</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>How I (currently) Explain The State of Blockchains To Executives and Researchers (</article-title>
          <year>2015</year>
          ), https://monax.io/
          <year>2015</year>
          /08/10/ how
          <article-title>-i-current-explain-blockchains/?redirect from eris=true</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Nakamoto</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Bitcoin: A Peer-to-Peer Electronic Cash System</article-title>
          .
          <source>Tech. rep.</source>
          , https: //bitcoin.org/bitcoin.pdf
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Norton</surname>
            ,
            <given-names>S.: CIO</given-names>
          </string-name>
          <string-name>
            <surname>Explainer: What Is Blockchain? The Wall Street Journal</surname>
          </string-name>
          (
          <year>2016</year>
          ), http://blogs.wsj.com/cio/2016/02/02/cio-explainer
          <article-title>-what-is-blockchain/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Pilkington</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <source>Blockchain Technology: Principles and Applications. Research Handbook on Digital Transformations</source>
          , edited by F.
          <article-title>Xavier Olleros and Majlinda Zhegu</article-title>
          . Edward
          <string-name>
            <surname>Elgar</surname>
          </string-name>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>