Skip to content
Snippets Groups Projects
Commit 8a454abd authored by Guzman Llambias's avatar Guzman Llambias
Browse files

Update README.md

parent d8393f41
No related branches found
No related tags found
No related merge requests found
...@@ -7,6 +7,6 @@ This repository holds the artefacts that raised the results of our first paper _ ...@@ -7,6 +7,6 @@ This repository holds the artefacts that raised the results of our first paper _
In this paper, we explore the formalisation of a gateway-based interoperability solution with Event-B. The results showed that the method was suitable and that a straightforward specification could be developed considering Ethereum and Hyperledger Fabric as the involved blockchains. The Event-B specification was assessed with three strategies that enabled its verification and validation. In particular, formal verification (e.g. safety properties), functional validation, and functional utility. These promising results constitute a step forward in the development of formal specifications for blockchain interoperability solutions. In this paper, we explore the formalisation of a gateway-based interoperability solution with Event-B. The results showed that the method was suitable and that a straightforward specification could be developed considering Ethereum and Hyperledger Fabric as the involved blockchains. The Event-B specification was assessed with three strategies that enabled its verification and validation. In particular, formal verification (e.g. safety properties), functional validation, and functional utility. These promising results constitute a step forward in the development of formal specifications for blockchain interoperability solutions.
The artefacts generated in this research were: The artefacts generated in this research were:
- An Event-B specification of the gateway-based interoperability solution proposed by [Pandolfi et al.](https://ieeexplore.ieee.org/document/10346168). This specification is composed of three machines: an abstract machine and two refinements. One refinement describes the behaviour of the gateway and smart contracts involved when the source blockchain is Ethereum and the target blockchain is Hyperledger Fabric. The second refinement describes the behaviour of the gateway and smart contracts when the source is Hyperledger Fabric and the target Ethereum. - [An Event-B specification](Gateway_Event_B_specification.pdf) of the gateway-based interoperability solution proposed by [Pandolfi et al.](https://ieeexplore.ieee.org/document/10346168). This specification is composed of three machines: an abstract machine and two refinements. One refinement describes the behaviour of the gateway and smart contracts involved when the source blockchain is Ethereum and the target blockchain is Hyperledger Fabric. The second refinement describes the behaviour of the gateway and smart contracts when the source is Hyperledger Fabric and the target Ethereum.
- Animations of the three specifications (i.e. abstract and refinements) that enabled us to validate the functional behaviour of the specification and provided the means to understand the gateways' behaviour without Event-B knowledge. - Animations of the three specifications (i.e. abstract and refinements) that enabled us to validate the functional behaviour of the specification and provided the means to understand the gateways' behaviour without Event-B knowledge.
- An Event-B specficiation of a use case scenario that shows the utility of the specification. - An Event-B specficiation of a use case scenario that shows the utility of the specification.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment