Profiles, Jobs & Disputes UI Description

This table gives a detailed description for each of the UI element related to Profiles, Jobs & Disputes. The UI should facilitate all the points mentioned in the Specification column. You can also directly look at the Figma Design to get a better visual idea.

Feature
Specification

Wallet Connectivity

  1. Connect Wallet using Metamask, Coinbase Wallet, Wallet Connect

  2. Allow Users to switch between Arbitrum, Ethereum, OpenWork Custom L2, XDC & any other L2s. Also, there will be other chains in the future so just note that.

User Profile Management

  1. Account for referral fees for both customer and talent [they should join by adding in the address that referred them or something that will work as per the system described on the paper]

  1. Set, View, and Edit profile details.

  • Profile picture

  • Username

  • First Name, Last Name

  • Description

  • Location

  • Languages

  • Email

  • Telegram Handle

  • Skills

    • A skill can be selected from a list of skills we have on a searchable dropdown

    • A skill can be verified by Athena [as long as it has that skill oracle active]

  • Hourly rate

  • Jobs done [only if done, not editable]

  • Rating [only if there, not editable]

  • Past Work Experience

    • Title

    • Image

    • Description

    • Skill related to

    • Package related to

Smart Contract-based Job Agreements

  • Initiation:

    • Initiate a job contract by accepting a job application and putting funds in escrow.

    • Initiate a job contract by entering job details, job taker address, and putting funds in escrow.

  • Add a work submission [work submissions be viewed and number of them made can be seen]

  • Funds are released by the job giver and job is complete

  • Rating [on 5] and review done by each side. Only the job giver can give a rating as of now

  • Job Giver raises dispute to skill oracle [can be general oracle] giving “reason”, “amount to be refunded back from escrow”.

  • Job Taker can raise a dispute to the skill oracle [can be general oracle] giving “reason”, “amount to be given to them from escrow”.

Job Posting & Application

  • Post a job with essential details.

    • Job title

    • Job requirement

    • Job skill

    • Location [optional]

    • Language [optional]

    • & Chain

    • Dispute resolution

    • [if available] Skill Oracle for that skill resolves disputes

    • [if skill oracle not available or user wants this] General oracle for dispute resolution.

  • Apply to an available job.

    • Application details

    • Proposed amount

Dispute Resolution

  • Skill oracle [including general oracle], can see tickets on ticket view, can be resolved as per UI.

  • Apply to become part of a SkillOracle by submitting an application field and being approved by the skill oracle or DAO.

  • Receive notifications for dispute resolution requests.

  • Review disputes and provide resolution [as per table view mentioned] .

  • Verify skill verification applications through majority wins mechanism [exact mechanism to be figured out]

OpenWork Ledger (OWL)

  • Initiated Job View: Display all jobs initiated in real-time.

    • Has filters: active, completed, job giver: address/username, job taker: address/username, before/after date & time & Chain

    • For each job Includes job giver, job taker, requirement, work submission details [unless private setting is on], amount promised, amount paid, amount still locked, rating, whether it used dispute resolution, if so what were the details of the dispute and result of the same & Chain.

  • Job Posting View:

    • Has filters: active, inactive, job giver: address/username, before/after date & time & Chain

    • For each job posting includes job giver, requirement, amount promised, skill needed & Chain

    • Add flow for connector as described in OpenWork- someone taking a fee of the job and recommending talent who is gone with.

  • User View:

    • Has filters: skills, verified skills, ratings, jobs done, languages, location, hourly rate, price of package, search by package [if it makes sense]

    • For each user includes <all fields under profile that fit>

  • Package View:

    • Has filters: skill, ratings, jobs done, price

    • For each package includes <all fields under package that fit>

  • Skill Oracle View:

    • Has filters: skill oracle, application view, user view, dispute ticket view

    • Application view:

      • Each row is an application to the skill oracle. It has username, application details, status: accepted/rejected/pending

    • User View:

      • Each row shows the members of each skill oracle, their contributing votes with reasons, earnings, current staked amount, times been with majority, times lost to majority.

    • Dispute Ticket View:

      • Each row shows the member who raised the ticket, is it job giver/taker, reason, amount, votes for, votes against, staked for, staked against, and an option to vote with stake [vote with stake].

Notifications

Receive alerts for job applications, messages, job completions, and dispute resolution requests.

Predefined service packages (to be executed in later phases)

  • Title

  • Package Price

  • Deliverables

  • Linkage to above Past Work Experience [this forms the image as well]

  • Skill linked to

  • When clicked, it allows anyone to enter a contract with the person directly for the amount and deliverables mentioned [This would use the direct contract entering route, without the application process].

  • Jobs done [if there are]

Communication (to be executed in later phases)

[to be decided if we use this or telegram handle for chat] Web3 direct message between job doer, job giver, and Skill Oracle within the context of a job or dispute. They can also just message each other when they want. (No direct way to contact inside the platform, but you can add your Email, telegram, Phone in the profile)

Last updated