Topic: TRASH (Read 37292 times)
Shit coin. I'm not the first saying that?=)
You are on the wrong Topic ShitCoin is here and yes you are the first mentioning this Coin https://bitcointalksearch.org/topic/ann-new-coin-launch-shit-coin-sht-307419
Just 4 fun
The commit has nothing to do with the diff, it just changed the Hashrate calculation in the deamon ( a log_print )
Sorry, I was unclear. This was just a side reference to an example of the hash rate being derived from difficulty, rather than something the network "knows".
I'm not sure what you want that i change there (commit a pull requests)
I'm working now on a solution
EDIT: As we still finding finding Blocks, I would say that i just change the diff window to 1 Block. As a temporary change
I'm working now on a solution
EDIT: As we still finding finding Blocks, I would say that i just change the diff window to 1 Block. As a temporary change
I was just commenting on the delay between hash rate loss and difficulty, I did not want you to change anything in particular. I'm not sure it's worth changing the window now tbh. The diff will drop at some point, I'm just not sure how much time it'll take.
Oh, sorry. I misunderstood you, let's see how much time it takes.
The commit has nothing to do with the diff, it just changed the Hashrate calculation in the deamon ( a log_print )
Sorry, I was unclear. This was just a side reference to an example of the hash rate being derived from difficulty, rather than something the network "knows".
I'm not sure what you want that i change there (commit a pull requests)
I'm working now on a solution
EDIT: As we still finding finding Blocks, I would say that i just change the diff window to 1 Block. As a temporary change
I'm working now on a solution
EDIT: As we still finding finding Blocks, I would say that i just change the diff window to 1 Block. As a temporary change
I was just commenting on the delay between hash rate loss and difficulty, I did not want you to change anything in particular. I'm not sure it's worth changing the window now tbh. The diff will drop at some point, I'm just not sure how much time it'll take.
New hashrate 60 KH/sec. On track
That large miner(s) seems to have left the network though, so we're stuck with a sky high difficulty till it drops again.
I still see a Network Speed about 60kh/s
Yes, that's the trouble. Network hash is derived from the difficulty [1], and it will go down slowly as the difficulty algorithm realizes that blocks are coming in very slowly, because that 60 kH/s is not there anymore.
10:08:30 73446
12:45:11 73447
14:21:24 73448
16:09:18 73449
19:27:04 73450
Looks like about a block every hour and a half today. And it will be so till enough blocks are found at this rate for the difficulty adjustment mechanism to bring diff down.
[1] That was one thing that needed updating from the CN code in commit c542b91a8a72982a77f46ffd71c3bf17b18ec0c5
Just got home and must agree you, the big miner is away.
The commit has nothing to do with the diff, it just changed the Hashrate calculation in the deamon ( a log_print )
I'm not sure what you want that i change there (commit a pull requests)
I'm working now on a solution
EDIT: As we still finding finding Blocks, I would say that i just change the diff window to 1 Block. As a temporary change
New hashrate 60 KH/sec. On track
That large miner(s) seems to have left the network though, so we're stuck with a sky high difficulty till it drops again.
I still see a Network Speed about 60kh/s
Yes, that's the trouble. Network hash is derived from the difficulty [1], and it will go down slowly as the difficulty algorithm realizes that blocks are coming in very slowly, because that 60 kH/s is not there anymore.
10:08:30 73446
12:45:11 73447
14:21:24 73448
16:09:18 73449
19:27:04 73450
Looks like about a block every hour and a half today. And it will be so till enough blocks are found at this rate for the difficulty adjustment mechanism to bring diff down.
[1] That was one thing that needed updating from the CN code in commit c542b91a8a72982a77f46ffd71c3bf17b18ec0c5
New hashrate 60 KH/sec. On track
That large miner(s) seems to have left the network though, so we're stuck with a sky high difficulty till it drops again.
I still see a Network Speed about 60kh/s
New hashrate 60 KH/sec. On track
That large miner(s) seems to have left the network though, so we're stuck with a sky high difficulty till it drops again.
Exchanges ?
As i posted before we still wait for answeres. But you can Vote for DB on some Exchanges
How is the big update going? Any news?
No news now. We are still working on the Code, there is no ETA.
i have a question why my wallet reload block everytime ?
i need to do "save" ?
You need to do "exit". That command saves automatically.i need to do "save" ?
But you can do "save" also. This saves at any moment, not only on the exit of the program .
DoctorByte logo contest submissions closing January 16th 2015 5pm EST.
https://bitcointalksearch.org/topic/doctorbyte-logo-contest-900007
https://bitcointalksearch.org/topic/doctorbyte-logo-contest-900007
Jump to: