Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving council reports #18

Closed
mochet opened this issue Sep 1, 2020 · 2 comments
Closed

Improving council reports #18

mochet opened this issue Sep 1, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@mochet
Copy link
Collaborator

mochet commented Sep 1, 2020

Currently I complete all the council reports by hand and using small code snippets within the Javascript menu, there is a lot that could be improved and these could largely be automated and improved upon.

Compared to the tokenomics reports, the council reports should ideally focus on both:

  • data (aspects of council performance, how much CMs voted, how quickly proposals were voted through and other information that isn't available from the chain or UI)
  • opinion (what were problems, challenges and what can be improved)

You can look at the current set of council reports to get an understanding of what they show now: https://github.com/Joystream/community-repo/tree/master/council-reports

These improvements + automation could easily be completed for bounties, I can help to produce a template if necessary. The end product would ideally be a script which can take a start + end blockheight as input and output a detailed, useful council report that can then be completed with a bit of input for the opinion aspects.

  • Council / election round number
    • How many elections were held to elect this council, how long did it take?
    • How many applicants, how much stake, how many votes?
    • How much is the total stake + votes behind all applicants?
    • How many unique accounts voted?
  • Council member information
    • Who are the council members, how much stake, how many votes?
    • What was the total amount of stake/votes put behind the successful council applicants?
  • Council mint information
    • Start and end total minted values
    • How much was spent on minting proposals? (+ percentage of this from mint spend)
    • How much were council members paid, were any payments missed? (+ percentage of this from mint spend)
    • Percentage increase difference from start to end
  • Proposal information
    • Proposal totals, proposal type totals
    • For spending proposals the total value of these proposals
    • For mint proposals the total value of these proposals
  • CM participation info
    • How long did each proposal take to finalize, what was the total + average time for proposals to get finalized?
    • How often did each council member vote?
@mochet
Copy link
Collaborator Author

mochet commented Sep 8, 2020

More additions:

  • Per Mint Spend / non-spend failure
    • Total per mint spend (ex. how much did proposals for the storage mint add to?)
    • Total per mint non-spend (ex. total of all expired and cancelled proposals for storage mint and other mints)
  • Burn
    • Total tokens burned via proposal failure (ex. cancelled, expired and withdrawn proposals have a fee, what is the total of these fees?)
  • Proposals
    • Total stake used for all proposals added together
    • Highest simultaneous proposal stake
    • Proposals have different active periods, what percentage on average did it take to reach a proposal being finalized? (ex. if a text proposal has a voting period of 72k blocks, and on average text proposals were finalized at 36,500/72,000 what percentage is this? What is this percent value for each proposal type?)
  • Proposal limits
    • For how long, if at all, were proposals unable to be submitted due to the proposal pool being filled? (this is currently set at 5 but may change later on)

@mochet
Copy link
Collaborator Author

mochet commented Sep 19, 2020

One more metric we could add to council reports is to track the total potential council actions and what percentage of these are fulfilled during a council term. This would simply add up all the votes needed to reach quorum on the various proposal types (ex. a runtime needs 90% quorum, so on a 10 member council, this would be 9 required votes)

The reason for this metric is it gives a very easy indication of how well the entire council performs.

freakstatic pushed a commit to freakstatic/community-repo that referenced this issue Oct 9, 2020
This PR adds the council report for round Joystream#18 (KPI 14.3)
@mochet mochet added the enhancement New feature or request label Nov 3, 2020
@mochet mochet closed this as completed Feb 5, 2021
freakstatic added a commit to freakstatic/community-repo that referenced this issue Aug 25, 2021
freakstatic added a commit to freakstatic/community-repo that referenced this issue Aug 25, 2021
freakstatic added a commit to freakstatic/community-repo that referenced this issue Aug 25, 2021
mochet added a commit that referenced this issue Aug 26, 2021
mochet added a commit that referenced this issue Aug 26, 2021
…report

Add sumer council #18 tokenomics report
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant