---
# System prepended metadata

title: "\U0001F346\U0001F351 FUX Notes"
tags: [' Brainstorm', "\U0001F346\U0001F351 FUXDAO"]

---

---
title: 🍆🍑 FUX Notes
tags: 🍆🍑 FUXDAO, Brainstorm
---
# 🍆🍑 FUX Notes 
## 03/14/2023
### Prep for DAO Camp
- @vengist Polish and build
- @bitbeckers fix ENS and graph??
- @SasquatchTru launch DAO and Docs
- Testing?
    - How to manage use at DAO Camp?
    - How to encourage use?
    - How to collect input?
    - 
### Review on UI updates
- 1,2,3
    - 1 >> CREATE WORKSTREAM
- Claim fux >> Hide if already claimed
- Evaluations broken
    - ENS issues
- 

## 02/09/2023
### ISSUE
+ undercommit to game their rVrA
    + EX: contributor commits artificially low (either to game score or to get into a workstream when holding low bandwidth)
    + Solution: Human
        + Coordinator has a sanity check at initial commitments (contibutor commits 1 FUX and has 10hrs/wk of work) 
        + Upon Evaluation stage reviewers can call out a disperate commit 2 value score ((What does this look like in practice??))
    + Solution: Staking
+ Contributor Management
    + EX: 

### UX REVIEW
#### 2nd Look with BB
+ move manage contributor button from "my workstreams" to "workstream detail"
+ Indicator on "My Workstream" for workstreams in which user is a 'coordinator'

#### w/ Ven and Sassy
+ Landing Page
    + high level what/why/how (infographic)
    + "get started" button to ???
        + "connect"
+ My Workstreams
    + Before CLAIM FUX: get rid of Fux available and view history
        + include quote below before FUX are claimed
    + Confetti moment with eggplants and peaches and middle fingers
    + Bring back the 1,2,3 or 
        + LATER: forced tutorial after FUX CLAIMED
    + "FIRST FORK"
        + Coordinator: sees "+ ADD WORKSTREAM" button
        + Contributor: See workstreams that they've been added to
            + N2H: way to hide workstreams that I'm not interested in
+ Add Workstream modal
    + TOOL TIP on Deadline; estimated time of delivery for workstream
        + POINT FOR ASKING USERS
    + Advanced option expander
        + nestle the Fund Workstream below 
            + TOOL TIP: Funds applied to workstream will be automatically distributed based on peer evaluations (aka vFUX)
        + fjor linking to Scope or information on workstream
    + ADD "add contributors" within the modal
        + N2H: list of remembered addresses, stared addresses, 
+ My Workstreams
    + HIGHLIGHT on Hover for Workstream Detail
    + chance actions into context menu (...)
+ Contributor Modal
    + change dd additional field is in the next line 
    + ENS Resolve and include avatar
    + close modal on submit and loader for 'sign txn'
+ Update FUX Modal 
    + close modal on submit and loader for 'sign txn'
+ BUG: adding contributors is broken
    + added 2 contributors and only my address was shown
+ Workstream Detail Page
    + Enable evaluations on the same page, the contributor array
+ Workstream History page
    + DATA
        + date submitted date finalized
    + Filter
        + Workstreams "i'm" a coordinator of
        + funding sort
    + Expand view turns into table w/ above info
+ MY WORKSTREAM vs MY HISTORY
    + right now they are redundant
    + Change to active / past
+ REMOVE My Rewards page
+ Add profile page
    + Stats page of preformance and participation
    + # of workstreams participated inasdf
### UX TEST SET-UP

## 01/31/2022
### Testing Review
+ Evaluations
    + current: workstream coordinator is 
## 01/26/2023
### UX Testing
+ Targeted groups
    + Service DAOs
        + Raid Guild
        + WGMI
        + Govern
        + HATs
        + DAOHAUS
        + Gitcoin
        + MakerDAO
        + boysclub???
        + IndieDAO
+ Goerli for the Testers
+ 

### Integration with HATs
+ if a partcipant is engaged in a workstream then they are eligible for an 'active member' HAT
+ how would the rV/rA score work into this 
### Review of Ven's update
+ Update
    + add tool tips
    + change font
    + add title for workstream contributors
+ Bugs
    - Fresh contract deployment
    - Look into API key usage
    - WHY NO EVALUATE?!
