Update README.md

Author: ghareeb-falazi

README.md

@@ -1,7 +1,9 @@
-# Blockchain Access Layer
+# Blockchain Access Layer (BAL)
+
 The project is a Java 8 web application that uses Jersey to expose a RESTful API.
 
 ## Configuration
+
 The blockchain access layer needs to be able to communicate with a [geth node](https://github.com/ethereum/go-ethereum)
 which has RPC connections enabled.
 Furthermore, the layer directly accesses the keystore file holding the private key of an Ethereum account used for sending
@@ -14,6 +16,7 @@ The configuration file that can be used to configure these aspects (communicatio
 
 
 ## Building and Deployment
+
 After cloning, you can build the project and package it into a WAR
 file using the following command:
 ```
@@ -28,6 +31,7 @@ of the Bitcoin Core node. However, the used library is not available in a public
 a local Maven repository which includes the required binaries. This repository is found [here](local-maven-repo).
 
 ## Accessing the API
+
 The application exposes an asynchronous RESTful API to subscribe and unsubscribe from the provided operations.
 
 **To summarize:**
@@ -59,6 +63,7 @@ paths to manually delete the corresponding subscription:
 ```
 
 ## Running a Local geth Node
+
 A geth node is used to access the Ethereum network. For development purposes, it is advised
 not to connect to the main Ethereum network, but rather to one of the testnets.
 (another, more difficult option would be to run a local private Ethereum network).
@@ -84,6 +89,7 @@ To start a geth node in the fast-sync mode, execute the following command:
 please replace _localhost_ with the ip address of the computer running the node.
 
 ## Running a Local Bitcoin Core Node
+
 A Bitcoin Core node (or _bitcoind_ node) is used to access the Bitcoin network. For development purposes, it is advised
 not to connect to the main Bitcoin network, but rather to one of the testnets.
 (another, more difficult option would be to run a local private Bitcoin network).
@@ -103,10 +109,13 @@ connection, and the availability of peers).
 ```
 bitcoin-cli -getinfo -rpcconnect=<ip address of the node> -rpcport=<port of the node> -rpcuser=<rpc username> -rpcpassword=<rpc password>
 ```
+
 ## Setting-up a Hyperledger Fabric Network
+
 Please follow these steps [Fabric Setup](https://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html)
 
 ### Note
+
 The included Fabric unit test depends on the [FabCar official example](https://hyperledger-fabric.readthedocs.io/en/release-1.4/write_first_app.html), so in order to run it
 ensure the following:
 
@@ -122,6 +131,7 @@ ensure the following:
    This ensures that the SDK is able to find the orderer and network peers.
 
 ## Case Study (For BlockME)
+
 The case study invloves a cryptocurrency exchange service utilitzing the blockchain access layer.
 The exchange uses the following simplified BlockME-model:
 
@@ -166,7 +176,12 @@ You can find the details about the resulting testnet3 Bitcoin transaction [here]
 * a _geth_ node is running on a virtual machine in a VSphere accessible from the local network.
 * a _bitcoind_ (Bitcoin Core) node is running on a virtual machine in a VSphere accessible from the local network.
 * The blockchain access layer is running in a local Tomcat server listening to port 8081
-* The camunda engine is running in a local Tomcat server litening to port 8080
+* The camunda engine is running in a local Tomcat server listening to port 8080
+
+## BAL as a Smart Contract Invocation Protocol (SCIP) Gateway
+
+The BAL provides a JSON-RPC API as a prototypical implementation of the [SCIP protocol](https://github.com/lampajr/scip) playing the role of a SCIP gateway.
+
+### SCIP Case Study
 
-## Case Study (For BlockME2)
-Detailed case study for BlockME2 coming soon!
+A case study that demonstrates the usage of the BAL as a SCIP gateway [can be found here](https://github.com/ghareeb-falazi/SCIP-CaseStudy).