A proof of concept Blockchain project around Car Insurance.

To deploy to Bluemix:

1. Hit the button above.

2. Open the created pipeline, inspect the 'credentials' step & add missing environment property values.

   APIKEY=EDMUNDS API KEY (sign up for one), GCM_KEY=Google cloud messaging key for webpush.

3. Open 'deploy' and add a basic CF deploy job.

4. Run the pipeline from the start.

5. If errors occur, bind an instance of IBM's blockchain service to the application & restage.

We're building on the docker-compose from https://github.com/IBM-Blockchain/fabric-images.

See also these instructions for using a local hyperledger network.

To run a single node network using Docker Compose -

docker-compose -f docker-compose/single-peer-ca.yaml up -d

For a four node + CA network:

docker-compose -f four-peer-ca.yaml up -d

To test it is up and running properly hit http://localhost:7050/chain

Execute the following commands after running docker-compose (from the docker-compose folder)

docker cp membersrvc/membersrvc.yaml dockercompose_membersrvc_1:/opt/gopath/src/github.com/hyperledger/fabric/membersrvc
docker exec -i -t dockercompose_membersrvc_1 /bin/bash
rm -rf /var/hyperledger/production
exit
docker restart dockercompose_membersrvc_1
docker exec -i -t dockercompose_vp0_1 /bin/bash
rm -rf /var/hyperledger/production
exit
docker restart dockercompose_vp0_1

7 users will then be created:

claimant1
claimant2
garage1
garage2
insurer1
insurer2
superuser

In order for the correct username/role to be established within the chaincode (in dev mode), an attributes value has to be added to the REST request. Example:

curl -H "Content-Type: application/json" -X POST -d '{
     "jsonrpc": "2.0",
     "method": "query",
     "params": {
         "type": 1,
         "chaincodeID": {
             "name": "insurance"
         },
         "ctorMsg": {
             "function": "retrieveAllPolicies"
         },
         "secureContext": "claimant2",
				 "attributes": ["username","claimant2","role","policyholder"]
     },
     "id": 4
 }' http://localhost:7050/chaincode

To run chaincode locally without having to deploy from a github url:

1. Build your chaincode

go build ./

2. Register the chaincode with a peer

CORE_CHAINCODE_ID_NAME=insurance CORE_PEER_ADDRESS=0.0.0.0:7051 ./insurance_main

3. Send a REST request to enroll a user

POST: http://localhost:7050/registrar
{
  "enrollId": "bob",
  "enrollSecret": "NOE63pEQbL25"
}

4. Send a REST deploy request

POST: http://localhost:7050/chaincode
{
  "jsonrpc": "2.0",
  "method": "deploy",
  "params": {
    "type": 1,
    "chaincodeID":{
        "name": "insurance"
    },
    "ctorMsg": {
        "function":"init"
    },
    "secureContext": "bob"
  },
  "id": 1
}

5. The chaincode should now be deployed and ready to accept INVOKE or QUERY requests.

If you want to view your blockchian locally you can use the blockchain explorer.

To build the Docker image, run -

git clone https://github.com/hyperledger/blockchain-explorer.git
cd blockchain-explorer/explorer_1
docker build -t hyperledger/blockchain-explorer .

To run it first you will need to find out which network your hyperledger fabric peers are running on. To do this run:

docker network ls

Grab the Docker Compose network name and use it below:

docker run -p 9090:9090 -itd --network=dockercompose_default -e HYP_REST_ENDPOINT=http://vp0:7050 hyperledger/blockchain-explorer

The explorer should then be available on http://localhost:9090.

In order to use the car value oracle to obtain actual vehicle values from Edmunds you must:

1. Obtain an Edmunds api key and set the env variable. (Note: this step can be skipped, and the oracle service will then just callback with a hardcoded value.)

EDMUNDS_API_KEY

2. Deploy the chain code with an init argument specifying the host address of the oracle service (including port)

3. Configure the node app with the correct blockchain settings (in default.json).

4. Run the app.js node app

npm install
node app.js