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
Establish how much more was allocated to each worker for term 32 #5145
Comments
Reward paid can be extracted from the QN with the following ( query dwgWorkerRewards {
rewardPaidEvents(
where: {
inBlock_gte: 7012830
group: { id_eq: "distributionWorkingGroup" }
inBlock_lte: 7314596
}
) {
inBlock
createdAt
amount
worker {
membership {
handle
}
}
}
}
|
Amount column (see appendix) can then be aggregated by member handle and compared with the actual plan.
The procedure to rebalance DWG salaries is the following:
|
Future directionA few observations, we have now joyutils which allows you to set block reward given the usd amount at each term. |
Appendix
|
DWG first refund: coming from |
I like that all the necessary info was written above clearly and the issue is being resolved accordingly. |
From there worker
I will close the issue once all workers have been correctly compensated |
|
ConclusionI have transferred to the DWG budget:
Hence worker spoonbender ows in total Next Steps
Final debt table setup (HAPI with 2 decimals to ignore)
|
From the above, converting the JOY amounts into USD with ema30(term 32) = .021 An operator salary is 327USD per term, If we set his salary to 55USD per term it means that the remaining 272USD are going to
|
I have erroneously set the reward per block to a too high number.
The previous DWG board item solves the unnecessary DWG debt that should be zero.
Now I need to figure out how much each worker has been paid since the erroneous start of the term. This can be achieved, for instance, by inspecting the subscan tool with the reward account for each worker (which can be view on the DWG entity on the chain). From there I will figure out:
DWG workers and councilors will be clearly notify of all of this.
The text was updated successfully, but these errors were encountered: