The last few weeks I was developing network dashboard for Decred. It's still in early stage of development, but there are already some useful data, which I want to share with you. See the live site here: http://dcrstats.com And here is github repository - your pull requests and issues are welcome. What was developed so far: 1. Decred price monitoring (BITREX + BTC-E for conversion from btc to usd) 2. Common network stats, such as PoS Difficulty, Poolsize, Mempool size, Average mempool fees, etc. 3. Some hints for PoS miners based on the last ticket price, mempool size and max/average fees. 4. Some charts. Everybody loves charts. What is planed for development in the next few weeks: 1. Network hashrate distribution charts (as start point it will be only public data from the pools) 2. Hints for traders (based on the prices and big orders in Open Books on exchanges) 3. More charts: possibility to switch between Day, Week, Month, All time. 4. (Maybe) Simple sidebar-hidden chat 5. (Maybe) FAQ - so far in the hundred threads on the forum we found many "undocumented features" I mean some important network parameters, which is not yet described anywhere except dcrd source code. I'm not sure that dcrstats is a good platform to shed more light on decred software, probably it's better to choose one forum thread or wiki, but anyway someone should do this. 6. (Maybe) Redesign 7. Performance improvements: separate backend logic part (cron jobs) and express.js part to 2 different applications. Then it will be possible to run webapp in cluster mode (with PM2); Well, please ask me for some cool features that would be useful to have on the network dashboard, I will be happy to develop them. PS: right now project hosted on the cheapest 1$ vps, so maybe you will see some server 500 error, if many of you want to use it, so don't be afraid. However, I think that Node.js is fast enough to handle plenty of us.
@Dyrk, you will pleased to know a request for proposal (RFP) is coming out today for exactly something like this. Except, it's a port of eth-netstats. Might be worthwhile for you and others interested in this kind of work to put in proposals for that. Very cool to see this and it makes me excited knowing there are Node.js developers around!
This is very useful, I've been referencing it throughout the day. Can't think of anything other than some of the 7 you mentioned to add. Even if you port the eth dashboard under RFP3, which is beautiful, futuristic and great for the desktop, I hope you'll still tinker with this one. It's super clean and simple.
Thanks everyone for the feedback! Today I've deployed 2 new experimental features: http://dcrstats.com/ 1. "Voters per block" chart: In total there were 4250 votes casted; but 342 votes were missed or not included in blocks. - 69.1% (or 587 blocks) have 5 votes - 21.6% (or 184 blocks) have 4 votes - 9.3% (or 79 blocks) have only 3 votes This means that PoW miners already lost ~ 1280 DCR and PoS miners lost ~ 636 DCR of reward, if my math is correct. 2. "Decred supply" chart. Here I haven't yet considered difference between "yes" / "no" votes, so this data is not enough correct (only percentage seems to be ok). But anyway you can already imagine how mining process is going. What is in development and will be deployed this week: 1. Ratio of "yes" to "no" votes. (I want to see it so much, but it is not so easy, because I need to parse all SStx transactions) 2. Сountdown to next PoS difficulty adjustment (that's one should be easy to do, but for sure super useful for PoS-miners) 3. Current block subsidy + countdown to next subsidy adjustment. 4. Bug fixes + full&mobile versions UI fixes
I think the ticket price is not showing properly on the graph at the bottom of the page. Please check that. Thanks for this great resource Sent ~$5 according to current price from your website https://mainnet.decred.org/tx/82eda5a5a1e1b2b7f952a96c6a5fa32ec97b96922df2ee33c430481219eed59c
Thank you As for two bottom charts, you are right. They showing daily average values (poolsize may vary in +- 3000 tickets within 24 hours). The same is for ticket price, when it has been just adjusted the average value will start rising next 24 hours. These 2 charts are "all time" charts, they will become more interesting after at least 2-6 months. But for sure I will add also daily "realtime" charts.
I think this needs to be a point in time plot at a specific amount for it to be accurate. Averaging this out over time will change it over time and will give false info.
One thing you could add is the total value of locked DCR. It would involve adding up the difficulty of all tickets still in the pool. That would involve keeping track of each member of the pool and it's difficulty cost separately though, which might not be worth the effort!
I made few changes: 1. DCR price in USD chart added 2. "PoS poolsize" & "PoS difficulty" charts temporarily removed. In current realization they seems to be useless. Need to rethink it. 3. Current block reward, estimated time to next block reward & PoS-price adjustments added. 4. Migrated to https 5. Bugs fixed
I quite liked the PoS poolsize and PoS difficulty charts myself Useful to look at to see if the poolsize is levelling off at the target size or not.
Yeah, I'm going to add them back soon. I just worry that page became quite big, so I think what I can remove or move somewhere else. Maybe it's time to add Tabs "Common", "PoS", "PoW" to separate some data. What I'm going to add: 1. Ratio of "yes" to "no" votes chart (I hope it's possible to parse all votes from 40K pool, it's not just interesting to know, but then we can predict decred supply for next 30 - 150 days) 2. Network hashrate distribution charts 3. PoW-Difficulty chart, PoS-price chart, PoS-poolsize chart As you can see there are at least 5 more charts and tables that I want to deliver to dashboard. My UI skills sucks, I'm wasting so much time for mobile version optimization, so I just afraid to make this page even bigger. Right now I stuck on PoS price predictions: https://github.com/Dyrk/decred-dashboard/issues/5 Good opportunity to start learning Go-lang
@Kandiru well, just for you I optimized PoS-poolsize and PoS-difficulty charts, and they now deployed back. From PoS-difficulty chart I removed interval of 8-22 FEB, when price was always 2. Now it will display only those days, when sbits was adjusted (actually it happens each ~ 12 hours). Anyway now this chart more useful. As for PoS-poolsize chart, the only change is that now it displays maximum daily poolsize (before it was daily average), so I still don't like it, but now it less confusing.
Nice work. Estimation of the next difficulty requires you to create a "hotwired" version of the difficulty algorithm. It should pretend that the current last segment of n blocks extending to the last difficulty adjustment point is actually a full 144 blocks by using targets that are for n blocks rather than 144 blocks. It's TODO along with RPC calls for it. You are welcome to raise an issue on GitHub, or submit a PR yourself. Adding the RPC itself is a little complicated because it needs to be routed through the blockManager for safety.