demo

Sharing Updatable Models (SUM) on Blockchain Demo

(formerly Decentralized & Collaborative AI on Blockchain Demo)

A dashboard and examples for deploying updatable AI models to Ethereum. A video demo is available There is a video example showing how to deploy here.

This folder also contains Solidity examples for models, data handlers, and incentive mechanisms for deploying models that are free to use for inference as initially proposed in our introductory paper.

This project is made from a React project with Truffle added. This Truffle example was used to help add Truffle.

This work in its current form is just meant as an example and proof of concept. It is not ready to be deployed for production yet.

Setup

This section explains how to set up locally on Linux/WSL, alternatively, you can skip ahead and use a Docker image.

The following steps are made for Linux/WSL and require npm with node version 10. Other later versions of node might work too but some node-gyp issues occurred with version 14.

You will need to have make installed. On Debian (e.g. Ubuntu) you can do:

sudo apt install build-essential

Run

./setup.sh

Troubleshooting Setup

If you have problems running the setup steps related to node-gyp, then you might need to set Python 2.7 to be your default (just during the installation). Recommendation: Temporarily set up a Python 2.7 Conda environment (just for the installation) and activate it:

conda create --name python2 python=2
conda activate python2

Docker Setup

1. Clone this repo.

2. Navigate into the folder containing this README.md file:

cd 0xDeCA10B/demo

3. You can use a Docker image by running:

docker run --rm -it -p 3000:3000 -p 5387:5387 -p 7545:7545 -v ${PWD}:/root/workspace/demo -v /root/workspace/demo/node_modules -v /root/workspace/demo/client/node_modules --name decai-demo mcr.microsoft.com/samples/blockchain-ai/0xdeca10b-demo bash

# If this is your first time setting up then run:
./setup_libs.sh

# So that you can start a few processes in the Docker container, run:
byobu

4. You have completed the setup steps. Next, refer to the Deploy steps lower down on this page.

If you want to use a different version of the Docker image, then you can find the available tags for the Docker image here and check the details for the latest tag here.

Building the Docker Image

(Optional) If you want to build your own fresh image:

docker build -t decai-demo .

(Microsoft Devs) Updating the Public Image

First get permission to push 0xdeca10bcontainerreg.azurecr.io.

Then

docker login 0xdeca10bcontainerreg.azurecr.io
newVersion=<Set the new version. E.g. 1.2.0>
docker tag decai-demo 0xdeca10bcontainerreg.azurecr.io/public/samples/blockchain-ai/0xdeca10b-demo:${newVersion}
docker tag decai-demo 0xdeca10bcontainerreg.azurecr.io/public/samples/blockchain-ai/0xdeca10b-demo:latest
docker push 0xdeca10bcontainerreg.azurecr.io/public/samples/blockchain-ai/0xdeca10b-demo:${newVersion}
docker push 0xdeca10bcontainerreg.azurecr.io/public/samples/blockchain-ai/0xdeca10b-demo:latest

(Microsoft Devs) To update the production website, see the instructions at the top of service.Dockerfile.

Update

To update dependencies after already setting up:

./setup.sh

Deploy

There is a video example showing how to deploy here.

Blockchain

Models and data are stored on a local blockchain.

Start the blockchain (uses ganache-cli) in one terminal. Run:

yarn blockchain

Do once:

• In your browser, you will need to add http://localhost:7545 as a custom RPC, you can use the MetaMask extension for this.
  • If required, you can set the chain ID to: 0xDeCA10B
• Copy the first private key output by the above command.
• Use that private key to create a new account in MetaMask.

Server

(Optional) The server is used to store model meta-data and original data when for training models.

The server is used by default in development mode but not in production mode.

If you want to store meta-data in a local database file instead of just within the browser, then start the server in one terminal. This step allows you to see models listed when you open the dashboard for the first time.

If you do want to use the database file then you should have REACT_APP_ENABLE_SERVICE_DATA_STORE=true in your client/.env.development file.

Run:

yarn server

Client

The website is the "client", it allows you to interract with the blockchain and optional server.

In another terminal. Run:

yarn client

Troubleshooting Deployment

Blockchain Issues

Run yarn clean to delete your local blockchain and cached contracts. This will delete any transactions done but should make everything work again.

Errors about a contract not found at a certain address

If you get errors about calling a contract then it's probably because you restarted your blockchain (Ganache) and the contract doesn't exist anymore on the blockchain. This could happen if you restarted your computer. You have to delete the generated .json files that keep track of contract addresses:

rm -f client/{build,src}/contracts/compiled/*.json

Then you should be able to deploy normally.

You can also try to rm -rf blockchain_db to delete your blockchain and restart from scratch.

MetaMask Issues

Issues about nonce

If MetaMask gives issues about the nonce not being right for a transaction then it's probably because you restarted your blockchain but MetaMask caches some basic things on the URL and the network ID.

You can first try to reset your account in the MetaMask settings. This will clear your transaction history.

You shouldn't need to if you've been consistently using a blockchain for just this project but you can also try changing the network ID for Ganache. This can be done in the Ganache UI or CLI (--networkId).

MetaMask Loading Issues

If MetaMask is spinning and non-responsive:

1. Disable the extension here: chrome://extensions
2. Re-enable the extension.
3. Open the extension.
4. Change the network to use. E.g. Select Main Ethereum Network.
5. Log in to MetaMask.
6. Change the network back to the custom one.
7. Reject any queued transactions.

If you get the spinning issue again, then also try following the steps above with resetting your account as well as restarting the blockchain by:

1. Stop the yarn blockchain process.
2. Run yarn clean.
3. Run yarn blockchain.

Testing

To run all automated tests:

yarn test

A local blockchain will be started and stopped so it's best not to have a blockchain running at the same address and port (e.g. one running through yarn blockchain).

Manual Testing

Not all tests are automated (yet, maybe one we'll automate them all). Some things that should be manually tested in the UI after completing the deployment:

• Pick a model
• PREDICT: Verify that you can use the model to classify some data
• TRAIN: Add "incorrect" data as user "Bad"
• Add "correct" data as user "Good"
• REFUND: Verify that "Good" can get a refund for the "correct" data
• REWARD: Verify that "Good" can report "Bad"'s "incorrect" data
• Add a new model

Running Specific Tests

To run specific smart contract tests and save time by not waiting for Truffle migrations:

• In one terminal, start a blockchain: yarn blockchain
• In another terminal session, run:

cd client
npx truffle test [<test file paths>] --network skipMigrations
# For example:
npx truffle test test/contracts/*.js test/contracts/**/*.js --network skipMigrations

Linting

Run yarn lint.

Run yarn lint-fix to automatically resolve some issues.

Solidity Files

We use Ethlint for linting and enforce it on pull requests. The above yarn lint and yarn lint-fix commands will also check Solidity files.