sorry guys could not stand it
Topic: TRASH - page 7. (Read 37362 times)
I'm talking about an external miner, not the wallet miner
Can't do that, they're pool miners. You could run your own pool though, but then you'd run into the same thing.
Why Spam ? We use a better Ring Signature and a better Block Calculation, we have 25Million Coins.
Oh, what did you change to the ring signatures ? I thought there were just changes to the emission config.
I'm talking about an external miner, not the wallet miner
Can't do that, they're pool miners. You could run your own pool though, but then you'd run into the same thing.
Why Spam ? We use a better Ring Signature and a better Block Calculation, we have 25Million Coins.
Oh, what did you change to the ring signatures ? I thought there were just changes to the emission config.
There are more One Time address created, so there is a Higher Security
I'm talking about an external miner, not the wallet miner
Can't do that, they're pool miners. You could run your own pool though, but then you'd run into the same thing.
Why Spam ? We use a better Ring Signature and a better Block Calculation, we have 25Million Coins.
Oh, what did you change to the ring signatures ? I thought there were just changes to the emission config.
How exactly is this coin different from other cryptonote coins? Except try to ride doctorcoin train when You missed on monero?
Found this coin from spam in another thread. Not cool man, not cool...
Found this coin from spam in another thread. Not cool man, not cool...
Why Spam ? We use a better Ring Signature and a better Block Calculation, we have 25Million Coins.
What is DoctorCoin never head for that.
Have a link from the another thread ?
How to solo mine with external miner?
My miner shows 300H/s and pool only gets ~80
My miner shows 300H/s and pool only gets ~80
start_mining
I'm talking about an external miner, not the wallet miner
How to solo mine with external miner?
My miner shows 300H/s and pool only gets ~80
My miner shows 300H/s and pool only gets ~80
start_mining
For the pool hash rate, it counts an average of submitted shares over the last... 20 minutes I think.
If you've waited at least that long, then it does sound odd if it never goes above that.
Blocks found stay maturing for 60 blocks, so you should see your pending balance increase after a found block you hashed for matures (and is not an orphan). At the moment, it takes about 1 hour and a half. See
http://dbpool.mooo.com/#pool_blocks for the list of blocks, and you can get an idea of when a block you hashed for matures.
http://dbpool.mooo.com/#pool_blocks for the list of blocks, and you can get an idea of when a block you hashed for matures.
Is there something wrong about this pool? I've submitted some shares, but still got nothing on pending...
You may check those details;
Address: dbz1mWbLMushi59ZuEjdyRDMcJx4DBtpmiVkCjbde915iRqyrRkMhidDBifBuAHUTEWZTS8SLLnhNfZ FRUEzcYSQ4RuHq3gF99
Pending Balance: 0.000000000000 DB
Payment Threshold: 1 DB
Total Paid: 0.000000000000 DB
Last Share Submitted: 3 minutes ago
Hash Rate: 10.00 H/sec
Total Hashes Submitted: 10000
We could try to change the Block Speed to 60 or 150 seconds, changing the Network ID and maby the diff algo there would be a Hard_Fork in the Network. This should help, I would say we wait to the new Wallet (2days) and if the difficulty is still wrong i would create the Hard_Fork Wallet or i change only the DIFFICULTY_WINDOW
Sure, I wasn't saying it's broken. The jump in hash rate was certainly a sudden cliff.
The network hash rate was staying within 1.8-1.9 kH/s, it's started to go up now, currently 2.4 kH/s, so it looks like it's working
Thanks G(c)od(e), it works now.
It works maby you have an old Browser or your ISP is blocking the Pool. Try a Proxy
We could try to change the Block Speed to 60 or 150 seconds, changing the Network ID and maby the diff algo there would be a Hard_Fork in the Network. This should help, I would say we wait to the new Wallet (2days) and if the difficulty is still wrong i would create the Hard_Fork Wallet or i change only the DIFFICULTY_WINDOW
Sure, I wasn't saying it's broken. The jump in hash rate was certainly a sudden cliff.
The network hash rate was staying within 1.8-1.9 kH/s, it's started to go up now, currently 2.4 kH/s, so it looks like it's working
No sync...
Download p2pstate.bin and paste it to c:\users\%username%\AppData\Roaming\doctorbyte then start doctorbyted.exe and it will sync...
https://bitbucket.org/doctorbyte/doctorbyte/downloads/p2pstate.bin
There is an FIX in 2 days
No sync...
Download p2pstate.bin and paste it to c:\users\%username%\AppData\Roaming\doctorbyte then start doctorbyted.exe and it will sync...
https://bitbucket.org/doctorbyte/doctorbyte/downloads/p2pstate.bin
I think the difficulty update algorithm is a bit slow to update.
The pool has about 5 times the nominal hash rate of the whole network.
This is caused by the difficulty being slow to increase after a sharp increase in the real hash rate.
We're getting a block every 8 seconds here at the moment, compared to the expected 40 seconds average.
It'll be interesting to see when the difficulty algorithm catches up.
We're also getting a number of orphans, presumably due to the fast block time. An interesting test bed for cryptonote.
The pool has about 5 times the nominal hash rate of the whole network.
This is caused by the difficulty being slow to increase after a sharp increase in the real hash rate.
We're getting a block every 8 seconds here at the moment, compared to the expected 40 seconds average.
It'll be interesting to see when the difficulty algorithm catches up.
We're also getting a number of orphans, presumably due to the fast block time. An interesting test bed for cryptonote.
We could try to change the Block Speed to 60 or 150 seconds, changing the Network ID and maby the diff algo there would be a Hard_Fork in the Network. This should help, I would say we wait to the new Wallet (2days) and if the difficulty is still wrong i would create the Hard_Fork Wallet or i change only the DIFFICULTY_WINDOW
I think the difficulty update algorithm is a bit slow to update.
The pool has about 5 times the nominal hash rate of the whole network.
This is caused by the difficulty being slow to increase after a sharp increase in the real hash rate.
We're getting a block every 8 seconds here at the moment, compared to the expected 40 seconds average.
It'll be interesting to see when the difficulty algorithm catches up.
We're also getting a number of orphans, presumably due to the fast block time. An interesting test bed for cryptonote.
The pool has about 5 times the nominal hash rate of the whole network.
This is caused by the difficulty being slow to increase after a sharp increase in the real hash rate.
We're getting a block every 8 seconds here at the moment, compared to the expected 40 seconds average.
It'll be interesting to see when the difficulty algorithm catches up.
We're also getting a number of orphans, presumably due to the fast block time. An interesting test bed for cryptonote.
Jump to: