<?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">CEUR Workshop Proceedings (CEUR-WS.org) Blockchain Interoperability</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Guzmán</forename><surname>Llambías</surname></persName>
							<email>guzman.llambias@pyxis.com.uy</email>
							<affiliation key="aff0">
								<orgName type="department">Facultad de ingeniería</orgName>
								<orgName type="institution">Universidad de la República</orgName>
								<address>
									<settlement>Montevideo</settlement>
									<country key="UY">Uruguay</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Pyxis</orgName>
								<address>
									<settlement>Montevideo</settlement>
									<country key="UY">Uruguay</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">CEUR Workshop Proceedings (CEUR-WS.org) Blockchain Interoperability</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">C9162E5D3F32A7D065D08DB549919985</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-06-19T14:26+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>Distributed Ledger Technologies (DLT)</term>
					<term>blockchain</term>
					<term>interoperability</term>
					<term>cross-chain transactions</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Blockchain is one of the most disrupting technologies in recent years and has been used in several domains, such as health, supply chain and finance. In addition, organisations started integrating their blockchains with other blockchains or other external software systems. However, this is challenging for blockchain systems as interoperability is not a native design feature. Several academic and industrial efforts were performed to enable blockchain interoperability in the last years, but they were proposed for specific domain scenarios. To the best of our knowledge, there is not a general-purpose interoperability solution that enables blockchain interoperability. This research project aims to define a general-purpose blockchain interoperability framework to enable blockchain interoperability. This framework will comprise methods, guidelines, specifications and software pieces that ease interoperability between blockchains. This paper presents this research project, describing its research questions, the adopted and projected research methodologies, preliminary results and its current status.</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>Blockchain is a technology that enables decentralised payments across participants without the need of a centralised trusted third-party. Furthermore, blockchain became a suitable technology for other domains besides finance, such as health, Internet of Things (IOT) and supply chain, among others. Indeed, blockchains are used on open and permissionless scenarios where security, transparency and anonymity are key requirements, but also on closed and permissioned scenarios, where user identity, authorisation and privacy are needed. In addition, organisations started to increasingly require that permissionless and permissioned blockchains interoperate with other blockchains and external software systems. This requirement represents a challenge, as blockchains are isolated information systems, and interoperability was not part of their design. In particular, organisations are required to implement data transfer, asset transfer and asset exchange scenarios. A data transfer scenario involves copying information from a source blockchain to a target blockchain. An asset transfer scenario requires the transfer of an asset (e.g. cryptocurrency) from a source blockchain to a target blockchain, while an asset exchange scenario involves the atomic exchange of assets that belong to different blockchains.</p><p>Blockchain interoperability differs from traditional software interoperability. Blockchain systems maintain a state following rules defined by their consensus protocol, and only data that satisfy these rules may be registered on the blockchain. Therefore, enabling interoperability between blockchains implies that there must be a consensus between blockchains about the validity of the exchanged information, which is a complex challenge. Furthermore, being blockchain a decentralised system where participants need to reach finality about their results, it is challenging for this technology to access external data that can be dynamic by nature (e.g. invoking an API of an external system). Secure integration mechanisms need to be used to ensure the blockchain's consistency.</p><p>In the last years, efforts to enable blockchain interoperability were proposed with quite a success for domain specific scenarios -such as asset transfer -(e.g. Polygon PoS Bridge <ref type="bibr" target="#b0">[1]</ref>) and between specific blockchains (e.g. Ethereum <ref type="bibr" target="#b1">[2]</ref> and Polygon). However, to the best of our knowledge, a general-purpose interoperability solution for blockchain systems is not yet available.</p><p>This paper provides an overview of the PhD thesis's research goals, which are focused on blockchain interoperability. The paper is structured as follows: Section 2 introduces related work on blockchain interoperability. Section 3 presents the objective of this thesis and the proposed research questions. Section 4 presents the research methodologies to be used in this thesis. Section 5 describes preliminary results and contributions, while Section 6 presents the conclusions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related work</head><p>Blockchain interoperability has gained special attention in the research community in recent years, where several literature reviews analysed the state-of-the-art <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b3">4]</ref>. In particular, Belchior et al. presented the most exhaustive survey <ref type="bibr" target="#b2">[3]</ref>, where they proposed categorising blockchain interoperability solutions into three categories: Public Connectors, Hyrbrid Connectors and Blockchain of Blockchains. These categories also have the following subcategories: Notary Scheme, Hash Time Lock Contracts (HTLC), Sidechains, Trusted Relays, Agnostic Protocols and Blockchain Migrators. Scheid et al. <ref type="bibr" target="#b4">[5]</ref> and Li et al. <ref type="bibr" target="#b5">[6]</ref> presented two examples of Notary Scheme solutions, while there are several proposals for HTLC <ref type="bibr" target="#b3">[4]</ref>. Zendoo is an example of a Sidechain solution using Zero Knowledge Proof for cryptocurrency transfers <ref type="bibr" target="#b6">[7]</ref>. Abebe et al. <ref type="bibr" target="#b7">[8]</ref> presented a solution based on Trusted Relays between two blockchains, based on Hyperledger Fabric on a data exchange scenario. Liu et al. <ref type="bibr" target="#b8">[9]</ref> presented Hyperservice, belonging to the Agnostic Protocols category, where they proposed a platform for the modelling and specifying smart contracts to enable interoperability between blockchains in an asset exchange scenario. Scheid et al. <ref type="bibr" target="#b9">[10]</ref> proposed a Blockchain Migrator solution, defining a framework based on policies for blockchain selection. On the other hand, Blockchain of Blockchains is the most novel and least studied category <ref type="bibr" target="#b3">[4]</ref>. Other authors provided other classifications but were less exhaustive. For example, Koens et al. <ref type="bibr" target="#b10">[11]</ref> proposed a classification based on twelve properties, but only included Notary Scheme, Sidechains and HTLC categories.</p><p>Regarding software architecture, Jin et al. proposed a reference architecture for blockchain interoperability based on the OSI network layers <ref type="bibr" target="#b11">[12]</ref>. In addition, Hardjono et al. proposed an interoperability architecture based on Gateways, taking the internet model as an inspiration <ref type="bibr" target="#b12">[13]</ref>.</p><p>Some formalisation of blockchain interoperability has been proposed. Kiayias et al. <ref type="bibr" target="#b13">[14]</ref> and then Gaži et al. <ref type="bibr" target="#b14">[15]</ref> formalized the Sidechain solution for two consensus protocols: Proof-of-Work and Proof-of-Stake. Herlihy <ref type="bibr" target="#b15">[16]</ref> formalised the HTLC solution through game theory. Zamyatin et al. <ref type="bibr" target="#b16">[17]</ref> proved that achieving cross-chain communication without a trusted third party is impossible. At the same time, Lafourcade and Lombard-Platet <ref type="bibr" target="#b17">[18]</ref> showed that it is impossible to achieve interoperability between two blockchains under the classical definition of blockchain. However, if this definition is relaxed, it is possible to achieve interoperability, creating a two-in-one blockchain (i.e. a blockchain with two ledgers).</p><p>Most of the academic community had focused on enabling interoperability between nonpermissioned blockchains, while a small-scale effort was put into permissioned blockchain interoperability. This effort is even less for enabling interoperability between permissioned and permissionless blockchains <ref type="bibr" target="#b3">[4]</ref>. Abebe et al. <ref type="bibr" target="#b7">[8]</ref> and Bradach et al. <ref type="bibr" target="#b18">[19]</ref> provide two solutions for permissioned blockchain interoperability. Franzoni <ref type="bibr" target="#b19">[20]</ref> and Falazi et al. <ref type="bibr" target="#b20">[21]</ref> propose two solutions to interoperate permissioned and permissionless blockchains but do not provide cross-chain transaction validations.</p><p>On the other hand, the industry has been active in proposing solutions for blockchain interoperability. Blocknet enables blockchain interoperability based on two components: XBridge and XRouter <ref type="bibr" target="#b21">[22]</ref>. By design, Blocknet may enable interoperability between permissioned and permissionless blockchains, but to the best of our knowledge, only permissionless blockchains are supported. ARK is a permissionless blockchain that enables blockchain interoperability by using two protocols: Specific Smart Bridge and Protocol-Agnostic Smart Bridge <ref type="bibr" target="#b22">[23]</ref>. ARK enables interoperability between Bitcoin and Ethereum, as well as other Bitcoin-based Blockchains. Hyperledger Cactus <ref type="bibr" target="#b23">[24]</ref>, Weaver <ref type="bibr" target="#b24">[25]</ref>, and YIU <ref type="bibr" target="#b25">[26]</ref> are three incubated projects developed by Hyperledger to achieve blockchain interoperability. Hyperledger Cactus provides a framework that business applications may use to interoperate with heterogeneous blockchains and currently supports Hyperledger Fabric <ref type="bibr" target="#b26">[27]</ref>, Hyperledger Besu <ref type="bibr" target="#b27">[28]</ref>, Corda <ref type="bibr" target="#b28">[29]</ref> and Quorum <ref type="bibr" target="#b29">[30]</ref>. Weaver is a Trusted Relay based solution, where each blockchain must have an IOP module and a Trusted Relay. The IOP module is responsible for cross-chain transaction verification, while the Relay is responsible for cross-blockchain communication. YIU implements the IBC (Inter-Blockchain Communication) protocol proposed by Cosmos <ref type="bibr" target="#b30">[31]</ref>  <ref type="bibr" target="#b31">[32]</ref>. With this approach, every blockchain must have an IBC module that implements the protocol and is responsible of the connectivity and verification of cross-chain transactions. YIU currently supports Hyperledger Besu, Hyperledger Fabric and Corda. Finally, Cosmos and Polkadot <ref type="bibr" target="#b32">[33]</ref> are two blockchain of blockchains solutions with similar behaviour. Cosmos relies on the IBC protocol to enable interoperability between blockchains and requires the interoperating blockchains to modify their source code to support the protocol. On the other hand, Polkadot uses bridges to enable interoperability between blockchains and also requires changes in the blockchain source code. Both solutions use a main blockchain that provides a consensus protocol to validate cross-blockchain transactions. Finally, Optimism <ref type="bibr" target="#b33">[34]</ref> and Polygon PoS Bridge <ref type="bibr" target="#b0">[1]</ref> are two examples of Sidechain solution that allows asset transfer between Ethereum and other Ethereum Virtual Machine based blockchains. In particular, Optimism enables asset transfer between Ethereum and Optimism, and vice versa, while Polygon PoS Bridge enables asset transfer between Ethereum and Polygon. Both solutions provide cross-chain transaction verification but are specific solutions for asset transfer between two specific permissionless blockchains.</p><p>Considering the existing work, blockchain interoperability has had significant advances since the first proposals, but there are still challenges to be solved. Despite the current work, there is no consensus in the scientific community about a blockchain interoperability definition nor a categorisation of the existing solutions <ref type="bibr" target="#b3">[4]</ref>. Existing approaches are platform specific (e.g. Polygon) and do not yet provide a general-purpose interoperability solution.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Objective and research questions</head><p>The main objective of this PhD thesis is to provide an approach to enable interoperability between blockchain platforms for general-purpose scenarios. To this end, this PhD thesis proposes the following research questions.</p><p>RQ1: What challenges exist to enable blockchain interoperability? RQ2: What factors need to be considered to enable blockchain interoperability? RQ3: What approaches exist to enable blockchain interoperability? RQ4: What challenges are not covered by the existing approaches, and how can they be addressed?</p><p>RQ5: How can a reference framework be developed to support blockchain interoperability? RQ6: How can this framework be applied to existing blockchains?</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Research methodology</head><p>This PhD thesis follows the Design Science research (DSR) as it constitutes a suitable methodology to reach the research goals and provide solutions to the research questions.</p><p>The DSR is an incremental process that designs and evaluates artefacts intended to solve identified organisational problems <ref type="bibr" target="#b34">[35]</ref>. DSR uses existing knowledge (e.g. theories, frameworks, methods, methodologies) applied to existing needs of organisations and people to build new artefacts or improve existing ones in an iterative process. The followed methodology is described in Fig. <ref type="figure" target="#fig_0">1</ref> and is composed of four stages. At stage one, a literature review is performed to understand the motivation of blockchain interoperability, identify challenges and define the requirements of the artefact (i.e. the reference framework). Stage two takes these requirements to design the first iteration of the artefact. In stage three, the artefact is evaluated through design evaluation methods (e.g. observational, analytical, experimental). At this stage and after the evaluation of the obtained results, the process may return to stage two for the improvement of the artefact. The results are later communicated at conferences, workshops and journals at stage four, where new feedback is gathered from the research community. After this last stage is finished, the process starts again. It continues on stage two unless a defined number of iterations is reached and enables the finalisation of this PhD thesis.</p><p>Stage one is partially completed and was developed by adopting some features of the PRISMA statement <ref type="bibr" target="#b35">[36]</ref>.</p><p>We plan to execute stage two through an iterative process, following a bottom-up approach. The first iterations of the methodology will focus on the foundations of the artefact, and the following iterations will focus on building new features and its evolution.</p><p>We plan to evaluate the artefact through several evaluation methods at stage three <ref type="bibr" target="#b36">[37]</ref>. In particular, we plan to use prototypes and illustrative scenarios to demonstrate its utility. Technical experiments, such as performance testing, will be performed to evaluate the technical performance of the artefact. An assessment through expert evaluation is planned to show the suitability of the artefact. Subject-based experiments are planned to test the artefact with different blockchains.</p><p>Finally, at stage four we plan to communicate our research results through scholarly research and professional publications. The first may include academic seminars, conferences, workshops and journals whose audience are students and researchers. The professional publications include technical reports and industry conference talks, and aims to a practitioners audience (industry and government).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Preliminary ideas, results and contributions</head><p>Fig. <ref type="figure" target="#fig_1">2</ref> depicts the expected blockchain interoperability framework as the artefact to be built. The artefact is composed of a set of elements. The theoretical concepts element describes the background concepts regarding blockchain interoperability and related concepts to understand the framework. The decision guidelines element provides decision guidelines to select the most suitable blockchain interoperability solution according to the business requirements. The design patterns element describes blockchain interoperability patterns that can be used to build a blockchain interoperability solution. The solution specification element describes a specification of a blockchain interoperability solution that enables interoperability between two or more blockchains. A reference implementation of the specification is another element that provides software following the specification. This software can be used to enable interoperability between two specific blockchains (e.g. Ethereum and Hyperledger Fabric). Finally, a set of case scenarios that shows the usage of the framework constitutes its last element.</p><p>This PhD started with stage one to answer RQ1, RQ2 and RQ3. At this stage, a literature review was performed, which analysed sixty-two papers and proposed a feature-based classification framework to improve the classification of blockchain interoperability solutions <ref type="bibr" target="#b3">[4]</ref>. This literature review enabled the identification of challenges and requirements for developing the reference framework. Furthermore, this work constitutes the basis of the theoretical element of the framework. The first iteration of the methodology was finished and provided the first preliminary results, enabling interoperability between two permissioned blockchains on a specific social security scenario <ref type="bibr" target="#b18">[19]</ref>. These results included a first version of the specification element, a prototype that served as a preliminary version of the reference implementation and an illustrative scenario that will be part of the case scenario element. The prototype and the illustrative scenario served as the evaluation methods of these results. The experiment had some limitations as it did not consider cross-chain transaction authentication, cross-chain transaction authorisation, or data privacy properties of permissioned blockchains. An extended version of this work was recently submitted to a journal where further assessment was performed based on two blockchain interoperability frameworks <ref type="bibr" target="#b37">[38]</ref>.</p><p>The ongoing work of this PhD thesis consists of starting the second iteration of the methodology and the redesign of the artefact based on the obtained results and research community feedback. The first iteration provided a tailored made interoperability solution for two specific permissioned blockchains on a specific social security scenario. The second iteration pursued the evolution of the previous elements to build a general-purpose interoperability solution. In this case, the evolution of the specification, reference implementation and case scenarios elements. Furthermore, this iteration introduced permissionless blockchains and aimed to enable interoperability between permissionless and permissioned blockchains. In particular, between Ethereum and Hyperledger Fabric. The iteration is on stage four (communication stage), where the obtained results are planned to be submitted to a workshop or conference.</p><p>On a third iteration, it is planned to start the development of the design patterns and the decision framework elements. The works of Pillai et al. will inspire the latter <ref type="bibr" target="#b38">[39]</ref> and Belchior et al. <ref type="bibr" target="#b39">[40]</ref> with further development.</p><p>At the end of this PhD thesis, we envision a reference blockchain interoperability framework that practitioners and researchers may use to enable interoperability between two or more blockchains. In addition, students and researchers may use the framework to get introduced to this topic and extend it with new features.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusions</head><p>Blockchain is a disrupting technology that was applied in multiple domains (e.g. health, IOT, supply chain, art), but its usage is limited because of its design principles. Blockchains are isolated systems that work as silos of information, and interoperability is not part of their native design. It is a challenge for a blockchain to interoperate with other blockchains or other external systems. In the last years, some industrial and academic approaches enabled blockchain interoperability but they were limited to specific domain scenarios. To the best of our knowledge, there is not a general-purpose interoperability solution that enables blockchain interoperability.</p><p>This paper presents the approach of my PhD thesis, where its main objective is the development of a general-purpose interoperability framework that enables blockchain interoperability.</p><p>This PhD thesis follows a Design Science Research methodology with different stages. The first stage provided a survey on blockchain interoperability state of the art, identifying challenges and defining of the proposed research questions. Further stages enabled the development of the first elements of the artefact. The first result was a gateway-based middleware that enabled interoperability between two permissioned blockchains on a specific based scenario. These elements are being evolved in the next iterations of the methodology. In particular, the evolution to include permissionless and permissioned blockchain interoperability, cross-chain transaction authentication and new elements of the framework, like the design guidelines and design patterns.</p><p>The main contribution of this PhD thesis is the definition of a blockchain interoperability framework that provides solutions for general-purpose interoperability between blockchain platforms. Future work will include the evolution of the framework by enhancing its elements and building blocks. We envision that this framework may ease the development of blockchain interoperability solutions and positively impact their quality. In addition, this PhD thesis will provide an organised knowledge base that may be the baseline for future academic research.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Proposed methodology based on Design Science Research</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Blockchain interoperability reference framework</figDesc><graphic coords="6,213.77,83.66,222.71,172.74" type="bitmap" /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>I want to thank Dra. Laura González and Dr. Raúl Ruggia from Universidad de la República for the supervision of this PhD thesis. Guzmán Llambías is supported by Pyxis. The research that gives rise to the results presented in this publication received funding from the Agencia Nacional de Investigación e Innovación under the code POS_NAC_2022_4_174476. Blockchain icons created by Freepik -Flaticon.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Introduction to polygon pos</title>
		<ptr target="https://wiki.polygon.technology/docs/develop/getting-started" />
		<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<author>
			<persName><forename type="first">V</forename><surname>Buterin</surname></persName>
		</author>
		<ptr target="https://ethereum.org/en/whitepaper/" />
		<title level="m">Ethereum: A next-generation smart contract and decentralized application platform</title>
				<imprint>
			<date type="published" when="2014-04">2014. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">A survey on blockchain interoperability: Past, present, and future trends</title>
		<author>
			<persName><forename type="first">R</forename><surname>Belchior</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Vasconcelos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Guerreiro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Correia</surname></persName>
		</author>
		<idno type="DOI">10.1145/3471140</idno>
		<ptr target="https://doi.org/10.1145/3471140.doi:10.1145/3471140" />
	</analytic>
	<monogr>
		<title level="j">ACM Comput. Surv</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page" from="1" to="41" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Blockchain interoperability: a feature-based classification framework and challenges ahead</title>
		<author>
			<persName><forename type="first">G</forename><surname>Llambías</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>González</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ruggia</surname></persName>
		</author>
		<idno type="DOI">10.19153/cleiej.25.3.4</idno>
		<ptr target="https://doi.org/10.19153/cleiej.25.3.4" />
	</analytic>
	<monogr>
		<title level="j">CLEI Electronic Journal</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="page" from="4" to="5" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Bifröst: a modular blockchain interoperability api</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">J</forename><surname>Scheid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hegnauer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Rodrigues</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Stiller</surname></persName>
		</author>
		<idno type="DOI">10.1109/LCN44214.2019.8990860</idno>
		<ptr target="https://doi.org/10.1109/LCN44214.2019.8990860" />
	</analytic>
	<monogr>
		<title level="m">IEEE 44th Conference Local Computer Networks</title>
				<meeting><address><addrLine>Osnabrueck, Germany</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="332" to="339" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Agentchain: A decentralized cross-chain exchange system</title>
		<author>
			<persName><forename type="first">D</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Tang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Q</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Guan</surname></persName>
		</author>
		<idno type="DOI">10.1109/TrustCom/BigDataSE.2019.00072</idno>
		<ptr target="https://doi.org/10.1109/TrustCom/BigDataSE.2019.00072.doi:10.1109/TrustCom/BigDataSE.2019.00072" />
	</analytic>
	<monogr>
		<title level="m">18th IEEE International Conference On Trust, Security And Privacy In Computing And Communications/13th IEEE International Conference On Big Data Science And Engineering (TrustCom/BigDataSE)</title>
				<meeting><address><addrLine>Rotorua, New Zealand</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="page" from="491" to="498" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Zendoo: a zk-snark verifiable cross-chain transfer protocol enabling decoupled and decentralized sidechains</title>
		<author>
			<persName><forename type="first">A</forename><surname>Garoffolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kaidalov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Oliynykov</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICDCS47774.2020.00161</idno>
		<ptr target="https://doi.org/10.1109/ICDCS47774.2020.00161.doi:10.1109/ICDCS47774.2020.00161" />
	</analytic>
	<monogr>
		<title level="m">IEEE 40th Int. Conf. Dist. Comp. Sys</title>
				<meeting><address><addrLine>Singapore, Singapore</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020. 2020</date>
			<biblScope unit="page" from="1257" to="1262" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Enabling enterprise blockchain interoperability with trusted data transfer (industry track)</title>
		<author>
			<persName><forename type="first">E</forename><surname>Abebe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Behl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Govindarajan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Hu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Karunamoorthy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Novotny</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Pandit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Ramakrishna</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Vecchiola</surname></persName>
		</author>
		<idno type="DOI">10.1145/3366626.3368129</idno>
		<idno>doi:10.1145/3366626.3368129</idno>
		<ptr target="https://doi.org/10.1145/3366626.3368129" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 20th International Middleware Conference Industrial Track</title>
				<meeting>the 20th International Middleware Conference Industrial Track<address><addrLine>Davis, CA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="29" to="35" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Hyperservice: Interoperability and programmability across heterogeneous blockchains</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Xiang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Shi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Gao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Xiao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Wen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y.-C</forename><surname>Hu</surname></persName>
		</author>
		<idno type="DOI">10.1145/3319535.3355503</idno>
		<idno>doi:10. 1145/3319535.3355503</idno>
		<ptr target="https://doi.org/10.1145/3319535.3355503" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2019 ACM SIGSAC Conference on Computer and Communications Security</title>
				<meeting>the 2019 ACM SIGSAC Conference on Computer and Communications Security<address><addrLine>London, United Kingdom</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="549" to="566" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Toward a policy-based blockchain agnostic framework</title>
		<author>
			<persName><forename type="first">E</forename><surname>Scheid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Rodrigues</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Stiller</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IFIP/IEEE Symposium on Integrated Network and Service Management (IM)</title>
				<meeting><address><addrLine>Arlington, VA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="page" from="609" to="613" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Assessing interoperability solutions for distributed ledgers</title>
		<author>
			<persName><forename type="first">T</forename><surname>Koens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Poll</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.pmcj.2019.101079</idno>
		<ptr target="https://doi.org/10.1016/j.pmcj.2019.101079" />
	</analytic>
	<monogr>
		<title level="j">Pervasive and Mobile Computing</title>
		<imprint>
			<biblScope unit="volume">59</biblScope>
			<biblScope unit="page">101079</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Towards a novel architecture for enabling interoperability amongst multiple blockchains</title>
		<author>
			<persName><forename type="first">H</forename><surname>Jin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Dai</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Xiao</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICDCS.2018.00120</idno>
		<ptr target="https://doi.org/10.1109/ICDCS.2018.00120.doi:10.1109/ICDCS.2018.00120" />
	</analytic>
	<monogr>
		<title level="m">IEEE 38th Int. Conf. Dist. Comp. Sys</title>
				<meeting><address><addrLine>Vienna, Austria</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">2018. 2018</date>
			<biblScope unit="page" from="1203" to="1211" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Toward an interoperability architecture for blockchain autonomous systems</title>
		<author>
			<persName><forename type="first">T</forename><surname>Hardjono</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lipton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Pentland</surname></persName>
		</author>
		<idno type="DOI">10.1109/TEM.2019.2920154</idno>
		<ptr target="https://doi.org/10.1109/TEM.2019.2920154.doi:10.1109/TEM.2019.2920154" />
	</analytic>
	<monogr>
		<title level="j">IEEE Transactions on Engineering Management</title>
		<imprint>
			<biblScope unit="volume">67</biblScope>
			<biblScope unit="page" from="1298" to="1309" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Proof-of-work sidechains</title>
		<author>
			<persName><forename type="first">A</forename><surname>Kiayias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zindros</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-43725-1_3</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-43725-1_3" />
	</analytic>
	<monogr>
		<title level="m">Financial Cryptography and Data Security</title>
				<meeting><address><addrLine>St. Kitts, St. Kitts and Nevis</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="page" from="21" to="34" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Proof-of-stake sidechains</title>
		<author>
			<persName><forename type="first">P</forename><surname>Gaži</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kiayias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zindros</surname></persName>
		</author>
		<idno type="DOI">10.1109/SP.2019.00040</idno>
		<ptr target="https://doi.org/10.1109/SP.2019.00040.doi:10.1109/SP.2019.00040" />
	</analytic>
	<monogr>
		<title level="m">2019 IEEE Symposium on Security and Privacy (SP)</title>
				<meeting><address><addrLine>San Francisco, CA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="139" to="156" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Atomic cross-chain swaps</title>
		<author>
			<persName><forename type="first">M</forename><surname>Herlihy</surname></persName>
		</author>
		<idno type="DOI">10.1145/3212734.3212736</idno>
		<idno>doi:10.1145/3212734.3212736</idno>
		<ptr target="https://doi.org/10.1145/3212734.3212736" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2018 ACM Symposium on Principles of Distributed Computing</title>
				<meeting>the 2018 ACM Symposium on Principles of Distributed Computing<address><addrLine>Egham United Kingdom</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="245" to="254" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Sok: Communication across distributed ledgers</title>
		<author>
			<persName><forename type="first">A</forename><surname>Zamyatin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Al-Bassam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zindros</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Kokoris-Kogias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Moreno-Sanchez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kiayias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">J</forename><surname>Knottenbelt</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-662-64331-0_1</idno>
		<ptr target="https://doi.org/10.1007/978-3-662-64331-0_1" />
	</analytic>
	<monogr>
		<title level="m">Financial Cryptography and Data Security, Virtual Event</title>
				<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="3" to="36" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">About blockchain interoperability</title>
		<author>
			<persName><forename type="first">P</forename><surname>Lafourcade</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Lombard-Platet</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.ipl.2020.105976</idno>
		<ptr target="https://doi.org/10.1016/j.ipl.2020.105976" />
	</analytic>
	<monogr>
		<title level="j">Information Processing Letters</title>
		<imprint>
			<biblScope unit="volume">161</biblScope>
			<biblScope unit="page">105976</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">A gateway-based interoperability solution for permissioned blockchains</title>
		<author>
			<persName><forename type="first">B</forename><surname>Bradach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Nogueira</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Llambías</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>González</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ruggia</surname></persName>
		</author>
		<idno type="DOI">10.1109/CLEI56649.2022.9959907</idno>
	</analytic>
	<monogr>
		<title level="m">2022 XVLIII Latin American Computer Conference (CLEI)</title>
				<imprint>
			<date type="published" when="2022">2022</date>
			<biblScope unit="page" from="1" to="10" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Franzoni</surname></persName>
		</author>
		<title level="m">Blockchain and smart contracts in the Fashion industry</title>
				<meeting><address><addrLine>TO, Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
		<respStmt>
			<orgName>Politecnico di Torino</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Master&apos;s thesis</note>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Unified integration of smart contracts through service orientation</title>
		<author>
			<persName><forename type="first">G</forename><surname>Falazi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lamparelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Breitenbuecher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Daniel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Leymann</surname></persName>
		</author>
		<idno type="DOI">10.1109/MS.2020.2994040</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Software</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="page" from="60" to="66" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Culwick</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Metcalf</surname></persName>
		</author>
		<ptr target="https://docs.blocknet.org/project/blocknet-whitepaper.pdf" />
		<title level="m">Blocknet design specifications</title>
				<imprint>
			<date type="published" when="2018-04">2018. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<monogr>
		<ptr target="https://ark.io/Whitepaper.pdf" />
		<title level="m">Ark ecosystem whitepaper</title>
				<imprint>
			<date type="published" when="2019-04">2019. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><surname>Montgomery</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Borne-Pons</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hamilton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Bowman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Somogyvari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Fujimoto</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Takeuchi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Kuhrt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Belchior</surname></persName>
		</author>
		<ptr target="https://github.com/hyperledger/cactus/blob/main/whitepaper/whitepaper.md" />
		<title level="m">Hyperledger cactus whitepaper</title>
				<imprint>
			<date type="published" when="2022-04">2022. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<author>
			<persName><forename type="first">Weaver</forename><surname>Team</surname></persName>
		</author>
		<author>
			<persName><surname>Weaver</surname></persName>
		</author>
		<ptr target="https://labs.hyperledger.org/weaver-dlt-interoperability/" />
		<title level="m">Dlt interoperability framework</title>
				<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Yui</forename><surname>Datachain</surname></persName>
		</author>
		<ptr target="https://www.datachain.jp/products/yui" />
		<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<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><forename type="middle">De</forename><surname>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>
		<author>
			<persName><forename type="first">S</forename><surname>Muralidharan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Murthy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Nguyen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Sethi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Singh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Sorniotti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Stathakopoulou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Vukolić</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">W</forename><surname>Cocco</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Yellick</surname></persName>
		</author>
		<idno type="DOI">10.1145/3190508.3190538</idno>
		<ptr target="https://doi.org/10.1145/3190508.3190538" />
	</analytic>
	<monogr>
		<title level="m">Proc. 13th EuroSys Conf</title>
				<meeting>13th EuroSys Conf<address><addrLine>Porto, Portugal</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="1" to="15" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<monogr>
		<ptr target="https://besu.hyperledger.org/en/stable/" />
		<title level="m">Hyperledger besu ethereum client</title>
				<imprint>
			<date type="published" when="2022-04">2022. Apr. 2023</date>
		</imprint>
	</monogr>
	<note>Hyperledger Besu community</note>
