-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Governance: Distribution Report - $SA 1M bounty! #4270
Comments
The project is at a stage in which it would greatly benefit from liquidity pools emerging on multiple DEXs, particularly now that we've launched to token on the Ethereum blockchain. That would, for example, enable CoinMarketCap to verify the market cap and circulating supply figures, and rank the project accordingly. The reports requested on this improvement issue would allow, for example, to show potential liquidity providers how many tokens have existing providers been rewarded with in the past. Under that lens, this improvement is not just desirable for accountability and transparency. It is also a tool that enables the growth of the project. |
@BastianMuc would you be interested in taking on this improvement? |
I'm offering a $SA 1M bounty for this improvement. The initial task is to help clearly define the scope. |
In terms of generating the exported data, is there some preferred format? it probably wouldn't be too much trouble to get the browser to generate a csv file for each table/tab or possibly even an xslx spreadsheet with it all in different sheets. For a more informative report I assume it would be good to know what the tokens were awarded for: Month: MM-YYYY At the moment this would need to be generated from the browser at distribution time/cut-off time, but depending on how the report is generated this could then live in storage and be available for the public to refer back to. |
@Awhiteweb it'd be good if you checked with @BastianMuc if this export process should be related with the actual distribution process, or if it can run previous to the distribution process. In any case, we must make sure that the actual distribution coincides with the report. About the scope of the content of the report and the format: Until now, we know the rewards each address get. In my view, what we need is to know the details of what each address got for each governance program, i.e.: Airdrop, Github, Referrals, Supporters, Mentors, Claims, Votes, Staking, Liquidity, Delegation, Computing (these are tabs within the Governance Tab). Some of these concepts have a reward (Awarded column in the app) and some have a bonus (Bonus column in the app). So, maybe the CSV file should be arranged as follows: User profile, Blockchain Account, Tokens Awarded, Token Bonus, Tokens Mined, ... ... up to that point, it's basically the columns of the Mining tab within the Governance Tab; after that, we include the specific concepts as listed above: ... Airdrop, Github, Referrals, Supporters, Mentors, Claims, Votes, Staking, Liquidity, Delegation, Computing |
Does distribution happen in the app or is the done externally based on the data generated by the governance tabs? |
This is a work in progress, there is now a PR available to review for a UI based download: |
I believe it's an external process that does take the data from the Governance Tab. Please check with Bastian. |
Awesome! Will take a look once it's merged! |
The governance distribution process needs an improvement to make the distribution more transparent and accountable.
At this point, all we know about past distribution events is that X number of tokens where distributed to Y addresses, and how many tokens each address got. To figure this out, one needs to go the token tracker page and research the transactions made by the treasury account.
But it's impossible to trace why those addresses got the rewards.
It'd be good if the distribution process exported the information on each of the Governance tables. That way, everyone could check if the distribution happened as expected.
That will also allow us to keep and publish a historical record of all distributions.
Ideally, the information would be posted or exported as CSV files, with a naming convention that allows populating a folder with all the files generated by recurrent distribution events.
This would also allow us to populate the Sponsors Dashboard described on issue #4269 with historical information, for instance, the rewards obtained by a sponsor for the staking program in the previous distribution, and even accumulated rewards for each concept or program.
The text was updated successfully, but these errors were encountered: