Pocket-science/Labchain
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Norbert Schmidt
2022-01-08 07:54:43 +01:00
committed by GitHub
parent ce6c837e2e
commit 700b64bb71
1 changed files with 15 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@@ -2,7 +2,7 @@ This is the Labchain Open Sourced version.
Labchain offers a way to securely exchange health records (but other kinds of transactions are perfectly possible too) Labchain offers a way to securely exchange health records (but other kinds of transactions are perfectly possible too)
It runs on any ethereum-compatible network. It runs on any ethereum-compatible network. The original design ran on a Raspberry PI 3 with its own private Ethereum node.
It sends transactions with IPFS hashes using web3js from node to node. It sends transactions with IPFS hashes using web3js from node to node.
In this software two nodes are preconfigured. It sends a transaction to the other node with the ipfs hash for the encrypted In this software two nodes are preconfigured. It sends a transaction to the other node with the ipfs hash for the encrypted
@@ -17,8 +17,18 @@ Installation instructions:
Runs on any php enabled (linux) web server. Just drop the files in the /var/www/ directory Runs on any php enabled (linux) web server. Just drop the files in the /var/www/ directory
For secure exchange of files ipfs is needed and some ports have to be opened. Install via ipfs.io. For secure exchange of files ipfs is needed and some ports have to be opened. Install via ipfs.io.
For testing and creating accounts i use Geth command line (Go Ethereum)
For example:
geth --ropsten --syncmode "light" console --http
personal.newAccount("<YOUR PASS>")
Take the output and configure in app.js
Web3js is included, as well as Trezor login (not finalized yet). Web3js is included, as well as Trezor login (not finalized yet).
For this OS version we are using JS to push the hash from one node to the other. In the pro version (using Quorum infrastructure) a smart contract is used for interaction. Which is of course way safer and GDPR compliant.