Re: CoinChoose - alternative site to show respective profitability of the alt coins
[/quote]
A few things:
1. Would it be possible to show current network hashrate for each of the coins? That info would be AWESOME for judging overall coin health but may be a bit out of scope to coinchoose (if you do it, a graph like you have of the prices would be the cat's meow).
2. What about total market voume trade (in BTC) for each of the coins over the past 24 hours? Another crucial bit of info in deciding which coin to mine.
3. Total coin marketcap would be a valuable one to see too... not as crucial as the first too.
The FTC fiasco fallout and cleanup should be fun. I'm mining DGC myself.
Yes to all three. Hashrate is what I am looking at adding next (once I verify I have a good way of finding it).1. Would it be possible to show current network hashrate for each of the coins? That info would be AWESOME for judging overall coin health but may be a bit out of scope to coinchoose (if you do it, a graph like you have of the prices would be the cat's meow).
2. What about total market voume trade (in BTC) for each of the coins over the past 24 hours? Another crucial bit of info in deciding which coin to mine.
3. Total coin marketcap would be a valuable one to see too... not as crucial as the first too.
The FTC fiasco fallout and cleanup should be fun. I'm mining DGC myself.
hashrate doesnt work for PoS networks . It eliminates PoS blocks from security and health estimation.
PPC has +80% of PoS blocks. it would be super secure on 0 hashrate.
My fault, I should have been clearer.
I was just stating my concerns about a site that would put up a network hash rate that cannot be accurate.
Just to take caution with the rest of their numbers...
Anyway, I am basically going to get around the POS/POW problem by setting up an extra database that will contain the POW difficulty for every block since its implementation. The explorers on CCE update every block when the daemon trips the blocknotify script. I will add the process of getting the POW difficulty for the block currently being mined, along with a couple of other bits of information. This should allow for an accurate hash rate calculation.
The extra information is to allow the users of the getnetworkhash API to use time or blocks when defining how they want the network hash calculated.As of now the API only allows for blocks.
I was just stating my concerns about a site that would put up a network hash rate that cannot be accurate.
Just to take caution with the rest of their numbers...
Anyway, I am basically going to get around the POS/POW problem by setting up an extra database that will contain the POW difficulty for every block since its implementation. The explorers on CCE update every block when the daemon trips the blocknotify script. I will add the process of getting the POW difficulty for the block currently being mined, along with a couple of other bits of information. This should allow for an accurate hash rate calculation.
The extra information is to allow the users of the getnetworkhash API to use time or blocks when defining how they want the network hash calculated.As of now the API only allows for blocks.
Is this thing on? Can people see my posts??
As long as POW blocks are being produced there is a hash rate. My plan does not elimate the POS blocks, but rather uses what the POW difficulty of a POS block would have been had it been solved via POW vs, POS. Thereby counting POS blocks in the calculation.
