# Can we use RAID to facilitate strong commitment to Raids and RIPs?

## Background
- Some (but not many) explicit commitment failures in previous Raids. A couple instances where key people left a raid unexpectedly.
- Clerics and Monks would feel more confident in setting up raids and negotiating with clients on budget and timing if they could be more confident about the commitment of the Raiders they’ve found to work on the Raid
- There may be more issues with Raider commitment the larger we grow
- Generally, we want to test and establish ways to give Raiders rewards for completing Raids (including reputationally)

## Purpose
- Scalability of Raid and RIP Party formation (in terms of data about availability, and consistency of commitment)
- Secondary: Increase in RAID token price, via additional utility and demand for RAID token

## MVP
**Stake to commit to a Raid (or RIP), get slashed if you don’t complete the Raid.**

Benefits include:
- Increases the threshold for committing to a Raid
- Raiders will communicate better and prioritize optionality less
- Clerics can trust commitments more
- Increases friction for leaving a Raid early (loss aversion)

### v1 [OUTDATED, FOR LATEST: SEE v3 AT THE BOTTOM OF DOC]
1. Cleric is forming a team (before client is signed), makes initial availability request to Raider
2. Raider signals interest and availability with Stake 1
3.
a. Cleric does not need Raider, Raider receives Stake 1 back in full
b. Cleric needs Raider, but Raider is unavailable, has Stake 1 slashed
c. Cleric is ready to sign the client, confirms Raider for Raid party
4. Raider signals commitment to full extent of Raid (as outlined in SOW) with Stake 2
5.
a. Raider completes Raid, receives Stake 2 back in full + Reputational reward
b. Raider does not complete Raid, has Stake 2 slashed

### Potential subsequent adjustments:
- In addition to reward after Stake 2, provide a Reputational reward for Raider after Stake 1 (in 3a or 3c)
- Adjust the amount slashed from Stake 2 (in 5b) on a % basis relative to how much of the Raid they completed (i.e. missing 1 week at the end of the
is different from bailing after the first week of a Raid -> adds leniency)
- Allocate some or all of a Raider's slashed Stake 2 (in 5b) to the other Raiders in the party (like Kickback)
- or use slashed Stake 2 to create a bounty to fill the role with urgency
- Staking is optional, but Raiders who choose not to stake have lower priority with Cleric relative to other Raiders, and do not receive reputational reward for staking
- Add RAID economic reward to successful Stakes
- Where does the funding come from? If Staking is optional, one way is to allocate some % of total loot from a Raid as a Staking reward. If it’s a dedicated pool / vault, how does that vault get refilled?

### Possible values:
- Stake 1 = 5% of expected loot from raid
- Stake 2 = 15% of expected loot from raid
- e.g. Raid = 200k RAID and Raider 1 projected to receive 40k RAID, then Stake 1 = 2k RAID and Stake 2 = 6k RAID (approx. $10k; $2k, $100, $300)
- (Another way to think of this is essentially staking for membership in the subDAO that is the Raid Party - but the stake is not ragequit-able)
- Reputational Reward = Voting Power (X shares) + 1 “Gear” NFT (see [Brainstorming on "Gear"](/vOTeVSlpQICHoQtqMOT6-w))

### Questions:
- My understanding from previous services orgs is that Clerics need multiple stages of commitment. Hence Stake 1 and Stake 2. Is this true currently in RG? or is this true *eventually* in RG?
- If a Raider completes part of a Raid then bails, do they receive compensation for the work they did?
- Is there an existing accountability / reputation system to plug into here? Or are these types of commitments worthy of their own system? (e.g. Gear)
- Technically, should this staking be done via a “Commitment Minion,” similar to the Championing proposal?

# Can we use RAID for bandwidth / availability signaling?
First pass solution: in addition to Stake 1 and Stake 2 above, add a Stake 0 for having availability up-to-date. This is a natural extension of using RAID for commitments to Raids, above.

1. Cleric is forming a team before client is signed, makes initial availability request to Raider
2.
a. Raider’s availability is correct, receives Reputational reward
b. Raider’s availability is not updated, has Stake 0 slashed by some %
3. Raider updates availability and re-stakes full amount for Stake 0
4. Proceed from Step 2. in the Raid Commitments flow above

> [name=spengrah]
> I wonder if a 2 token system might work well here. For example, you have to stake $RAID in order to receive $bandwidth tokens...
> - the amount of $bandwidth tokens you receive are a (sublinear?) function of the amount of $RAID you stake, with the maximum you can hold representing full bandwidth (eg approximately full time work)
> - the more $RAID you have, the more $bandwidth you can receive and therefore the more raids and rips you can participate in (here $RAID is acting as a proxy for experience / reputation)
> - $bandwidth can be redeemed for the appropriate amount of $RAID
> - you can stake $bandwidth tokens as a commitment to join a given raid or RIP (as described in the previous section), with the required $bandwidth stake correlated to the raider's expected time commitment to the project
> - so the amount of $bandwidth tokens you hold that are not staked on raids or rips represents your availability that you wan to find work for
> - completing a raid or rip returns your $bandwidth tokens
> - failing to complete a raid or rip burns your $bandwidth tokens, which means you lose a claim on some amount of your staked $RAID
> - success rewards are paid out in $RAID

$bandwidth meme-ified name ideas:
- $quest-points
- $flasks
- $LFG
- $lockout
- $motes
- $allegiance
- $call-to-arms
- $swords
- $steel
- $mana

---

### v2:
- Acquire $allegiance
- Stake RAID, receive $allegiance (250:1 --> i.e. 40hrs/week = ~$500 XDAI)
- Intent is to acquire an amount of $allegiance that represents the amount of work you want to do (1 $allegiance per 1hr/week of work you're available for)
- Stake 0:
- Stake up to 100% of your $allegiance to signal your open availability for Raids
- Clerics use this to determine your availability when negotiating with clients
- Get slashed if your open availability is incorrect
- Stake 1:
- Cleric asks you to be on a Raid in process of being signed
- Unstake from availability contract (Stake 0) and re-stake $allegiance to this project
- Stake 25% of the hours you would need to commit to that Raid
- Get slashed if you are needed but can't participate
- Stake 2:
- Cleric adds you to a project team that is signed
- Unstake from availability contract (Stake 0) and re-stake $allegiance to this project
- Stake 100% of the hours you would need to commit to that Raid
- Get slashed if you don't finish the Raid (slash amount may change based on how much of the Raid that you complete)
- Reward
- Economic: Receive additional RAID when completing a Raid, relative to how much $allegiance you staked
- Governance Power: Receive DAO Shares for completing a Raid
- Reputation: (?)
- [I think there's an opportunity to add reputational rewards here. $experience (non-tradeable), Gear NFT, something like this]
- Perhaps maximum $allegiance you can hold (by staking RAID) is capped by your reputation (amount of $experience, or what not)

#### Notes from Call with Tae (Cleric)
- Standard approaches for assigning Raiders to Raids:
- Interal Thursday meeting, talk about Raids
- Raider Roundup call on Tuesday - who is on what Raids, current status, what's going on, Clerics can pitch Raids to get RAiders interested
- Blast channels and @roles to fill specific roles
- Works about 10% of the time
- Be very proactive as a Cleric (most common)
- Know who is good at what and would be a great fit (skills) -> improves with work history with the Raiders
- Knowing the requirements of a Raid from client
- Get people into the working funnel:
- Reason we do the Cohort is to build trust with people, begin to build work history (especially if people are psuedonymous)
- People also claim to have many years of experience outside of web3, do quick calls with them to verify
- Back and forth with a Raider:
- Usually jump on a call
- Get a sense if they are available
- Have to know that they can do the job, availability is on them
- Availability can be harder for new people. Giving people a chance to prove themselves / build reputation. People care because they are trying to break into web3
- Sometimes people have BSed their experience -> this is the main problem, not availability
- New Raid happy path
- Consultation, get a sense of what client is looking for
- Either: Client has clarity on what they need and specific deliverables -> easy to understand what roles are needed
- or: Client has an idea, then have to figure out exactly what they need
- Have a follow-up call
- Do a design sprint to fully scope it
- Or do a technical sprint to evaluate it ["discovery"]
- Sometimes, client doesn't understand scope, Tae has to say it maybe will take 140k and 6 months -> can we do an MVP instead?
- Review of v2
- Tae likes Stake 2 a lot
- Stake 0
- Stake 1 not necessary - start simply
- What's the reward?
- RAID + Reputation
- Possibly to incorporate Skill Trees?
- May be a case study out there that's doing this well (Andrej design firm called "deep work studio")
- Start simply, getting buy-in from folks will be one of the hardest parts
- If the sell is "makes us more efficient as we scale"

---

### v3 - Discussed at Token Talk 10/21
1. **Acquire $allegiance to signal availability**
- *Stake RAID, receive $allegiance* [process for this is biggest question]
- Possible value: 250 RAID = 1 $allegiance (i.e. 40hrs/week = ~$500 XDAI)
- Variable exchange rate, to (de)incentivize hours when needed?
- Acquire an amount of $allegiance that represents the amount of work you want to do
- Possible value: 1 $allegiance per 1hr/week of work you're available for
- Perhaps hours per period
- Hours may be hard to estimate
- Could we cap $allegiance you can hold based on DAO shares (as a proxy for reputation)?
- Clerics use this to determine your availability when negotiating with clients
- Get slashed if your open availability is incorrect?
2. **Stake $allegiance to signal commitment**
- Cleric adds you to a Raid
- Stake $allegiance to cover the hours you are committing to that Raid
- Get slashed if you don't / can't complete the work you took on for the Raid
- Slash amount may change based on how much of the Raid that you complete
3. **Receive reward for completed commitments**
- Get your $allegiance back
- Receive RAID as bonus reward when completing a Raid, relative to how much $allegiance you staked
- and for what time period?
- or based on how much you earned?
- or blend with grading by your peers
- Alt: "Raid Party Mining" / "Shipping Farm" -> "Outcome Coalitions"
- Possible addition of member-funded pool of additional rewards

---

### v4
1. **Acquire $allegiance to signal availability**
- Stake RAID to receive an amount of $allegiance that represents the amount of work you want to do
- Only mintable by DAO members
- Possible values:
- 1 $allegiance per 1hr/week of work you're available for
- Mint a maximum of 40 $allegiance
- Stake 250 RAID = mint 1 $allegiance (i.e. 40hrs/week = ~$500 XDAI)
- Clerics use this to determine your availability when negotiating with clients
2. **Stake $allegiance to signal commitment**
- Cleric adds you to a Raid
- Stake $allegiance in a Raid-specific contract to cover the hours you are committing to that Raid
- Get slashed if you don't / can't complete the work you took on for the Raid
- Slash amount may change based on how much of the Raid that you complete
- Slash is voted on by other members of the Raid Party and Cleric
3. **Receive reward for completed commitments**
- Upon Raid completion:
- Get your $allegiance back
- Receive RAID as bonus reward, relative to how much $allegiance you stake for what time period
- Possible value: 25 RAID per $allegiance per week staked (i.e. 40hrs/week = ~$50 XDAI/week bonus)

---

### v4.1 -> MVP
**Commitment Process:**
1. Raid party opts-in to doing commitment stakes
2. Create a Raid-specific DAO or multisig, if one doesn't already exist
3. Connect Raid-specific DAO to commitment Safe Minion
4. Each raider signals commitment by staking RAID on the commitment contract
- Stake approximately ~5% of the total earnings you are expecting
5. Upon raid completion, Raid-specific DAO requests RAID from Guild reward pool for bonuses
6. Each raider submits a withdraw proposal to the Raid-specific DAO for their initial stake + bonus
- Proposals are manually approved by vote of the Raid-specific DAO
- "Slashing" just means that the staker's withdraw proposal is rejected by the DAO (similar to Championing process)
- Bonus formula = double your stake OR 5% of the total earnings you received from the raid, whichever is less

*Note:* this leaves out the Availability tracking component for the MVP. The reason for this is that we need to have guild-wide adoption on commitments, and this will come after the MVP.

**TODO:**
- Request pool of RAID for MVP and RIP work
- Write commitment Safe Minion / staking smart contract

**Key knobs we can set for the final implementation:**
- Staking amount [*note:* talk to Scott & DamangedGoods on this -> had discussion and saw dungeon master progress, they are excited to integrate]
- Bonus
- Number of of active stakes over time (to get a sense number of commitments)
- Slashing events

---

# Availability-n-Commitments RIP Draft

## Background
- Some (but not many) explicit commitment failures in previous Raids. A couple instances where key people left a raid unexpectedly.
- Clerics and Monks would feel more confident in setting up raids and negotiating with clients on budget and timing if they could be more confident about the commitment of the Raiders they’ve found to work on the Raid
- There may be more issues with Raider commitment the larger we grow
- Generally, we want to test and establish ways to give Raiders rewards for completing Raids (including reputationally)

## Purpose
- Scalability of Raid and RIP Party formation (in terms of data about availability, and consistency of commitment)
- Secondary: Increase in RAID token price, via additional utility and demand for RAID token

## MVP
*Stake to commit to a Raid (or RIP), get slashed if you don’t complete the Raid.*

**Benefits include:**
- Increases the threshold for committing to a Raid
- Raiders will communicate better and prioritize optionality less
- Clerics can trust commitments more
- Increases friction for leaving a Raid early (loss aversion)

**MVP Process (v5):**
1. Raid party opts-in to doing commitment stakes
2. Raid party creates either:
a. A Moloch DAO with a raid-specific minion used for staking, or
b. A multisig
5. Each raider signals commitment by staking RAID on the commitment contract
- Stake approximately ~5% of the total earnings you are expecting
6. Upon raid completion, Raid party requests RAID from Guild reward pool to their DAO or multisig for bonuses
7. Each raider then submits a withdraw proposal to the Raid-specific DAO or multisig for their initial stake + bonus
- Proposals are manually approved by vote of the Raid party
- "Slashing" just means that the staker's withdraw proposal is rejected by the DAO (similar to Championing process)
- Reward formula = double your stake OR 5% of the total earnings you received from the raid, whichever is less

**Key knobs to modify and track:**
- Staking amount
- Bonus amount
- Number of of active stakes over time (to get a sense number of commitments)
- Number of slashing events