Create Job / Task / Project

1. Authenticate
2. Navigate to Create Form
   1. Fields= TODO
      1. Type - Task / Job / Project
      2. Description
      3. First man gets the job / accept applications
      4. Compensation - released at end / released at each period (1w)
      5. Required Stake.
      6. Timeframe / Steps
         1. TODO: we need examples as much as possible
      7. Completion Criteria.
         1. All steps to be completed
3. Form Submitted
   1. Lock initial amount in contract (for 1st week ?)
   2. Job details get hosted on IPFS (immutable)
   3. IPFS link gets saved on-chain.

Stake & Start Work

1. Browse through a list of Jobs (with filters etc)
   1. Jobs stored in a Ceramic stream.
   2. UI queries jobs as a GraphQL request ?
2. Choose then Stake & Start
   1. Stake amount stored in contract (in jobs mapping struct)
3. First Step gets completed.
   1. UI for dev to "submit work"
   2. UI for provider to "review & verify"
4. Verified by provider
   1. 1st payment gets released & small state changes.
5. Final step gets completed
   1. Return stake.
   2. Send compensation.
   3. Get % for protocol (us).

Dispute Resolutions

At any step the Provider can decline the submitted work with feedback (gets recorded on ipfs).

1. TODO: research how to integrate Kleros.

Considerations:

• We might want to create a separate "Vault" contract with minimal logic that'll keep all the funds.
• Each time a new JobContract is finalized (aka dev gets accepted) we can deploy a new Smart Contract with the whole logic encapsulated inside.
  • Why ? → this way we'll give up the ownership & it will be truly trustless.
  • Too much gas ? → we can use CREATE2 op-code to pre-calculate the address and deploy only if the first step of the JobContract gets completed.