69 Ghash/sec .... and climbing.
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
nope, all fine and under control
Topic: [CLOSED] BTCMine - ZERO fee mining pool (LP, SSL, JSON API, P2SH) - page 31. (Read 171605 times)
May 09, 2011, 12:55:21 AM
nope, all fine and under control
May 09, 2011, 12:25:02 AM
it felt cozier when it was sub 20 Gh/s =O
May 09, 2011, 12:12:52 AM
Gonna migrate here from deepbit to help balance the networks a bit.
May 08, 2011, 09:12:55 PM
69 Ghash/sec .... and climbing.
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
Everything is working fine for me
May 08, 2011, 09:05:25 PM
69 Ghash/sec .... and climbing.
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
... any warning lights flashing, rivets or screws popping out yet dbitcoin??
May 08, 2011, 01:52:34 PM
Backend error - what this about (crach in GUIminer v2011-05-01) 
server restarted. 
May 08, 2011, 01:28:38 PM
Backend error - what this about (crach in GUIminer v2011-05-01)
May 08, 2011, 01:08:24 PM
There is some issues with bitcoind and LP, I will fix this after 10 may.
May 08, 2011, 11:27:58 AM
I'm consistently seeing my miner submit one or more invalid/stale shares after the pool finds a new block, sometimes up to 1 minute after the "long poll: new block" message appeared. Could this be a possible problem with the server? It doesn't happen in other pools.
Yes, I am seeing near 1% right now. It is almost as if long polling isn't even working.
May 08, 2011, 11:05:26 AM
Tyran,
Almost all of my rejected shares come after an LP:new work pushed
Up to one rejected share after a new block is expected because of network latency, and because most miners still submit found shares from kernel executions that were in progress while new work was pushed.Almost all of my rejected shares come after an LP:new work pushed
What I'm seeing is 2-3 invalid, so it looks like the server is sending invalid work. I'm not 100% sure, but it appears to affect only blocks found by the pool, so it's not a big deal
May 08, 2011, 10:12:55 AM
Tyran,
Almost all of my rejected shares come after an LP:new work pushed
Almost all of my rejected shares come after an LP:new work pushed
May 08, 2011, 10:11:12 AM
I'm consistently seeing my miner submit one or more invalid/stale shares after the pool finds a new block, sometimes up to 1 minute after the "long poll: new block message" appeared. Could this be a possible problem with the server? It doesn't happen in other pools.
Well, there is always Deepbit.
May 08, 2011, 08:26:26 AM
I'm consistently seeing my miner submit one or more invalid/stale shares after the pool finds a new block, sometimes up to 1 minute after the "long poll: new block" message appeared. Could this be a possible problem with the server? It doesn't happen in other pools.
May 08, 2011, 06:14:54 AM
But not in the case if LP not enabled for 'unknown' miner.
Are you saying you're UA snooping to enable and disable LP support? Don't do that.
May 08, 2011, 04:29:49 AM
Either way, 5 is already the default, and when LP turns on it completely ignores it. -g is simply not needed.
But not in the case if LP not enabled for 'unknown' miner.
Anyway, with LP this option just ignored, so there is no problem
May 08, 2011, 04:10:41 AM
Nah, they are not competing since in the end they both get paid for the work they have done. It is just another route to get onto the btc network that pays differently, i.e. diversification. If you have two rigs both going solo on the network, or even just two GPU nodes, sure they are competing on the same problem but you are getting paid for both their work eventually .... unless you are a really, really unlucky mofo.
You only get paid when the pool gets paid for finding a block solution. So if pool one finds the block with your miner, then the other pool isn't paid. The only exception is paid per share. So yes, they are competing, even if it is insignificant (with large pools anyway).
The other pool will eventually find a block as well. It will find it in a proportionally larger amount of time to the amount of hash power you are contributing to the first pool. The first pool finds its block in a proportionally smaller amount of time. You have the same EV no matter what, because you are contributing hashes to the network, not any one pool. A hash is worth the same amount whether it is contributed to any pool (less fees) or solo mining.
You are never competing. You can be said to be "competing" to find the next block, just like how mining works as a whole, but you are not affecting your EV in any way whether you solo mine, join one pool, or join two, or fifty. All a larger pool does for you is decrease variance.
May 08, 2011, 03:25:03 AM
Hey dbitcoin
Change the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
okChange the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
*cough* You forgot to remove -g 5 from both lines.
Nope
Read PM please.
Either way, 5 is already the default, and when LP turns on it completely ignores it. -g is simply not needed.
May 08, 2011, 03:21:07 AM
Hey dbitcoin
Change the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
okChange the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
*cough* You forgot to remove -g 5 from both lines.
Nope
Read PM please.
May 08, 2011, 02:45:38 AM
Hey dbitcoin
Change the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
okChange the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5 from the Linux command line (not only is 5 the default, my miner supports LP).
*cough* You forgot to remove -g 5 from both lines.
May 07, 2011, 11:53:30 PM
Hey dbitcoin
Change the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5[/-i] from the Linux command line (not only is 5 the default, my miner supports LP).
okChange the Windows instructions for my miner to DiabloMiner-Windows.exe -u your-login@miner-name -p miner-password -o btcmine.com -r 8332 and remove -g 5[/-i] from the Linux command line (not only is 5 the default, my miner supports LP).
Jump to: