From a81e637907a9ae394562afcbf67f78a7426a099e Mon Sep 17 00:00:00 2001 From: Ladd Hoffman Date: Mon, 10 Jun 2024 11:29:09 -0500 Subject: [PATCH] sys design: Onboarding --- specification/docs/future-work.md | 3 +++ specification/docs/system-design.md | 6 ++++++ 2 files changed, 9 insertions(+) diff --git a/specification/docs/future-work.md b/specification/docs/future-work.md index 5b1cfe4..56a763a 100644 --- a/specification/docs/future-work.md +++ b/specification/docs/future-work.md @@ -12,3 +12,6 @@ The ratio of minted REP staked for and against a VP could be taken as a paramete ## Chat REP +## Multi-REP (Interacting DAOs) + +## Reviews \ No newline at end of file diff --git a/specification/docs/system-design.md b/specification/docs/system-design.md index daa1493..a6dca79 100644 --- a/specification/docs/system-design.md +++ b/specification/docs/system-design.md @@ -254,6 +254,12 @@ To achieve the Work Smart Contract requirements, a work contract must do the fol 1. Once approval/disapproval is submitted, either initiate a Validation Pool tarageting the WEV, or submit the fee and worker's REP stakes to the Rollup contract instead (explained below). +### Onboarding + +The process of adding a new Member to the DAO can be implemented as a Work contract. The Customer is a prospective Member. A work request is a request to be onboarded, and the assigned Worker is responsible for reviewing the onboarding request. + +The reviewer submits their review as work evidence. The Onboarding contract initiates a VP targeting this review, including a portion of the fee submitted with the onboarding request. If this VP is approved, then the Onboarding contract initiates a second VP, this time targeting the onboarding request, including the remainder of the fee. + ### Rollup Rather than submit every Post on-chain and conduct every Validation Pool on-chain, it is more efficient to keep a collection of Posts off-chain, and add a single Rollup Post on-chain representing multiple off-chain Posts.