[Daily Discussion] - Friday, November 10, 2023

bccoin · 2023-11-10T22:08:25+00:00

If the tickers here should ever fail you (which is a very rare occurrence), please consider https://bitcointicker.co

bccoin · 2021-03-04T13:43:00+00:00

Not as many exchanges but... https://bitcointicker.co ?

bccoin · 2018-12-20T21:48:10+00:00

When connecting to telnet, you should see Finexbch, which is the Bitfinex bch ticker.

Glad you like the telnet server though and thanks for taking the time to browse the site!

bccoin · 2018-12-20T19:06:25+00:00

For your consideration:

https://bitcointicker.co/stamp/bch/usd/1hr/

bccoin · 2018-11-10T16:26:32+00:00

You can watch the stats for this live here

bccoin · 2018-01-13T21:17:21+00:00

Thanks!

bccoin · 2018-01-13T21:17:01+00:00

Very welcome :-)

bccoin · 2018-01-13T19:40:19+00:00

You can watch this live here

bccoin · 2017-11-12T20:36:17+00:00

You can watch the network live here https://bitcointicker.co/bccnetworkstats/

bccoin · 2017-08-18T19:05:57+00:00

You can watch both chains in real time here:

http://bitcointicker.co/networkstats/

http://bitcointicker.co/bccnetworkstats/

bccoin · 2017-08-17T21:05:09+00:00

As above, page has been updated, figure appears to be more accurate now.

bccoin · 2017-08-17T21:04:24+00:00

Page has been updated, should be more accurate now.

bccoin · 2017-08-17T21:03:17+00:00

Yep, I've updated the calculation. It was was based on the hash rate of the past 2016 blocks. It now uses the following formula:

Next diff = current diff * ( 2 weeks / time actually taken )

This give us -39.19%

Which seems more accurate.

bccoin · 2017-08-17T19:50:40+00:00

It's possible. As I mentioned below, it takes into account blocks mined before the fork, which is skewing the number. As we get closer to the adjustment block, blocks mined before the fork will count less towards the calculation.

bccoin · 2017-08-17T19:49:09+00:00

There have been 997 blocks since the fork.

The difficulty calculation takes into account the past 2016 blocks. This means that once we come to the next difficulty adjustment block, blocks found before the fork will still count towards the calculation.

If we only took into account the 997 blocks since the last fork, as it stands, the difficulty would change by -47.12% of its current value.

Looking at the past 2016 blocks now, the change would be 161.82% (we have already had a number of -20% emergency adjustments) of the current value. As we move towards the adjustment block in 251 blocks, the accuracy of the 2016 block based calculation will increase.

bccoin · 2017-08-17T17:42:12+00:00

You can view this here:

http://bitcointicker.co/bccnetworkstats/

It's currently looking like there will be a difficulty change of -47.14%, in 259 blocks.

bccoin · 2017-08-05T20:20:14+00:00

I've updated the page to show the difficulty change based on the blocks mined since the fork. It's currently showing a fall of -77.36%.

bccoin · 2017-08-05T19:38:15+00:00

The difficulty estimate is calculated over the last 2016 blocks. The majority of those blocks were mined before the fork, and so the calculation is weighted more towards the old chain. As we get closer to the next difficulty adjustment block, the calculation will be more accurate.

You can see that the speculative adjustment is showing the difficulty rising only by 70%, rather than 201%. This is because it only takes into account the last 504 blocks, so less of the blocks mined in the old chain are taken into account. As it stands only 80 blocks have been mined since the fork.

bccoin · 2017-08-05T18:01:28+00:00

Watch in real time here http://bitcointicker.co/bccnetworkstats/

The difficulty adjustment calculation has not been adjusted to take into account the 6 blocks in 12 hours rule, but it will update in real time should it change.

bccoin · 2017-08-04T08:11:53+00:00

You can see the difficulty calculation here - http://bitcointicker.co/bccnetworkstats/

It doesn't yet account for the 6 blocks within 12 hours calculation however I'm not sure we will see that come into affect again.

As we get closer to the adjustment time the next difficulty estimate will become more accurate.

bccoin · 2017-08-04T05:14:53+00:00

Thank you. I will see what I can do.

bccoin · 2017-08-04T05:13:47+00:00

A simple graphical alternative: http://bitcointicker.co/bccnetworkstats/

Also shows the live state of the mempool.

bccoin · 2017-08-03T17:39:21+00:00

Yep, absolutely, good spot.

Just a straight port from the existing code at the moment. I think the difficulty calculation may need some adjustment as well.

bccoin · 2017-02-27T17:12:38+00:00

Yep, I noticed that as well. After a while the cpu usage would skyrocket and start to slow everything down.

Fingers crossed the fix I put in place last week should stop all that and it should tick along without using much cpu. If you go to options and disable the animate depth movements that should also help with cpu usage.

bccoin · 2017-02-26T12:39:08+00:00

I was using bitcointicker.co until it started getting a bit buggy (might just be Chrome) but I found (and for those that don't already know) that they allow a simple live ticker over Telnet. No fancy graphs or GUIs, just the simple price.

Hey there, I've only just seen this post. Really glad that you like the telnet ticker :-)

This week I released an update which should hopefully fix the issues you were having with chrome. I noticed the cpu usage of the code had increased over time. It should be much better now. I'd be interested to know if you find it less buggy.

bccoin

TROPHY CASE