sys design: Onboarding
Gitea Actions Demo / Explore-Gitea-Actions (push) Failing after 34s
Details
Gitea Actions Demo / Explore-Gitea-Actions (push) Failing after 34s
Details
This commit is contained in:
parent
9375e8f0db
commit
a81e637907
|
@ -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
|
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue