Latest change for this feature branch

branch: token-transfer-ui

Note: truffle-config.js point to localhost network, to connect to the docker container with the private network, use the following network parameters:

Main component

This is a standard truffle project, the webapp directory contains a simple Web frontend realized with vanilla Web3.

This web frontend exposes the underlying smart contract methods for easy testing. The section Testing below is still valid, just does not require the usage of Remix.

blockchain-pm

Blockchain-based project management, focus on product and automate processes

Motivation

Project management involve too much burocracy, this project is an attempt to automate as much as possible the steps required to track project execution, including payment transaction and acceptance. Human work is focused on verification of deliverable's quality rather than keeping track of project metrics.

User Journey and main functionalities

The main idea is to define the scope of a Project, split it in Task and assign each Task to an Assignee and an Oracle. Assignee are experts assigned to execute the Task and generate the deliverables; Oracles are expert in the same domain, but responsible to describe, qualify and accept the deliverables.

The Project Owner creates the Project and assigns the project budget, by transfering test eth when calling contract constructor. Also, he creates the list of Tasks, defining for each of them the assigned Oracle and Assignee, compensation, deadlines and other properties.

Assignment is accepted by both by transfer of a small deposit. At this point, Assignee and Oracles agreed on the details of deliverables, deadlines and qualification procedure and the Task is moved to state accepted.

Once Assignee is done with his tasks and he believes the quality of deliverables is high enough for acceptance, Task is set to state resolved and Oracle is notified.

Oracle verifies the quality of the deliverables and eventually move the Task to state closed, releasing the task compensation for the Assignee.

In case of problems, like disagreement on deliverables or need to review Task budget or deadlines, the Task can be set to state on hold, and resolution with the Project Owner is triggered.

Once all the Tasks in the Project are closed, the whole Project is set as closed and all Task deliverables are qualified and eventually accepted by the Project Owner.

Testing

The easiest way to play with the contract is to use the Remix console at http://remix.ethereum.org. In particular, have a look about the Remix Editor quick start with Javascript VM https://remix.readthedocs.io/en/latest/quickstart_javascript_vm.html

Basically copy and paste the solidity code in this project in the Solidity Editor

compile and then deploy on a local simulation of the Ethereum Virtual Machine running locally (provided by Remix, very comfortable for quick tests). You can do that by selecting "JavaScript VM" as Environment in the Run tab of the Remix IDE.

This give you few default accounts with 100 test-ether. Different accounts can be used for roles of Project Owner, Oracle and Assignee to make the actual contract transactions. I usually take the first address as Project Owner, the second as Oracle and the third as Assignee.

Select the address that you want to use as Project Owner and set the value for the transaction, which will be the project budget. Press deploy button and confirm from the console message.

Now the contract is deployed and we can use Remix IDE to call methods method. Remember to set correct account and to set the amount when a transfer is required by the method.

The user journey above is described here in terms of contract calls:

Deploy the contract with a specific amount of test-eth as project budget.
With the same address, call addTask using the following parameters (you can add several Tasks):

    struct Task {
        int8 status;                // 0: new           3: closed
                                    // 1: accepted      4: cancelled
                                    // 2: resolved      5: onhold
        address oracle;             // has authority to change status
        address assignee;           // has accountability on task, can start Tasks
        uint deadlineAssignment;    // unix epoch timestamp of deadline
        uint deadlineDelivery;      // unix epoch timestamp of deadline
        uint compensationOracle;
        uint compensationAssignee;  // estimated compensation
        uint depositOracle;         // Oracle lock a deposit until task is completed
        uint depositAssignee;       // Assignee too
    }

And this is a compact form that you can copy and paste in the Remix method call, to make it faster. Remember to replace the addresses and the amounts. The timestamps for deadlines are set to end of 2019, so should work (depending by when you are reading this, check those in case of exception with addTask())

"1","20000000000000000","0x14723a09acff6d2a60dcdf7aa4aff308fddc160c","1574082855","1571404455","0x4b0897b0513fdc7c541b6d9d7e929c4e5364d2db","10000000000000000","20000000000000000","20000000000000000"