FR: add validation and storage on blockchain of work history

[rngadam]

• Take existing data from timesheet and move it to blockchain after verification with customer.

[arseneeth]

I did some research on the issue, so in order to pass our data to Ethereum network we have to have several things: smart contract acting as a storage and "custom executer"- a program running a full ethereum node that would get data from the server and generate a transaction to the smart contract by request. Here is a schema:

I see steps as follows:

• [ ] write storage smart contract and deploy it to test network
• [ ] run geth on test network
• [ ] write web3js interface
• [ ] test transaction from web3js interface to storage SC
• [ ] connect interface to db
• [ ] query data from db and generate transaction to storage SC

(Maybe it would be needed to update the steps later on)

As for Skycoin blockchain, I've found some info on their website that they have programming language called CX, while I haven't found any tutorials or use cases online. However, they directly sell skycoins for ether on their website, so I suggest that they are familiar with Ethereum eco-system :)

[rngadam]

• have you had a look at https://github.com/coderbunker/skills-market first?
• some draft document here that might provide some context: https://docs.google.com/document/d/1TfWySRaYh9uObE3TzUfKxTIb1pSp5V_QVRIVlQjr7N8/edit\
• CX? do you mean https://www.c2cx.com? Actually used them to sell some bitcoin

if you mean the language:

https://github.com/breckinloggins/cx (NOTE: This project is currently "sleeping" - I'm too optimistic to call it dead) ?

[rngadam]

As for the question as to WHICH data to push to the blockchain:

I think generally we want to create a verified history.

Which means a month by month breakdown of the paid work per project with a:

• summarized tasks/keywords
• number of hours
• uuid of entities involved

Separately, we want a way to get approval (through the contract on the blockchain?):

• cryptographic signing by vendor, host, customer and person confirming this particular transaction.

I would suggest to create a new view in the database and play around with what we want to export (where every row would represent the data we want to have in a single transaction).

[rngadam]

As a separate avenue of research, I would be very curious to see how we can interact with blockchain based / distributed databases with a FDW wrapper in th PostgreSQL: https://wiki.postgresql.org/wiki/Foreign_data_wrappers