</biblStruct>

<biblStruct xml:id="b28">
	<monogr>
		<title level="m" type="main">Corda: An introduction</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">G</forename><surname>Brown</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Carlyle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Grigg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hearn</surname></persName>
		</author>
		<ptr target="https://docs.r3.com/en/pdf/corda-introductory-whitepaper.pdf" />
		<imprint>
			<date type="published" when="2016-04">2016. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Goquorum</forename><surname>Consensys</surname></persName>
		</author>
		<ptr target="https://consensys.net/docs/goquorum//en/latest/concepts/blockchain-basics/" />
		<imprint>
			<date type="published" when="2022-04">2022. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b30">
	<monogr>
		<title level="m" type="main">The interblockchain communication protocol: An overview</title>
		<author>
			<persName><forename type="first">C</forename><surname>Goes</surname></persName>
		</author>
		<idno type="DOI">10.48550/ARXIV.2006.15918</idno>
		<ptr target="https://arxiv.org/abs/2006.15918.doi:10.48550/ARXIV.2006.15918" />
		<imprint>
			<date type="published" when="2020-04">2020. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b31">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><surname>Kwon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Buchman</surname></persName>
		</author>
		<ptr target="https://v1.cosmos.network/resources/whitepaper" />
		<title level="m">Cosmos whitepaper</title>
				<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b32">
	<monogr>
		<author>
			<persName><forename type="first">Web3</forename><surname>Foundation</surname></persName>
		</author>
		<ptr target="https://polkadot.network/Polkadot-lightpaper.pdf" />
		<title level="m">An introduction to polkadot</title>
				<imprint>
			<date type="published" when="2020-04">2020. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b33">
	<monogr>
		<ptr target="https://community.optimism.io/docs/developers/bridge/basics/" />
		<title level="m">Optimism Team, Bridging basics</title>
				<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b34">
	<analytic>
		<title level="a" type="main">Design science in information systems research</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Hevner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">T</forename><surname>March</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ram</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">MIS Q</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="page" from="75" to="105" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b35">
	<analytic>
		<title level="a" type="main">Preferred reporting items for systematic reviews and meta-analyses: the prisma statement</title>
		<author>
			<persName><forename type="first">D</forename><surname>Moher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Liberati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Tetzlaff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">G</forename><surname>Altman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Group</surname></persName>
		</author>
		<author>
			<persName><forename type="first">*</forename></persName>
		</author>
		<idno type="DOI">10.1371/journal.pmed.1000097</idno>
		<ptr target="https://doi.org/10.1371/journal.pmed.1000097" />
	</analytic>
	<monogr>
		<title level="j">Annals of internal medicine</title>
		<imprint>
			<biblScope unit="volume">151</biblScope>
			<biblScope unit="page" from="264" to="269" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b36">
	<analytic>
		<title level="a" type="main">Design science research evaluation</title>
		<author>
			<persName><forename type="first">K</forename><surname>Peffers</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Rothenberger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Tuunanen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Vaezi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Design Science Research in Information Systems</title>
				<meeting><address><addrLine>Berlin Heidelberg; Berlin, Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="398" to="410" />
		</imprint>
	</monogr>
	<note>Advances in Theory and Practice</note>
