---
tags: Legacy
---

# Delegator Brainstorming

## Work Plan

- Better refine the system level view and map out to what extent there should be a system of systems
- Use a many to one, one to one, etc format
- Sync up on the style of this graphic and the ways to define behaviors (i.e. behavioral vs. policy)
- Broker Stake Pool, for example, should be its own system that further defines the behavior patterns
- Begin with the broker stake pool specification including both graphics to describe the actions and flows + a beginning mathematical specification

## System Level

- Define the behaviors to track and how at the aggregate level it works
- Further refine the diagram below
- Build out the mathematical specification in a system of systems style


## Stake Pool Dynamics

- Each stake pool is a smart contract and the behaviors should be zoomed in to further define them

## Bounty

- Bounty is a smart contract?
- Further define how it interacts with the other pieces of the system

## Meeting Notes

- Does the broker interact with agreement that interacts with the pools for example
- Action space
- Broker vs. broker agreement
- Not as much policies as much as sub-systems
- Are you able to lose your capital
- Earlier parties want to benefit earlier when they have delegated
- Set of challenges
- Can lose money
- Started with price discovery
- Risk management
- Package of rights with brokers vs. delegators, etc.
- How do slashing events work
- How do losses get taken care of for shareholders
- Undelegate stuff in reserve, suck funds out of unallocated?
- Would have to force a broker to back out possibly
- Estimated time to break even on yields
- Does delegate believe in the broker -> add more to the contract or grab the stuff back
- Show the visual -> then explain what we previously have done (price discovery, no slashing, etc) -> more practically for consequences for failures -> list of issues -> math spec or outline of math spec