mTasks now uses SteemConnect for Escrow

mTasks previously used Steem-js escrow features which requires user to submit active private key to perform various escrow transfer, approve, release, dispute. It was helpful for the developer as we can check if the transaction was successful and perform various other required action on callbacks. But it is not safe for user as they need to trust an unknown party with their private key.

@fabien and @gregory.latinier was kind enough fix the issues with SteemConnect escrow transactions. Now we can use it to safely redirect users to SteemConnect and check their account history to validate transactions.

What is New

1. Service ordering is now done through SteemConnect. User will broadcast escrow transfer through SteemConnect and comeback to the site. Site will validate, update database, and redirect user to dashboard. GitHub PR.

2. Approval, disapproval, dispute, and release of transaction for both seller and buyer also use SteemConnect. PR.

3. Previously mentioned user actions and order status are validated and synced with the blockchain. PR.

4. Various other fixes and code improvements to support these changes. PR.

Limitation

• For now SteemConnect doesn't allow escrow initiator to release escrowed payment. I am in talk with them. I hope they will fix this.

In Development

• Dispute management for agent is in development. Agent now can release the escrowed payment but I am planning to add partial payment and a negotiation portal.
• An updated buyer and seller profile

To Do

• A good looking user interface
• Lot of validation rules are yet to add
• A better user and order management