</biblStruct>

<biblStruct xml:id="b37">
	<monogr>
		<title level="m" type="main">Gateway-based Interoperability for DLT</title>
		<author>
			<persName><forename type="first">G</forename><surname>Llambías</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Bradach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Nogueira</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>González</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ruggia</surname></persName>
		</author>
		<ptr target="https://www.techrxiv.org/articles/preprint/Gateway-based_Interoperability_for_DLT/22120520" />
		<imprint>
			<date type="published" when="2023-04">2023. Apr. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b38">
	<analytic>
		<title level="a" type="main">Cross-blockchain technology: Integration framework and security assumptions</title>
		<author>
			<persName><forename type="first">B</forename><surname>Pillai</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Biswas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Hóu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Muthukkumarasamy</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2022.3167172</idno>
		<ptr target="https://doi.org/10.1109/ACCESS.2022.3167172" />
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="page" from="41239" to="41259" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b39">
	<analytic>
		<title level="a" type="main">Do you need a distributed ledger technology interoperability solution?</title>
		<author>
			<persName><forename type="first">R</forename><surname>Belchior</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Riley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hardjono</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Vasconcelos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Correia</surname></persName>
		</author>
		<idno type="DOI">10.1145/3564532</idno>
		<ptr target="https://doi.org/10.1145/3564532.doi:10.1145/3564532" />
	</analytic>
	<monogr>
		<title level="j">Distrib. Ledger Technol</title>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
	<note>just Accepted</note>
</biblStruct>

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