# Taz V2 - Collaboration Updates
## Jan 29 - Feb 10 Updates
### RPG
Progression was made mostly on the game, behind the scenes. We have a visual overview, but will focus on that in the following weeks.

## Jan 26-27 Updates
### RPG
#### Vision
- If the package we're creating is good, it can become a reference for game designers in general.
- When we have the package ready to be tested, we'll have a simple front end for ppl to experiment.
- Any user will be able to play around with the Verification Mechanism in a similar interface we present here, but according to the user's new stats.

#### Delivered
Our focus this week has been with the functionality rather than the visuals.
1. Verification Mechanism for Stats
- Question 1. How to pack so many stats with a visual representation?
We got to a reputation breakdown with several features, including proof submission for each stat. You could experiment with being able to prove that you have that reputation/stat.

- Question 2. How to reconstruct and generate the proof safely?
We want to have this as easy and modular; as plug and play as possible. We could provide data for proof construction: generate proof in our back end, without needing a user to build it.

2. RPG updates
- Every time you take a decision in the game (story or challenge), the story component will be rendered

3. OpenZep Relayers: how to make it easier for users to sign in
Solution 1: Account abstraction with 100% decentralized decisions. This is not production ready yet.
Solution 2: Autotasks. The idea is to have 1 function relayer per action. If you have a proof of membership, we can pay your transaction without knowing who you are. *User doesn't need to sign or pay for transaction.*

### Bot & Stats Page
#### Vision
A Community Application
- Community being able to collect and share data with ZK. Collect data from users in a secure way for the user's privacy
- Data example: age, location, language, birth location, etc
- Could develop into a new level of data analysis in web3
- New use cases for Semaphore:
A. You can get the analytics in a similar to google
B. You can implement NPS and test how happy participants are with your DAO, protocol or project
C. Measure how good an ecosystem is to contribute with
D. *Instead of SBT, use Reputation:* have stats systems for a community. You can distribute stats across the community. Use it as a sign in method (instead of google sign up)

#### Delivered

- You can ask not specialized questions about Unirep & Semaphore
- You can contribute with the fine tuning, as long as you have signed in with your wallet

## Jan 16-20 Updates
### Delivered
- Chapter 1 first draft with different outlines
- [About the Game HackMD](https://hackmd.io/@patzip/BJLkNDwij)
- UX first looks
- AI chat for Semaphore and Unirep protocols is in better shape

### To be worked on
- Deliver working game, Chapter 1 with Story and Challenges
- Implementation of story outline with Unirep and Semaphore

## Jan 9-13 Updates
### Decisions made
- We'll develop a writing choice-based RPG
- "Reputation" Unirep mechanism will be used to store data for each Stats. There's a limit of 32 stats with 0-255 points.

### To be worked on
- Chapter 1
- Game mechanics
- UX for challenges and game interactions (text, choices, character, stats, challenges, combat)
- Back end
- AI chat for Semaphore and Unirep protocols has documentation

## Jan 2-6 Updates

### Achieved
- Good fluency and understanding around documentation of Unirep and Semaphore

### General Discussion
- comparison between users and GPT answers, and the game is for users to guess which is correct; not super engaging.
- choose a beta use case
- propose Reputation in Study Groups. Reputation will be part of a positive cycle with several interaction opportunities; is a useful case.

- what we've understood about Unirep
- what game/ application will we create?

### Game/ App Discussion
- Have rounds and levels;
- Leaderboard: levels with enough points instead of showing how many points (keep reputation anon)
- Battlezip: is it useful for for developers to get familiarized with Unirep if they need to learn another layer? Perhaps we should find a new route (new game, new application)
- Instead of game, we could create a plugin
- Open Ideas
- art competition
- story telling together
- study group epochs based on shared research items
- discord integration
- engaging mechanic for voting: hot or not hot/ yes or no

### Open Questions
- can we have a larger epoch cycle? (Danilo)
- can we have multiple epochs running in parallel? Or tasks/ situations/ etc

### Goals

### for Wednesday, Jan 11th
- create a chatbot about Unirep and Semaphore
- propose changes in Unirep documentation
- Unirep implementation with step-by-step
- try all the repos for Semaphore

### for Thursday, Jan 12th
- show new documents;
- propose some game options;

#### for January 27th
Have a working game

#### for January 13th

1- Have a simple Unirep + Semaphore contract
2- Check and try a simple implementation between Semaphore, Unirep and Battle Zips
3- Build simple Npm package
4- Research Documentation templates and implement a few tests

#### for next Sync
- Have our own repository
- Have understood what we are doing (explore and play around with all related to unirep)

### About

#### Project
- [Grant proposal](https://hackmd.io/0p8dNI-DQdaQ4Ycn_JiOSg)
- Desktop version
- Documentation as a reference for similar implemetations
- High end
- ZK Knowledge, interesting to be used on

#### Team
- deliver fast
- make weekly and daily progress