redesign reporter thoughts

[akremstudy]

Don't track anything in the hooks and make joining and exiting manual via transaction messages.

new design relies on maintenance by reporters and selectors!

MsgCreateReporter

• min to be reporter is 1 TRB
  • Allows reporter to set conditions to be a selectee with reporter. For example, minimum required BONDED tokens at time of selecting.
  • Should force to self select? and meet the requirements specified.
  • not necessarily an issue here but keep in mind total reporter tokens!! don't think you need this since the total tokens needed are in the snapshot!?
  • reporter cannot change their conditions once set? one reason: MsgRemoveSelect

MsgSelectReporter

• can be called if selector doesn't exist in the map (for example, first time)
• reporter conditions are met (ie min trb required)
• should you be allowed to be part of reporter if your stake is more than the lowest stake in the group?

MsgRemoveSelect

• can be called by anyone to remove a selector if their BONDED stake fell below the minimum required for that reporter.
• and if capped at max
• censorship or competition?

MsgSwitchReporter

• puts you in the group of selectors if cap is not met
• checks newly selected reporter conditions are met.
• puts your BONDED power in locked state for a time.

MsgExit

• not required, might mess up count for total actual reporters!!!
• puts selector in a locked state for a period until you're
• can cancel? idk