|
Title: Block Chain Size On Disk size Vs Number of Full Nodes Post by: TransaDox on July 21, 2015, 03:18:14 PM Can any point me to graphs or data showing a relationship, if any, between the block chain database size on disk (currently at about 40ish GB) for a full node and the number of full nodes over time? Is there a correlation?
I don't mind if I have to create them from raw data. Just point it out for me please? Title: Re: Block Chain Size On Disk size Vs Number of Full Nodes Post by: unamis76 on July 21, 2015, 03:22:05 PM I don't think there's such a chart, that I'm aware of, but it would be interesting to see one.
Maybe someone can take this (https://blockchain.info/charts/blocks-size?timespan=all&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=) info and this (https://getaddr.bitnodes.io/dashboard/?days=365) (or maybe something with more historical data, if it exists), combine them and create such a chart. Well, here's an idea for my free time... :D Title: Re: Block Chain Size On Disk size Vs Number of Full Nodes Post by: TransaDox on July 22, 2015, 10:01:27 AM I don't think there's such a chart, that I'm aware of, but it would be interesting to see one. Maybe someone can take this (https://blockchain.info/charts/blocks-size?timespan=all&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=) info and this (https://getaddr.bitnodes.io/dashboard/?days=365) (or maybe something with more historical data, if it exists), combine them and create such a chart. Well, here's an idea for my free time... :D Great. I was able to download the data for the block chain size, but the reachable nodes had no such facility as far as I could tell. The nodes graph seems to be all reachable nodes, which is useful, but not as useful as knowing full nodes which require the full block chain. Is there a way to distinguish a full node from any old node or is the user agent sufficient? |