- Todo
    - Clean up the "Workstream History" page
        - ENS in Workstream history page, evaluations subline
        - Add current evaluations under 'active' label
        - Add tag showing Active + Unresolved
        - Nice2Have: button to block resolution of workstream (based on contested evaluation)
        - Active workstream: Average of evaluations per user
        - Closed workstream: Table overview of all evaluations (like current)
    - "Evaluation Page"
        - add "submit evaluation" button for workstream coordinator (enable coordinator to change evaluation)
    - Update "Workstream View" page
        - add duration to overview
    - "Add workstream" modal
        - Fund Workstream?
            - 

## 01/18/2023
### Next Steps
- make standing meeting
- set deadlines
- plan for ETH Denver
- make user stories


### Notes
#### Blockers
- Funding 
    - test on goerli
- Evaluation
    - minimum worksteam participants
        - DAO tools for individuals is an oxymoron
        - maybe valid evaluations require 3+ people
        - the evaluations are stronger with larger groups, self evaluation isn't very useful
    - prisoners dilema
        - bob: 50 / 50
        - alice: 100 / 0
        - review step - for majority consent
    - Seperate score for how many people have evaluated the person
    - NO SELF EVALS
        - front end blocker for MVP
        - eventually add to contract
## 12/20/2022 
### Next Steps
- Get ven feedback
- after 1st of the year, knock-out list
- Jan 5 and after start testing with folks
### Notes 
- funding of the workstream
    - Might be the beyond the scope of the MVP
    - Maybe FUX is just a reputation mech
- Evaluation
    - ignoring gameification of the eval score ATM
    - enable masturbation, single evaluations
    - how to get consent and consensus on the evaluations
        - 1. build in grace period to review evaluations (yes or no)
        - if all yes workstream is closed evaluations locked
        - if there is one no workstream is sent back to evaluations step
            - repeat until all yes's
            - Necesitates converstiaotn between contributors/coordinator if there is a issue in eval step
            - outside scope of FUX
- Evaluations specificity for v2
    - Evaluation is weighted based on time in the workstream (i.e. if you exit early your evaluations don't carry as much weight)
    - Evaluation is weighted based on a users rV/(rArT) (if my attention is more valuable then my evaluations carry more weight)
- rV/rArT 
    - finish the 27 different permutations to assess if score is valid
    - How do we communicate this score to users?
- Current build
    - can withdraw your FUX whenever you please but you must submit eval before you leave
    - to accomplish the time aspect of the value add need 
- 
- public facing activities?
    - when are we sharing
## 12/02/2022 (We didn't give a FUX in February mate)
BB
0x23314160c752d6bb544661dce13d01c21c64331e
Ven
0xd26a3f686d43f2a62ba9eae2ff77e9f516d945b9
Sass
0x68f272fcaae074cb33e68d88a32c325ed0df8379
Sass II
0x104d7f12941eB03C15bAdEc9aE20523c34677329
- Sass trial bugs
    - ENS not supported for adding contributors
    - Not seeing workstream owner on as contributor
        - [bb] what are you missing exacly? Not very clear from the screenshot
    - reset button not reseting (assigned 50 to each, hit reset and the evaluations dropped to 2)
![](https://i.imgur.com/Fjrjady.png)
    - Not Seeing 
![](https://i.imgur.com/ugufdNg.png)





## Due Date 07/12/2022 (Damn European date form!)
- DAO December Demo
    - First week is talks, Second is hackathon
    - Backstory on FUX How & Why: Pub talk at ETH Denver
    - Upcoming/Nice-to-haves
        - NFT for Completed workstreams or dynamic NFT linked to rV/rA
        - Hats
        - Collaboration: DAOHaus, DeWork, Hats
    - Hackathon bounties
        - staking pool for attention (rV)
        - integration with HATs
            - assign evaluator role 
- SIDE NOTE
    - DM Midge on Quiver Update multiple provider RPCs



## MVP Knock-out list 2022.11.04
### Tasks:
#### Priority 1

#### Contract
- [ ] **P.1** Fresh deployment to wrap-up and review

#### App
- [ ] **P.2** bb: Evaluation: Fux timeline :chart_with_downwards_trend: 
    - [ ] sass:rVrA calculations and info-hover-thingy
- [ ] **P.1** vg: frontend cleanup
- [ ] **P.1** bb: block access to resolve page without FUX

#### Product
- [ ] **P.1** sass: DOCs (i know...) (lol lmfao)
    - [ ] Glossary of terms
    - [ ] Scientific method (WHAT WHY HOW WHO)
    - [ ] FLOW
        - [ ] Workstream 
        - [ ] Workstream resolution

#### 🪳 Bug
- [ ]**P.1** bb: Hide 'Reset' button after fuxxer has submitted vfux

#### Mix

- [ ] **P.1** bb: Option to contest evaluations
    - [ ] Grace period before execution (tranfering FUX)
    - [ ] Contributors/coordinator all must signal yes before eval locks and workstream closes
- [ ] **P.2**  sass: computed/display rV/rArT (feature or enhancement?)
    - [ ] Integrate time calculation into the resolution step
- [ ] bb: Add management to restore FUX by admin (FOR TESTING! 😉)

✅ Done:
- [X] **P.0** vg: ux -> 
    - [x] contrib list: display owner 'tag' if they commit
    - [X] creating workstream: ask if commit during process => will be 'how much' instead of IF
    - [x] contrib list: copy button
- [X] **P.0** Close own workstream and return FUX without workstream
- [X] Add counter that counts down from 100 based on evaluation values
- [x] **P.1** contributor list: Copy address button
- [X] Remove peer evaluation from resolution (and move to history?)
- [x] Update Evaluation header to replace 'vFUX' with '100 points'
- [x] Update evaluation addresses to NOT use address+workstream but workstream
- [x] History space at the bottom
- [x] Evaluations: On-chain - live
- [X] deploy theGraph: https://thegraph.com/hosted-service/subgraph/bitbeckers/fux-goerli
- [x] **P.0** CONNECT TO GOERLI REQUESTS ARE TOO DAMN HIGH! (when visiting other dapps on other chains in  other tabs). can we only prompt metamask to switch if actually triggering a transaction? => QUIVER
- [x] Check if user is FUXxer, not if has FUX balance for start page


ZKFUX ! => Tinder Edition
or masquerade - eyes wide shut lol

### Bug:

### Questions:
* Intermediate change of FUX given => How to display during evaluation and after resolution
* Acceptable if coordinator closes workstream?


### Evaluation flows:

1.

|Persona     | Evaluates | Gives vFUX   | Gets vFUX | 
| --------   |--------   | --------     | --------- |
| Owner      | None      | None         |None       |
| Contributor| Peers     | Peers        |Peers      |

2.

|Persona     | Evaluates | Gives vFUX   | Gets vFUX | 
| --------   |--------   | --------     | --------- |
| Owner      | Contributors | Contributors |None    |
| Contributor| Peers      | Peers         |None       |

3.

|Persona     | Evaluates | Gives vFUX   | Gets vFUX | 
| --------   |--------   | --------     | --------- |
| Owner      | Contributors | Contributors |None    |
| Contributor| Peers      | Peers         |None       |



## Demo Day 09.23.2022
- Workstreams 
    - can have same name, no one cares
    - ENS integration to come
    - Adding contibutors
        - change 'add' and 'add contributor' buttons
- Assigning FUX
    - can you change your fux?s
    - multiple transactions, continue to draw down total FUX. Doesn't correspond to the FUX allocated
    - **Question** are FUX fluid? can we change our attention to a workstream over time?
        - No, not at this time
        - you must remove fux to re-allocate
            - Timestamp the removal
            - if 30% of FUX is allocated for 10 days, if FUX are removed after 5days then only 15% of FUX is evaluated
- Evaluation
    - Coordinape style evaluation
    - Dynamic NFT for preformance on a workstream
        - keep 4 values
            - (average, n, n-1, n-2)
        - pie chart of workstreams, opacity tied to preformance score
    - vFUX metric
        - FUX to vFUX ratio = how valuable your attention is
        - 
## SCOPE
- what utility do we want for this MVP?
    - Profile
        - Data Visualization
            - current allocations via a pie chart
            - ratio of FUX to vFUX shown over time
        - history of workstreams, w/ allocation and resolution informationd
        - dynamic NFT showing 
    - HATS integration
    -
## Flow
- create workstream (just name and collaborators)
    - Masturbation issue: creating solo workstreams to mine vFUX
- coordinator can commit (gives them rights to evaluate)
- invite collaborators
- collaborators can commit (opt-in)
- admins can commence workstream which can set a deadline, but maybe that's optional/not required?
- workstream is active
- workstream can be resolved by admins which requires deadline for resolution
    - Hostage issue: after the grace period (workstream+10%time) then the contributors can resolve the workstream
- notification in-app to all collaborators still committed, to go and resolve
- committers go and resolve
- resolution ends at time set 



