---
# System prepended metadata

title: WarGames UH Federation Simulation - Checklist
tags: [WarGames]

---

---
###### tags: `WarGames`
---

# WarGames UH Federation Simulation - Checklist

#### Stage 1: Intro

- [x] Introduction lore/story
    - [x] needs to be performed by GM during first encounter
    - *Jeremy: could use a ticket bot for delivering private msgs to players*
    - UI369 + Jeremy will jam on this
- [x] Instructions on how to spin up a DAO and minion
    - [x] needs to be lorecrafted (if possible)
- [x] Distribute character sheet
    - [x] needs lorecrafting for distribution, elaborate character traits/details

Results:
- Players are introduced to set/setting of the game
- Players summon their DAO and minion
- Players choose their character

---

#### Stage 2: Onboarding

- [x] Extract info from character sheets:
    - [x] minion address for airdrop
    - [ ] eth address for POAP
    - [ ] needs lorecrafting to confirm receipt with players
    - *going to rename the races, align with the art that has been made*
- [x] Airdrop tokens to players
    - [x] instruct players to roll dice (is this what we are planning?)
    - [x] send tokens via a Disperse proposal
    - *let's figure out how to automate the gatehring of info, maybe the distribution of tokens, related to Jeremy+UI369 experimenting with bots?*
- [x] Instructions on how to Y33t in to the federate DAO
    - [x] needs to be lorecrafted (if possible)
- [ ] Invite players to game Discord server
- *write a welcome message to be manually distributed* Jeremy will jam
    - [ ] GM assigns them the proper roles
    - [ ] needs lorecrafting to introduce players to their character channels, provide orientation
*Do we want to experiment with onboarding bots here? Or other automated onboarding flows, token-gated access, Collab.land, etc? **Jeremy** and/or **Boilerrat**?*
- [ ] Invite players to Discourse forum
- *can also be accounted for in the onboarding flow, via the discord bot*
    - [ ] need instructions on how to introduce themselves - template?
    - [ ] instructions need lorecrafting
    - [ ] *Do we want to capture these posts somehow?*
- [ ] Distribute instructions on how to create proposals for the UH flow: forum > Snapshot > etc.
    - [x] need to write instructions - **Dekan**?
    - [x] instructions need lorecrafting
- [ ] Devise a way to elect or delegate an "operator"
    - [ ] carries forward snapshot proposal to become on-chain proposals
    - [ ] in Act 2, the operator would audit the code
    - [ ] in Act 3, they would perform house keeping on the stalled proposals

Results:
- Players know their character/faction, begin LARPing
- Players join the DAO-of-DAOs, are ready to play
- Players find their appropriate coms channels, ready to chat

---

#### Stage 3: Game Begins
In this particular simulation there will be **two games running in parallel at the same time**. (We might also continue to develop additional parallel scenarios to add on, so long as we are clear on what we are testing and how the value will be captured.)

##### Game 1, Act 1: Proposal Flow

- One player is chosen to execute a proposal spam attack. Spam attack could happen with the Snapshot, or with the DAO proposal flow. Other players will defend, retaliate, or otherwise respond. Results are tested against our hypothesized solution: *Mandatory rule to make an offering with each proposal submitted. Different from paying tribute (where the funds are sent after the proposal passes, instead of before).*

##### Game 1, Act 2: Misleading Minion Proposal

- One player is chosen to insert malicious code into a minion proposal. Other players are warned of this possibility and coordinate to spot the malicious "alien" and spot their attempt before it succeeds. Tested against our hypthesized solution: *delegated trusted proposal auditor to check every proposal.*

##### Game 1, Act 3: Unsponsored Proposals, No Votes, Never Executed

- One player is chosen to submit a shit-ton of proposals that will never be sponsored. The other vectors might be more difficult to test. Test against hypothesized solution: again, *a delegated auditor.*

##### Game 1, Act 4: All Out Chaos!

- Does the game devolve into capture the flag dynamics? How will we define success/failure? How will the game come to an end?

Needs:
- [ ] Instructions to chosen player on how to perform their role
    - [ ] needs lorecrafting
- [ ] Instructions to the rest of the players on what they might expect or prepare
    - [ ] needs lorecrafting
- [ ] Immersive lorecrafted story elements to announce each new act of the game
- [ ] Conclusion (or "to be continued") story to wrap up the game

---

##### Game 2, Act 1: Offensive Hacking

- Volunteer players attempt to white hat hack the DAO contracts via all means at their disposal.
- Lorecrafting describes this as taking over the protocol of the malicious AI and seizing control of the mothership (or whatever).

##### Game 2, Act 2: Defensive Hacking

- Volunteer players attempt to defend the DAO from the hackers, using all means at their disposal.
- Lorecrafting describes this as preventing the AI or other alien factions from reclaiming control of the mothership.

Ideas:
- Create a bounty board for trying to break the shaman?
- Espionage-style lorecrafting? Provides hints that empower people to hack the contracts.

Needs:
- [ ] Instructions for both kinds of hackers
    - [ ] lorecrafting to encode the instructions into "secret encrypted messages"
- [ ] Lorecrafting of periodic instructions (based on dice rolling?) to give hints on how the hackers might proceed
- [ ] Strategy/planning on how the hackers might operate differently in the Discord server