---
tags: RIPs
---

# Raid Skills v1

**to pair with the [Prototype](https://www.figma.com/file/g3dsXn35vTPry0KbdbYVE8/skill-forest-prototype?node-id=116%3A2) and [Skill Tokens](https://hackmd.io/Gq-sn7zBSnaitEVzw3lcQQ)**

## Skill Tokens Flow


## Proposal Process (Main flow)

1. Cleric completes initial skills proposal
- Save pending skill proposals to db
- Raids have a name and budget
- Skills points are derived from the budget 10:1


2. Raiders can add additional or change skills, if applicable, up until approved by the DAO.


3. The final raid skills proposal is submitted with total points to the DAO for approval usually some time after client makes deposit to escrow.

4. DAO votes to approve raid/rip for raid skills while the raid is running
5. On-chain endorsements, "vouches," can be added until the NFTs are minted. Endorsements will be recorded in the algorithm off-chain after minting once that infrastructure is ready.
- endorsements can be rescinded from the algorithm, but will persist on-chain
- off chain endorsements can be stored like snapshot votes on IPFS
- individual raiders can be swapped up until mint, if roles & skills remain the same. new skill require dao approval

6. Near the conclusion of the project, raid party members assign the approved budget of points to the different skills across the members.
- not all points must be used
- not required to be evenly distributed, currently
8. Skills are minted some time after the release of the escrow/other payment releases.
- head over to [Skill Tokens](https://hackmd.io/Gq-sn7zBSnaitEVzw3lcQQ) to see how this'll work
- TL:DR; 1 NFT per role per project

## Stories

### Roles
- cleric: not necessarily a cleric, but the member who initiates the proposal and will have responsibility to fairly distribute, if approved by raiders
> @lucas: maybe choose another word for this role. Messenger? Scout is cool but I dunno if it conflicts with open badges or other naming systems.
- raider: user that has agreed to participate in a raid or rip, acting as one or more roles (eg: Wizard).
> @lucas: since we also do rips, the name could be something less specific such as buidler. Also, should becoming a raider be restricted to members?
- member: users who are official DAO members
- user: any human (or DAO/squad?) that owns an eth address

### Create Proposal

- As a member, I can create a new skill proposal and add roles and skills for the project (then becoming its cleric)
- As a member, I can update a role for a specific "position" in the skill proposal
- As a member, I can add/remove existing skills for a role
- As a member (or raider), I can propose the inclusion of a new skill associated with one of my roles.
- As a member, I can assign a user to a role (user becomes raider)
- As a member, I can remove a role from a skill proposal
- As a member, I can set the budget for a skill proposal project
- As the system, I will compute the skill points when a proposal budget is provided

### Update Proposal

- As a raider, I can change my roles and skills
- As a cleric, I can change any role or skill
- As a cleric, I can update the budget for a skill proposal project
- As a cleric, I can submit the skill proposal to the dao for voting

### Vouching (Endorsements)

- As a member, I can vouch for other raider's roles (and those skills associated and weighed in the raid) before minting and it will be included in the NFT
- As a member, I can vouch for other raider's roles (and those skills associated) after minting and it will be recorded on IPFS and incorporated into the Forest algorithm
- As a member, I can rescind a vouch for other raiders role which is stored on IPFS

### Voting (Approval)

- As a DAO member, I can vote for or against on a skills proposal
- New skills, not currently in the skill inventory, will be added as newly available skills for future proposals.
- As a raid party member, I can trigger a new proposal vote for a skills proposal that incorporates new skills (not previously voted on)

### Skill Points

- As a raid party member, I can assign points to the different raiders up to the total budget
- the first version will be unanimous consent, where the raid party will agree on the points distribution. a future version could do quadratic voted distribution or consider other schemes like sourcecred
- As a raid party member, I can update the point allocations to raid members within the budget

### Minting

- As a raid party member, I can mint skills tokens after escrow has been released and with DAO approval

### Relevance Score

When vouching for raiders, it's possible that not all vouches are equal. The relevance of a vouch should be based on how relevant the member vouching is to the raider. Here are some ways we can create a relevance score:

* A member with more vouches is more relevant in vouching other raiders (similar to the PageRank algorithm).
* Has the vouching member gone on a raid with the raider he is vouching for? If yes, his vouch has a higher relevance score.
* A developer vouching for a devopler is more relevant than a cleric or PM vouching for a developer (and vice versa). The roles of the vouching member and raider matter. If the roles are the same, the vouch is more relevant than if the roles are different.
* Add in more thoughts & ideas...