Monero Circulating Supply Scraper

[diadata-org]

Monero Circulating Supply Scraper

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.3 ETH (82.4 USD @ $274.68/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $20,836.84 more funded OSS Work available on the Gitcoin Issue Explorer

[ankit-maverick]

@kaythxbye What source are we looking to scrap from to get the amount of circulating XMR coins?

[kaythxbye]

@ankit-maverick We would like to have a Monero blockchain node running that is used to get the amount of circulating XMR. We do not want to scrape a website, we need a reliable direct source (i.e. the blockchain itself).

[ankit-maverick]

@kaythxbye Do we have a blockchain node running already?

[kaythxbye]

@ankit-maverick You can find a dockerfile here: https://github.com/monero-project/monero/blob/master/Dockerfile

[kaythxbye]

@ankit-maverick Do you have any updated? Do you need more information?

[joshpurvis]

@kaythxbye I was considering this task too, but I'm not sure this is possible in a reasonable amount of time given the way your scrapers are currently configured (they update every 10 seconds). If I recall, it took about 20-30 minutes to calculate the supply from genesis on my relatively modern desktop. Is that acceptable?

An alternative might be to store the previous height/supply so that you can just calculate the difference. This can be done in a temp file if the scraper runs continuously, or by querying a database somewhere which provides those values as needed.

https://monero.stackexchange.com/questions/7468/calculating-the-circulating-supply-using-daemon-rpc

[kaythxbye]

@joshpurvis 20-30 minutes from genesis is quite quick, Ethereum takes hours until it is synced. Once it is running continuously however, it is relatively easy to keep up as only a diff has to be calculated. So your proposal is totally acceptable.

Storing a previous height in a db is also a good optimization idea, the scraper is determined to run continuously and we have a redis DB in the background. You could provide function stubs for storing and retrieving temporary results and we will then integrate them in our live system. These stubs then can check if a stored result is available and if yes, only determine the increment from then.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 5 days, 4 hours ago.
Please review their action plans below:

1. joshpurvis has started work.

   I have this task 90% finished, since I had already written some rough code in Python. I just have a slight rounding error and some cleanup work to do. It should be completed by tomorrow. (US/Eastern time)

Action plan:
[x] - Quick proof of concept converted to Go from Python
[x] - Keep track of previous height's supply in memory so that we only have to calculate difference
[ ] - Fix rounding error
[ ] - Cleanup overall code quality

Questions:
Do I need to do anything with the Dockerfiles? It's not apparent to me how they all fit together at the moment.

Learn more on the Gitcoin Issue Details page.

[joshpurvis]

Submitted a PR of the initial version for feedback. The rounding error should be fixed now that I switched from big.Float to big.Rat. Will make any adjustments tomorrow, if needed!

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 0.3 ETH (73.29 USD @ $244.31/ETH) has been submitted by:

1. @joshpurvis

@diamw please take a look at the submitted work:

• PR by @joshpurvis

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $20,923.06 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 0.3 ETH (51.46 USD @ $171.54/ETH) attached to this issue has been approved & issued to @joshpurvis.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $25,669.50 more funded OSS Work available on the Gitcoin Issue Explorer