---
# System prepended metadata

title: 6/2/2022 Meeting Notes
tags: [Meetings]

---

---
tags: Meetings
---

# 6/2/2022 Meeting Notes
## 5/18 Questions
1. Stake Slashing:
    - Important for the mechanisms to allow suers to differentiate themselves
    - Don't want to have the same preference profile for all the agents.
    - This can be done by allowing them to "attach" themselves to data, i.e. allowing them to observe their time and risk preferences w.r.t. different parameter values/data points.
    - Need to create enough data to allow agents to differentiate themselves.

2. In addition to technical documentation, it's important to have "user documentation", explaining how to function as a successful ecosystem participant
    - For example, how to run a successful Broker "business", analogous to a micro-SaaS business.

3. Rather than autocompounding, explicitly separating revenue and capital has organizational and psychological benefits.
    - However, autocompounding allows your profits to earn profits instead of just lying there.
    - At the systemic level, autocompounding results in a lot of capital just sitting there, rather than being used.
    - Leaving rewards separate is then like a call to action, prompting users to use their funds.
    - This layer of indirection avoids the default case of everyone autocompounding and "buys time" for a system with e.g. routing between streams to be built.

## cadCAD vision
1. narrower design space allows more focused exploration of parameters
2. develop kpis for desired parameters and run experiments to make sure bad UX or unintuitive behavior is dealt with.
3. Add time-weighted mechanism to delegator invest
    - Time-based mechanisms can preserve linearity in user actions
    - Allows you to avoid front-running by accounting for user's time-preference w.r.t. their actions.
    - Bonding curves are vlunerable to the front-running problem but have challenges related to capital.
4. In addition to short and long-form scenarios, we should have failure scenarios as well, so that we can handle steering away from them.

## Bounty Kick Mechanism
1. A standard way of collecting attestations and comparing it to the data needs to be developed on top of the smart contracts.
2. Then you can integrate into a platform like Celeste or Kleros and add a judicial system.
3. However, the data pipeline is currently hard as you can't snapshot the P2P system properly right now.

