<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Estimating the Duration of Blockchain-Based Business Processes Using Simulation</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Stephan</forename><surname>Haarmann</surname></persName>
							<email>stephan.haarmann@hpi.de</email>
							<affiliation key="aff0">
								<orgName type="department">Hasso Plattner Institute</orgName>
								<orgName type="institution">University of Potsdam</orgName>
								<address>
									<settlement>Potsdam</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Estimating the Duration of Blockchain-Based Business Processes Using Simulation</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">C789B008166B782E8AA66F38051E0E0D</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T20:17+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Business Process Management</term>
					<term>Blockchain</term>
					<term>Simulation</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Information systems automate parts of business processes and support involved stakeholders. Recently, blockchains and other distributed ledgers are considered to extend the possibilities for automating inter-organizational processes: these technologies offer a new paradigm for such processes as they may automatically enforce contractual agreements without a trusted third party. Although existing research shows that inter-organizational processes can be enacted based on blockchains, fundamental question, such as What is the impact of blockchain on the process?, remain open. This work focuses on analyzing the duration of blockchain-based inter-organizational processes using simulation techniques.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>With business process management (BPM), enterprises can structure, document, and enact their processes <ref type="bibr" target="#b14">[15]</ref>. At the core of BPM, process models (e.g., modeled using the Business Process Model and Notation (BPMN) <ref type="bibr" target="#b9">[10]</ref>) can capture process elements, such as tasks and data, the elements' relations (e.g., causal and data dependencies), as well as the process' interactions.</p><p>Process engines use various technologies: databases store process relevant data, mobile devices enable ubiquitous access, IoT technologies establish cyberphysical connections, and more. Recently, the BPM community researches the application of blockchain, especially in inter-organizational processes <ref type="bibr" target="#b7">[8]</ref>. The blockchain technology can enforce the execution of programs by creating transparency and integrity, so collaborating parties can rely on the blockchain as a source of truth. Most research focuses on the blockchain-based execution and mediation of processes: in a setting in which mutual distrust prevents any participant from acting as a central coordinator, authority, or platform provider, blockchain technologies can replace a trusted third party <ref type="bibr" target="#b2">[3]</ref>.</p><p>However, for some inter-organizational business processes, blockchain-based solutions are inefficient and not viable. Some methods employ model-driven development to speed up the development cycle, but expertise and manual effort is required for blockchain-specific configurations. For enterprises it is difficult to decide whether a blockchain is applicable and whether it is efficient enough to be viable. Additionally, most of the current solutions are tailored to one specific blockchain implementation (e.g., Ethereum <ref type="bibr" target="#b15">[16]</ref> or Hyperledger Fabric <ref type="bibr" target="#b0">[1]</ref>), but each technology has different characteristics and the implications for the process vary. Process analysis techniques, such as process simulation, can provide insights to support decision makers.</p><p>In this paper, we sketch an approach for analyzing the duration of blockchainbased business processes using simulation. The analysis is based on a configurable model of the blockchain's behavior, which can be integrated in process models to simulate the blockchain's impact on the process execution. Combined with general information (e.g., the technology's security guarantees), the results help businesses to make an informed decision about whether to apply blockchain.</p><p>The remainder of this paper starts with an example and an overview of works on blockchain-based BPM (Section 2). In Section 3, we present our approach of estimating the duration of blockchain-based processes. Finally, we discuss our approach and list directions for future work (Section 4).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Blockchains for BPM</head><p>In BPM, blockchains are mostly applied to inter-organizational (collaborative) business processes <ref type="bibr" target="#b7">[8]</ref>. Initially, blockchain was proposed to power the cryptocurrency Bitcoin <ref type="bibr" target="#b8">[9]</ref>. It supports simple money transfer and advanced concepts such as escrows.</p><p>The so called 2 nd generation of blockchains supports smart contracts: programs that are executed by the nodes of the blockchain network. Just as the blockchain-stored ledger, smart contracts are tamper-proofed, transparent, and permanent. These properties guarantee that the program is executed when it is called (stopping the execution requires manipulating the ledger); thus, smart contracts can enforce contractual agreements. Since inter-organizational process models describe an agreement on responsibilities (by whom and in which order are actions performed?), smart contracts can enforce them.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Related Work</head><p>The BPM community focuses mostly on the blockchains with smart contract capabilities. The degree of blockchain integration can vary from simple monitoring tools to blockchain-based process engines: Weber et al. demonstrated blockchain-based monitoring and execution of inter-organizational business processes <ref type="bibr" target="#b13">[14]</ref>. The tool Caterpillar by Lopez-Pintado et al. extends this idea to an Ethereum-based process engine -the work takes classical process models <ref type="bibr" target="#b5">[6]</ref>. Similar works with different foci exist: Sturm et al. focus on the flexibility of processes <ref type="bibr" target="#b12">[13]</ref>, Madsen et al. on declarative processes <ref type="bibr" target="#b6">[7]</ref>, and Hull et al. on data centric processes <ref type="bibr" target="#b3">[4]</ref>.</p><p>Generating smart contracts from process models reduces the development time. However, blockchain-based process execution may have non-functional requirements, i.e., temporal constraints. The mentioned works help to estimate aspects such as the duration; however, this still involves manual configuration and a blockchain setup. The same holds for the work by Yasaweerasinghelage et al.: their approach uses process simulation to send transaction to a blockchain in order to estimate its latency <ref type="bibr" target="#b16">[17]</ref>. A choreography model depicting the process of purchasing artworks; tasks are annotated with the time between detecting the previous message and sending the next; control flow is annotated with the time between sending a message and the next initiator detecting it; times marked with * do not exist in a blockchain-based process. Figure <ref type="figure">1</ref> depicts an example inter-organization process as a BPMN choreography model: a buyer purchases an artwork from auctioneers. Since the purchase may bear a high risk, the buyer first opens an escrow. The auctioneers send the artwork to the buyer and an expert assesses it. The expert is a neutral party trusted by both the auctioneers and the buyer. Based on the expert's assessment the money in the escrow is released, and the money is sent to the auctioneers (if the artwork is real). In case of a fraud, the artwork is sent back, and the escrow is canceled (transferring all funds back to the buyer).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Motivating Example</head><p>Blockchain technologies can take on different roles in the art-dealing example. Blockchains with inherent cryptocurrencies often support escrows. Thus, blockchain technologies can replace the bank (a trusted intermediary). With smart contracts, the process can further be enhanced: the contract can track the correct progression of the process, for example that the escrow is created before the artwork is delivered. Furthermore, blockchain-based identities can restrict the execution of actions to specific roles. By storing a fingerprint of messages or proficiency data, the blockchain can support the process as a data storage.</p><p>In the following, we describe initial work on simulating blockchain-based processes that helps stakeholders to estimate the process execution time and which can be configured towards various blockchain implementations. For the choreography, we consider two types of durations: the time between a message being sent and being detected by the initiator of the next task (annotated on edges) <ref type="bibr" target="#b4">[5]</ref> and time between detecting a message and sending the next one (annotated on tasks). For the former, we lift the assumption that interactions in choreographies are timeless.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Analyzing Blockchain-Based Latency</head><p>A blockchain is a decentralized system for reaching consensus in a peer-to-peer network. Due to its nature, blockchains introduce additional latency: transactions are submitted, shared, verified and processed, and eventually incorporated in the consensus. Afterwards, participants are accountable for their transactions.</p><p>Inter-organizational business processes can employ blockchain in various ways. For the art-dealing example, we consider blockchain-based process execution: The bank is replaced by a smart contract and all interactions are logged by a smart contract, which enforces the right ordering of the actions. The triggering participant sends a transaction at the end of each interaction, i.e., the auctioneers send the transaction for the shipment after handing over the artwork.</p><p>The transactions trigger the progression of the on-chain process instance. The network managing the ledger processes a transaction in steps: a local transaction is shared with the network but remains pending, a pending transaction is mined (included in a block that extends the ledger), and the mined block with all its transactions is confirmed (succeeded by a certain number of blocks). The duration of each step depends mostly on the blockchain and the underlying network: in Bitcoin, a transaction needs a couple of seconds to spread, and a new block is appended approximately every 10 minutes; for Ethereum, transactions diffuse the network similarly fast; however, a block is added every 15 seconds. We assume that a transaction is included in the first block that is mined after the transaction became available to the network (the reality may be more complex and influenced by transaction fees, network load, and throughput).</p><p>In most cases, a participant waits for all preceding transactions to be confirmed. However, if the same participant triggers two subsequent interactions, the participant does not need confirmation of his or her own action. Additionally, if an interaction is physically, such as shipping the artwork, the transaction must be confirmed and the interaction must be completed.</p><p>Figure <ref type="figure" target="#fig_1">2</ref> partially shows a timed Petri net representation of the inter-organizational process. Each interaction task of the choreography model is translated into corresponding transitions: the firing of such a transition indicates the completion of the respective interaction. It progresses the state by producing an unnamed token for the control flow. Further, each interaction puts a token identifying the interaction on the Transaction Local place. The net includes the blockchainbased transaction processing: a transaction is sent, diffuses the network, is included in a block, and eventually the block is confirmed. The transition Mine Block consumes all tokens on Transaction Pending and produces respective tokens on Transaction Included. Each interaction depends on the previous one; thus, the respective transition can only fire if the previous transaction is in the place Transaction Confirmed. This requirement is represented by the labels on the respective arcs. In the example, the expert is performing two actions in a row, and does not need confirmation of the first transaction. The transitions with label Cancel Escrow represent the different options: the escrow can be canceled immediately after Return Artwork; thus, there is a transition for Cancel Escrow for each possible state of the Return Artwork transaction (local, pending, included and confirmed). Each transition is annotated with ranges for the duration of the respective choreography task/blockchain action <ref type="bibr" target="#b11">[12]</ref>. We derived the time by assuming 8h per day. A transition is annotated with the sum of the choreographies task duration and the communication (outgoing arch), for example Return Artwork is annotated with &lt;1.5-2.5d&gt; which is the sum of the duration 0.5d and the communication 1-2d. While the duration of a choreography task is domain and instance specific, the duration for a blockchain action depends mostly on the implementation. For this purpose, we introduce a blockchain configuration: 1. the diffusion-time -the time until a transaction is known by the network (e.g., around 15 sec for Bitcoin [2]<ref type="foot" target="#foot_0">1</ref> ); 2. the inter-blocktime -the time between the mining of two blocks (e.g., approximately 10 min for Bitcoin, about 15 sec for Ethereum<ref type="foot" target="#foot_1">2</ref> ) 3. the confirmation-count -the number of blocks that follow an included transaction until it is consider confirmed (e.g., Bitcoin recommends a confirmation-count of 6, Ethereum one of 12, and most private blockchains use 0). These parameters are set according to the used blockchain. The product of inter-blocktime and confirmation-count denotes the time between mining a transaction and confirming a transaction.</p><p>The Petri net semantics equipped with temporal information of the choreography and a blockchain configuration allow a simulation of the blockchain-based inter-organizational process. We use CPNTools<ref type="foot" target="#foot_2">3</ref> to model<ref type="foot" target="#foot_3">4</ref> all aspects of the Petri net and simulate the process quantitatively and manually step-through simulation Running 100 instances, we derived an average duration of about 8 days for the version not using blockchain and about 3 days for a blockchain-based version (0 min diffusion-time, 10 min inter-blocktime, 6 blocks confirmation-count; duration ranges where simulated via a binomial distribution). While the blockchain causes delays, it enables process changes that reduce the overall duration: in the example, the replacement of the bank improved the process performance. By simply adjusting the blockchain it is possible to estimate other blockchain implementations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Discussion and Future Work</head><p>In some cases, blockchain technologies may remove the need for trusted intermediaries in inter-organizational business processes. However, such solutions have drawbacks: the distributed nature limits the throughput and causes latency. We sketched a method to analyze the duration of blockchain-based processes.</p><p>The analysis relies on formal semantics, domain specific information, and a configuration for a certain blockchain implementation. The configuration comprises three parameters; thus, adapting to different blockchains is simple. Through simulation, the analysis estimates the duration of blockchain-based processes with little effort compared to prototypical and model-driven implementations. However, the impact of blockchain-based implementations on processes is not always significant: especially processes that are executed frequently and that are highly automated might be slowed down by blockchains. Processes that contain various manual and physical tasks may be delayed insignificantly by blockchains or even speed up as manual tasks are automated or third parties are replaced by smart contracts.</p><p>The presented work is in an early state. In future work, we will support BPMN choreography models by integrating our approach into a business process simulator, which takes a blockchain configuration as well as an enriched BPMN choreography model as an input. Additionally, different ways of blockchain-based process support exist: we want to investigate existing solutions (such as Caterpillar) to estimate different implementations and paradigms. Furthermore, the blockchain behavior can be modeled and configured on different granularity levels: currently we do not consider that blocks are limited in size, the processing of transactions might be prioritized based on transaction fees, and that block propagation depends on various factors <ref type="bibr" target="#b1">[2]</ref>.</p><p>Additionally, execution time of processes is only one aspect affected by the underlying technology. Public blockchains include a cryptocurrency: a transaction has costs depending on its priority and payload. This may or may not have a significant impact on the overall costs of a process. Related to both costs and duration is the throughput of blockchains: when a blockchain is used for multiple purposes or by many participants, transactions may remain pending longer.</p><p>Analyzing various aspect of blockchain-based processes requires detailed understanding of the technologies as well as the configuration points. In future work, we will explore such behavioral properties and derive a formal model of blockchains that can be configured towards specific implementations. Detailed models can provide insights in blockchain's behavior as well as its impact on business processes beyond latencies. Such models equipped with empirical data <ref type="bibr" target="#b10">[11]</ref> may lead to higher precision in simulating the processes.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>Fig.1. A choreography model depicting the process of purchasing artworks; tasks are annotated with the time between detecting the previous message and sending the next; control flow is annotated with the time between sending a message and the next initiator detecting it; times marked with * do not exist in a blockchain-based process.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. A timed Petri net showing the three interactions Request Assessment, Return Artwork, and Cancel Escrow including the blockchain's transaction processing</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="1,0.00,159.54,612.00,472.91" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Bitcoin diffusion-time: http://bitcoinstats.com/network/propagation/ (02/06/2019)</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">Ethereum inter-blocktime : https://etherscan.io/chart/blocktime (02/06/2019)</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">CPNTools homepage: https://cpntools.org (1/7/2019)</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">Models and results: https://owncloud.hpi.de/index.php/s/iGVqu7WkgMYXIpWEstimating the Duration of Blockchain-Based Business Processes</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Hyperledger fabric: a distributed operating system for permissioned blockchains</title>
		<author>
			<persName><forename type="first">E</forename><surname>Androulaki</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Barger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Bortnikov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Cachin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Christidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>De Caro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Enyeart</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Ferris</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Laventman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Manevich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Thirteenth EuroSys Conference</title>
				<meeting>the Thirteenth EuroSys Conference</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page">30</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Information propagation in the bitcoin network</title>
		<author>
			<persName><forename type="first">C</forename><surname>Decker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Wattenhofer</surname></persName>
		</author>
		<idno type="DOI">10.1109/P2P.2013.6688704</idno>
		<ptr target="https://doi.org/10.1109/P2P.2013.6688704" />
	</analytic>
	<monogr>
		<title level="m">13th IEEE International Conference on Peer-to-Peer Computing, IEEE P2P 2013</title>
				<meeting><address><addrLine>Trento, Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2013">September 9-11, 2013. 2013</date>
			<biblScope unit="page" from="1" to="10" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The limits of trust-free systems: A literature review on blockchain technology and trust in the sharing economy</title>
		<author>
			<persName><forename type="first">F</forename><surname>Hawlitschek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Notheisen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Teubner</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.elerap.2018.03.005</idno>
		<ptr target="https://doi.org/10.1016/j.elerap.2018.03.005" />
	</analytic>
	<monogr>
		<title level="j">Electronic Commerce Research and Applications</title>
		<imprint>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="page" from="50" to="63" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Towards a shared ledger business collaboration language based on data-aware processes</title>
		<author>
			<persName><forename type="first">R</forename><surname>Hull</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">S</forename><surname>Batra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Deutsch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">F T H</forename><surname>Iii</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vianu</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-319-46295-02</idno>
		<ptr target="https://doi.org/10.1007/978-3-319-46295-02" />
	</analytic>
	<monogr>
		<title level="m">Service-Oriented Computing -14th International Conference, ICSOC 2016</title>
		<title level="s">Proceedings.</title>
		<meeting><address><addrLine>Banff, AB, Canada</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2016">October 10-13, 2016. 2016</date>
			<biblScope unit="page" from="18" to="36" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Time, clocks, and the ordering of events in a distributed system</title>
		<author>
			<persName><forename type="first">L</forename><surname>Lamport</surname></persName>
		</author>
		<idno type="DOI">10.1145/359545</idno>
		<idno>.359563</idno>
		<ptr target="https://doi.org/10.1145/359545" />
	</analytic>
	<monogr>
		<title level="j">Commun. ACM</title>
		<imprint>
			<biblScope unit="volume">21</biblScope>
			<biblScope unit="issue">7</biblScope>
			<biblScope unit="page" from="558" to="565" />
			<date type="published" when="1978">1978</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Caterpillar: A blockchain-based business process management system</title>
		<author>
			<persName><forename type="first">O</forename><surname>López-Pintado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>García-Bañuelos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dumas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-1920/BPM2017paper199.pdf" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the BPM Demo Track and BPM with 15th International Conference on Business Process Management (BPM 2017)</title>
				<meeting>the BPM Demo Track and BPM with 15th International Conference on Business Process Management (BPM 2017)<address><addrLine>Barcelona, Spain</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017-09-13">September 13, 2017. 2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Collaboration among adversaries: Distributed workflow execution on a blockchain</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">F</forename><surname>Madsen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Gaub</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Høgnason</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">E</forename><surname>Kirkbro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Slaats</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Debois</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Symposium on Foundations and Applications of Blockchain</title>
				<imprint>
			<date type="published" when="2018">2018. 2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Blockchains for business process management -challenges and opportunities</title>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Vom Brocke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Cabanillas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Daniel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Debois</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">D</forename><surname>Ciccio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dumas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Dustdar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>García-Bañuelos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Governatori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hull</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">L</forename><surname>Rosa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Leopold</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Leymann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Recker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Reichert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">A</forename><surname>Reijers</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Rinderle-Ma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Solti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rosemann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Schulte</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">P</forename><surname>Singh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Slaats</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Staples</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Weber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Weidlich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Weske</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Xu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Zhu</surname></persName>
		</author>
		<idno type="DOI">10.1145/3183367</idno>
		<ptr target="https://doi.org/10.1145/3183367" />
	</analytic>
	<monogr>
		<title level="j">ACM Trans. Management Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">16</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Nakamoto</surname></persName>
		</author>
		<title level="m">Bitcoin: A peer-to-peer electronic cash system</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m">OMG: Business process model and notation</title>
				<imprint>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Blockchain inefficiency in the bitcoin network</title>
		<author>
			<persName><forename type="first">G</forename><surname>Pappalardo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Di Matteo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Caldarelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Aste</surname></persName>
		</author>
		<idno type="DOI">10.1140/epjds/s13688-018-0159-3</idno>
		<ptr target="https://doi.org/10.1140/epjds/s13688-018-0159-3" />
	</analytic>
	<monogr>
		<title level="j">EPJ Data Sci</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">30</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Time and Petri Nets</title>
		<author>
			<persName><forename type="first">L</forename><surname>Popova-Zeugmann</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">A lean architecture for blockchain based decentralized process execution</title>
		<author>
			<persName><forename type="first">C</forename><surname>Sturm</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Szalanczi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Schönig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Jablonski</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-11641-529</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-11641-529" />
	</analytic>
	<monogr>
		<title level="m">Business Process Management Workshops -BPM 2018 International Workshops</title>
				<meeting><address><addrLine>Sydney, NSW, Australia</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">September 9-14, 2018. 2018</date>
			<biblScope unit="page" from="361" to="373" />
		</imprint>
	</monogr>
	<note>Revised Papers</note>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Untrusted business process monitoring and execution using blockchain</title>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Xu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Riveret</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Governatori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ponomarev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mendling</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-319-45348-419</idno>
		<ptr target="https://doi.org/10.1007/978-3-319-45348-419" />
	</analytic>
	<monogr>
		<title level="m">Business Process Management -14th International Conference, BPM 2016</title>
				<meeting><address><addrLine>Rio de Janeiro, Brazil</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2016">September 18-22, 2016. 2016</date>
			<biblScope unit="page" from="329" to="347" />
		</imprint>
	</monogr>
	<note>Proceedings.</note>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">Business Process Management -Concepts, Languages, Architectures</title>
		<author>
			<persName><forename type="first">M</forename><surname>Weske</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-642-28616-2</idno>
		<ptr target="https://doi.org/10.1007/978-3-642-28616-2" />
		<imprint>
			<date type="published" when="2012">2012</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
	<note>2nd Edition</note>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Ethereum: A secure decentralised generalised transaction ledger</title>
		<author>
			<persName><forename type="first">G</forename><surname>Wood</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Ethereum project yellow paper</title>
		<imprint>
			<biblScope unit="volume">151</biblScope>
			<biblScope unit="page" from="1" to="32" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Predicting latency of blockchainbased systems using architectural modelling and simulation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Yasaweerasinghelage</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Staples</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Weber</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICSA.2017.22</idno>
		<ptr target="https://doi.org/10.1109/ICSA.2017.22" />
	</analytic>
	<monogr>
		<title level="m">2017 IEEE International Conference on Software Architecture, ICSA 2017</title>
				<meeting><address><addrLine>Gothenburg, Sweden</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017">April 3-7, 2017. 2017</date>
			<biblScope unit="page" from="253" to="256" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
