|
bitcoinkkk
|
 |
January 13, 2015, 08:39:37 AM |
|
Exchanges ?
|
|
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
PestoQuinty
Member
 Offline
Activity: 106
Merit: 10
|
|
January 13, 2015, 09:53:24 PM |
|
How is the big update going? Any news?
|
|
|
|
|
doctorbyte (OP)
Jr. Member
Offline
Activity: 140
Merit: 1
|
|
January 14, 2015, 02:29:26 PM |
|
How is the big update going? Any news?
No news now. We are still working on the Code, there is no ETA. |
|
|
|
|
doctorbyte (OP)
Jr. Member
Offline
Activity: 140
Merit: 1
|
|
January 14, 2015, 02:30:44 PM |
|
Exchanges ?
As i posted before we still wait for answeres. But you can Vote for DB on some Exchanges |
|
|
|
|
|
ikanunaki
|
|
January 19, 2015, 01:03:03 PM |
|
New hashrate 60 KH/sec. On track
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
January 19, 2015, 05:31:08 PM |
|
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. |
|
|
|
|
doctorbyte (OP)
Jr. Member
Offline
Activity: 140
Merit: 1
|
|
January 19, 2015, 07:09:19 PM |
|
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 |
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
January 19, 2015, 08:12:48 PM |
|
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 |
|
|
|
|
doctorbyte (OP)
Jr. Member
Offline
Activity: 140
Merit: 1
|
|
January 20, 2015, 07:55:32 AM
Last edit: January 20, 2015, 08:07:33 AM by doctorbyte |
|
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 |
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
January 20, 2015, 08:18:05 AM |
|
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 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. |
|
|
|
|
doctorbyte (OP)
Jr. Member
Offline
Activity: 140
Merit: 1
|
|
January 20, 2015, 12:19:55 PM |
|
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 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. |
|
|
|
|
|
0x6A
|
|
January 20, 2015, 12:27:45 PM |
|
Shit coin. I'm not the first saying that?=)
|
|
|
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
February 28, 2015, 07:13:44 PM |
|
Just a note to say the pool is now stopped, as no miners there for a couple days and I need the RAM.
|
|
|
|
|
|
