Skip to content

Verifier Dashboard #10

@1nonlypiece

Description

@1nonlypiece

Description
Design a dedicated dashboard for users in the Verifier role. Verifiers are responsible for validating milestones and determining whether conditions have been met for fund release.

Target Users

  • Assigned verifiers for vaults
  • Third-party validators
  • Organizational approvers

Design Requirements

Must Include:

  • Verifier Overview:
    • Total vaults assigned for verification
    • Pending validations count
    • Completed validations count
    • Recent activity
  • Pending Validations Queue:
    • List of vaults awaiting verification
    • Vault owner information
    • Amount at stake
    • Deadline urgency indicator
    • Days remaining
    • Quick action (Review)
  • Validation Detail View:
    • Vault summary
    • Milestone(s) to validate
    • Submitted evidence/proof
    • Success criteria reminder
    • Historical context (previous milestones)
  • Validation Actions:
    • Approve milestone (success)
    • Reject milestone (failure)
    • Request more information
    • Add verification notes
    • Signature/confirmation step
  • Validation History:
    • Past validations performed
    • Approve/reject ratio
    • Verification notes
    • Timeline of actions

Should Include:

  • Bulk validation (for multiple milestones)
  • Dispute handling interface
  • Communication with vault owner
  • Verification templates
  • Calendar view of deadlines
  • Notification preferences

Design Specifications

  • Queue list: Sortable by urgency, date, amount
  • Evidence review: Support images, documents, links
  • Actions: Distinct buttons, confirmation dialogs
  • Mobile: Support on-the-go verification

Deliverables

  • Verifier dashboard overview
  • Pending validations queue
  • Validation detail/review screen
  • Approval flow with confirmation
  • Rejection flow with reason input
  • Validation history
  • Mobile responsive versions

Designer Notes

  • Verifiers hold significant responsibility—make consequences clear
  • Evidence review should be easy and thorough
  • Prevent accidental approvals/rejections (confirmations)
  • Show what happens after validation (fund release/redirect)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions