Skip to content
This repository has been archived by the owner on Nov 26, 2024. It is now read-only.

Sprint 2 User Story 8: Admin reporting #53

Closed
1 of 4 tasks
nickysemenza opened this issue Feb 26, 2018 · 4 comments · Fixed by #76
Closed
1 of 4 tasks

Sprint 2 User Story 8: Admin reporting #53

nickysemenza opened this issue Feb 26, 2018 · 4 comments · Fixed by #76
Assignees
Labels
feature stack_laravel laravel backend stack_react React code
Milestone

Comments

@nickysemenza
Copy link
Member

nickysemenza commented Feb 26, 2018

  • Create a current players report for admins, with stats such as cardCount, battleCount, win%, etc.
  • Create a transactions report with stats about all transactions, including seller, buyer, card, and price.
  • Create a transactions list on the card detail page for displaying all transactions involving that card
  • Create a transactions report with stats about token creation, including graphs of tokens created over time (maybe use https://www.amcharts.com)
@nickysemenza
Copy link
Member Author

@bbemis017 checkout http://recharts.org

@bbemis017
Copy link
Contributor

@harrischristiansen @Shonas301 Just to make sure I'm on the same page. I should query this data from mysql and the solidity code will fire an event that our backend will pick up and update the mysql database.

@nickysemenza
Copy link
Member Author

@bbemis017 all the data on transactions, users, etc should already be cached in the DB technically, since it'll be persisted to the DB as soon as each disparate transaction is put on the blockchain.
SO i don't think we'd need to interact with solidity for this, since it's only reading that's happening (except for say blacklisting users/cards, but that's #57, but does live under the admin section)

We could run into into a situation where for some reason the backend doesn't pickup on some blockchain txn happening, so perhaps we should do some sort of periodic DB state reconciliation on a cronjob. (although how does gas work for that if we are querying the blockchain un-prompted??)

@bbemis017
Copy link
Contributor

ok cool, I just wanted to double check before I starting building it.

As far as doing some kind of syncing operation, it should probably be avoided. But I think crypto kitties does something like that every once in a while.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature stack_laravel laravel backend stack_react React code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants