CoinChoose - alternative site to show respective profitability of the alt coins

[sal002]

imagine all the babies crying right now because of this

Because some immature little whiny people decide to destroy a free service?  Look, all I present is data.  People who fear data are losers, for lack of a better term.  I am never going to charge anyone and all data is verifiable.

I will look at sweeping the data to Google Docs so it is free

dude with your stupid service people pump and dump.. what good is that! I am so glad this site is down!

pump and dump is market manipulation on exchanges, it has almost nothing to do with switching from coin to coin based on profitability.
Miners by definition sell coins, they don't pump (buy) then dump (sell).

If you believe people waited for coinchoose to switch from coin to coin based on profitability you are sorely mistaken.

To give you an example, I only have one command to launch and 3 config files to edit for adding a new coin to my setup.
This includes automatically compiling the coin daemon from the git repository, adding an init script for it and launching it. My setup then distributes the configuration to the rigs needed to solo-mine and adapts to the new coin. It parses the exchanges rates, uses the local daemon to find out the actual mean reward including fees, computes an estimation of the orphan rate and fine-tune it from the rate of orphan my rigs mine. When the data is in it starts to switch rigs to the coin if it is the most profitable for a rig (it uses the sha256d and scrypt efficiency of each rig to make this decision).

I'm even warned when:

• the coin becomes popular enough that solo-mining becomes gambling so that I configure P2Pool for this coin or create a pool account,
  
• the original git repo is updated
• the coin is dying and may be removed from my configuration

I don't use coinchoose anymore (I did briefly as a source for exchange rates but I prefer to develop more elaborate decision algorithms) so if you think DoSing coinchoose will prevent people from switching from coin to coin, it's only true for the less serious miners that don't/can't code a dynamic setup like mine. Linking coinchoose to pump and dump is simply ridiculous.

This is exactly what I mean.  Mine is just the basic info and I am glad to see people developing more sophisticated methods! 

[1715000240]

1715000240

[1715000240]

1715000240

[mat5x]

I actually paid to have coinchoose shutdown.  Just rasing capital to shut down the rest.  make people work for their mining   I want to be able to mine them all when the diff is low and the hash is nil.  More coins for me bitches!

This is exactly what happened. SOmeone did it for themselves, or got someone to do it for them.

Its goign to keep happening, because there's market advantage to doing this. Idiots believe a 0.5BTC deep market is the proper value of 100,000 ALT, and so they go mine it.

I should look at historical trading info and see how much value was actually recaptured by flashmining a coin for 15 or 20 minutes. I bet it's way godamn lower than people think.  Like 1000x lower. Has to be. You have people doing 100BTC worth of mining over a day or 2 on hype coin, and the market depth is 0.5, that 100BTC never reappears in the form of sold ALT even in the next weeks.
Im not sure how people think thats a proper valuation.

Anyway, two ways to attack this issue, one is to try and dos every secret little valuing site, the other is to code a CC-resistant coin:

https://bitcointalk.org/index.php?topic=230105.new

[kevindeangelis]

Back up.

yay! you rock man!

[BitBardev]

Hi!!

I see you properly read diff of bitbar, but completely lost block reward.
you can make and easy workaround:

Calculate reward = 1/(diff/0,000244140625)^(1/6) ; and your problems will go forever.

Code:

coin.block_reward =  COIN / pow(coin.difficulty, 0.16666667)

Also, You can set default sort to adjusted diff, because it is awesome!

Thank You for this great site.
 

[sal002]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

[sal002]

Hi!!

I see you properly read diff of bitbar, but completely lost block reward.
you can make and easy workaround:

Calculate reward = 1/(diff/0,000244140625)^(1/6) ; and your problems will go forever.

Code:

coin.block_reward =  COIN / pow(coin.difficulty, 0.16666667)

Also, You can set default sort to adjusted diff, because it is awesome!


Thank You for this great site.
 

That calc leads to a block reward of around .61, but I believe it is .16. 

[dreamwatcher]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

I would be careful about any site that gives network hash rates on any of the POW/POS chains.

The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix     ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula.

I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week.

[BitBardev]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

Yes, this page is wrong too. It is NOT official page.

[BitBardev]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

I would be careful about any site that gives network hash rates on any of the POW/POS chains.

The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix     ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula.

I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week.

No.

Reward is based on difficulty. It is trivial to calculate, PoS found or not.
PoS blocks are rising the difficulty, so hashrate is hard to determine without eliminating PoS blocks.

 
 

[BitBardev]

Hi!!

I see you properly read diff of bitbar, but completely lost block reward.
you can make and easy workaround:

Calculate reward = 1/(diff/0,000244140625)^(1/6) ; and your problems will go forever.

Code:

coin.block_reward =  COIN / pow(coin.difficulty, 0.16666667)

Also, You can set default sort to adjusted diff, because it is awesome!


Thank You for this great site.
 

That calc leads to a block reward of around .61, but I believe it is .16.  

You have a broken calc.

diff: 14.03671291

14,03671291/0,000244140625 = 57494,376079
57494,376079^1/6 = 6,212564264
1/6,212564264=0,160964

That calc leads to a block reward of around 0.16 .

power comes before division

just paste it into excel or type it into science calc.

try again

edit:
go: http://web2.0calc.com/
paste: 1/(14.03671291/0.000244140625)^(1/6)
or paste it straight to google
https://www.google.pl/search?q=1%2F(14.03671291%2F0.000244140625)%5E(1%2F6)&oq=1%2F(14.03671291%2F0.000244140625)%5E(1%2F6)&aqs=chrome.0.57j58j0.1001j0&sourceid=chrome&ie=UTF-8

[dreamwatcher]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

I would be careful about any site that gives network hash rates on any of the POW/POS chains.

The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix     ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula.

I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week.

No.

Reward is based on difficulty. It is trivial to calculate, PoS found or not.
PoS blocks are rising the difficulty, so hashrate is hard to determine without eliminating PoS blocks.

 
 

I am not addressing rewards, but total network hash rate.

[BitBardev]

I get it from here - http://bitbar.info/stats/index.php.  Should that be fixed as well?

I would be careful about any site that gives network hash rates on any of the POW/POS chains.

The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix     ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula.

I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week.

No.

Reward is based on difficulty. It is trivial to calculate, PoS found or not.
PoS blocks are rising the difficulty, so hashrate is hard to determine without eliminating PoS blocks.
 

I am not addressing rewards, but total network hash rate.

Oh.. yea, sorry, but there is no hashrate on coinchoose. I assumed You are on topic.

[dreamwatcher]

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.

[BitBardev]

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.

In that case, You ARE on topic. sorry again.

[xorxor]

FTC is showing 220% profit when it is actually broken and gives 0%  - FTC forked into multiple chains and every big pool is on a different chain, [ftcpool, coinotron, give-me-ftc, wemineftc]

Bitbar is showing 0 reward, while giving 0.16 BTB

just refreshed and It's ok now.

[sal002]

FTC is showing 220% profit when it is actually broken and gives 0%  - FTC forked into multiple chains and every big pool is on a different chain, [ftcpool, coinotron, give-me-ftc, wemineftc]

Bitbar is showing 0 reward, while giving 0.16 BTB

BitBar is now fixed.  SO, basically, I should remove Feathercoin?

[rbdrbd]

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 two.

The FTC fiasco fallout and cleanup should be fun. I'm mining DGC myself.

[sal002]

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).

[xorxor]

FTC is showing 220% profit when it is actually broken and gives 0%  - FTC forked into multiple chains and every big pool is on a different chain, [ftcpool, coinotron, give-me-ftc, wemineftc]

Bitbar is showing 0 reward, while giving 0.16 BTB

BitBar is now fixed.  SO, basically, I should remove Feathercoin?

right now FTC is forked. noticed BTC-E , just finishing my mail to Bter and cryptsy.

I believe removing wil save many people from loosing tons of hashes, like I just did.

[xorxor]

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).

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.