private xain

Master-Branch:
Dev-Branch:

Structure

Run Xain in docker. We have three different docker images. xain_node for running a blockchain node. xain_contract_deployer for running the scenario simulation and xain_bootstrap for initializing the blockchain and interconnecting all xain_nodes.

xain_node files

1. blockchain_accounts are required for each blockchain node to start mining and participate in smart contracts. The XAIN implementation requires specific accounts which cannot be created by geth automatically. Therefore these accounts are fixed for each blockchain node
2. data_collection which sends the runtime data of the chain to a server.
3. scenario_slave which runs a websocket receiving transaction commands from the contract_deployer
4. scenario_execution_scripts which implements the xain specific execution of a transaction. They are connected with the scenario_slave
5. We are not allowed to upload the geth client to github. If you are interested in running the XAIN implementation, please contact us.

xain_contract_deployer files

1. data_collection which sends the runtime data of the chain to a server.
2. contract_migration which deploys the smart contract to run transaction with a specific payload. It also opens a websocket connection for retrieving the smart contract address, so the nodes are able to use the same smart contract instance.
3. master contains the main entry point to start the scenario-orchestration-service which listens for input from the private-chain-controller at port 22000.

xain_bootstrap files

1. blockchain genesis file which includes the genesis.json to initialize the blockchain

Docker Setup

All nodes use the same Dockerfile but have different entrypoints defined in the docker-compose.yml. To run the blockchain just start it by running docker-compose up. Please note that scaling is allowed only on the xain_node.