To determine real Curation, Storage and Operations spending summarize all worker and lead rewards during the period (code).
Bounties are not part of WG budgets but are paid from council budget via spending proposals.
Spending proposals need to be assigned to a WG manually. Find a way to associate spending proposals with a WG budget that makes sense long-term (possibly using labels if provided):
Should the UI allow for it? Save changes in local storage or backend, on chain?
The council manages a list of spending proposals in the community repo. They can be used but might be out of date:
Validators: The maximum reward is variable and depends on issuance and total stake (see Rewards on Joystream
). It can either be predicted based on past or current issuance using chain constants. To calculate real rewards summarize staking.EraPayout for the maximum payout per hour and staking.Reward for what is actually claimed by validators and nominators.
To enable consuls to predict budget spending:
1. Update https://joystreamstats.live/tokenomics with
- a bar chart with spent / total for each WG and the council term budget
- a cake / donut chart each for WG budget % spent / maximum
- a table similar to [tokenomics](https://pioneer.joystreamstats.live/#/tokenomics) with `minted JOY`, `budget JOY`, `minted $`, `budget $`, `Share` for each WG and total
- Either show all terms (Accordion) or let the user select one.
2. Let users change budget values for the current term.
3. Provide a way export a markdown table that can be used in posts.
# Data
Because budgets are approved via proposals the numbers need to be added manually. A `JSON` file can be stored at https://joystreamstats.live/static.
Some code to retrieve needed data can be found here:
- [report generator](https://github.com/Joystream/community-repo/blob/master/community-contributions/report-generator/src/StatisticsCollector.ts)
- [status-endpoint-joystream](https://github.com/Joystream/status-endpoint-joystream/tree/development/src)
- See also https://git.joystreamstats.live/Operations/process/issues/34
To determine real Curation, Storage and Operations spending summarize all worker and lead rewards during the period ([code](https://git.joystreamstats.live/Operations/jsstats/src/f85a8bf2830c2029042a2a652b02cdd4254e1af0/server/joystream/rewards.ts)).
Bounties are [not part](https://discord.com/channels/811216481340751934/822087161104957470/878601654700748840) of WG budgets but are paid from council budget via spending proposals.
Spending proposals need to be assigned to a WG manually. Find a way to associate spending proposals with a WG budget that makes sense long-term (possibly using [labels](https://github.com/Joystream/pioneer/issues/577) if provided):
- Should the UI allow for it? Save changes in local storage or backend, on chain?
- The council manages a list of spending proposals in the community repo. They can be used but might be out of date:
- https://github.com/Joystream/community-repo/blob/master/documentation/spending_proposal_categories.csv
- https://github.com/Joystream/community-repo/blob/master/documentation/spending_proposal_categories.json
Validators: The maximum reward is variable and depends on issuance and total stake (see [Rewards on Joystream
](https://github.com/Joystream/helpdesk/tree/master/roles/validators#rewards)). It can either be predicted based on past or current issuance using [chain constants](https://github.com/Joystream/joystream/blob/master/runtime/src/lib.rs#L342). To calculate real rewards summarize `staking.EraPayout` for the maximum payout per hour and `staking.Reward` for what is actually claimed by validators and nominators.
To enable consuls to predict budget spending:
Update https://joystreamstats.live/tokenomics with
minted JOY,budget JOY,minted $,budget $,Sharefor each WG and totalLet users change budget values for the current term.
Provide a way export a markdown table that can be used in posts.
Data
Because budgets are approved via proposals the numbers need to be added manually. A
JSONfile can be stored at https://joystreamstats.live/static.Some code to retrieve needed data can be found here:
To determine real Curation, Storage and Operations spending summarize all worker and lead rewards during the period (code).
Bounties are not part of WG budgets but are paid from council budget via spending proposals.
Spending proposals need to be assigned to a WG manually. Find a way to associate spending proposals with a WG budget that makes sense long-term (possibly using labels if provided):
Validators: The maximum reward is variable and depends on issuance and total stake (see Rewards on Joystream ). It can either be predicted based on past or current issuance using chain constants. To calculate real rewards summarize
staking.EraPayoutfor the maximum payout per hour andstaking.Rewardfor what is actually claimed by validators and nominators.