Solo + p2pool roation - cgminer

[rav3n_pl]

I have a question.
My 6770 getting about 180MH/s so I decided to try lottery (solo mining) aside of p2pool.
I run cgminer this way:
cgminer-2.3.6-win32\cgminer.exe --rotate 5  --no-adl -I 3 -u user -p pass -o http://127.0.0.1:8332 -u rav3n -p nn -o http://127.0.0.1:9332
8332 is a bitcoin (solo)
9332 is a p2pool

It looks to me, that when it is switched to 8332 it is still getting new longpool works from 9332 but not longpool resets - producing rejects one after another (ST is rising all the time when connected to 8332).
IMO it should NOT getting nothing from 9332 LP or get all longpool commands form it.

Code:

 cgminer version 2.3.6 - Started: [2012-04-29 11:55:19]
--------------------------------------------------------------------------------
 (5s):176.2 (avg):180.3 Mh/s | Q:72  A:0  R:2  HW:0  E:0%  U:0.0/m
 TQ: 1  ST: 41  SS: 0  DW: 3  NB: 1  LW: 0  GF: 0  RF: 0
 Connected to http://127.0.0.1:8332 with LP as user rav3n
 Block: 00000615c7cce1322c413caf39f117db...  Started: [11:55:19]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: 181.5/182.3Mh/s | A:0 R:2 HW:0 U:0.00/m I: 3
--------------------------------------------------------------------------------

 [2012-04-29 11:55:18] Started cgminer 2.3.6
 [2012-04-29 11:55:19] Found 0 ztex board(s)
 [2012-04-29 11:55:19] Probing for an alive pool
 [2012-04-29 11:55:19] No suitable long-poll found for pool http://127.0.0.1:8332
 [2012-04-29 11:55:22] Pool 0 http://127.0.0.1:8332 alive
 [2012-04-29 11:55:22] Pool 1 http://127.0.0.1:9332 alive
 [2012-04-29 11:55:22] Long-polling activated for http://127.0.0.1:9332/long-polling
 [2012-04-29 11:56:18] Rejected 68ab6802.da4dfeff GPU 0 pool 1
 [2012-04-29 11:56:19] Long-polling activated for pool http://127.0.0.1:8332 via http
://127.0.0.1:9332/long-polling
 [2012-04-29 11:58:16] Rejected 6789cbea.6e988e12 GPU 0 pool 1


 cgminer version 2.3.6 - Started: [2012-04-29 11:55:19]
--------------------------------------------------------------------------------
 (5s):181.3 (avg):179.7 Mh/s | Q:138  A:3  R:3  HW:0  E:2%  U:0.5/m
 TQ: 2  ST: 4  SS: 0  DW: 94  NB: 2  LW: 13  GF: 0  RF: 0
 Connected to http://127.0.0.1:9332 with LP as user rav3n
 Block: 000009a1c1d92998f549588a45b7e02e...  Started: [12:00:15]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: 178.1/181.0Mh/s | A:4 R:3 HW:0 U:0.69/m I: 3
--------------------------------------------------------------------------------

 [2012-04-29 12:00:34] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:34] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:39] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:39] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:52] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:52] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:56] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:00:56] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:01] Accepted ce4d4ff3.b8a07fa9 GPU 0 pool 1
 [2012-04-29 12:01:03] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:03] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:05] Accepted e35005b0.4fb698ed GPU 0 pool 1
 [2012-04-29 12:01:06] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:06] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:08] Accepted 08d7c611.25c7d735 GPU 0 pool 1
 [2012-04-29 12:01:12] Accepted c81961ef.0d39cb84 GPU 0 pool 1
 [2012-04-29 12:01:13] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:01:13] LONGPOLL from pool 1 requested work restart

 cgminer version 2.3.6 - Started: [2012-04-29 11:55:19]
--------------------------------------------------------------------------------
 (5s):184.8 (avg):177.0 Mh/s | Q:357  A:12  R:8  HW:0  E:3%  U:0.8/m
 TQ: 2  ST: 4  SS: 0  DW: 238  NB: 2  LW: 53  GF: 0  RF: 0
 Connected to http://127.0.0.1:9332 with LP as user rav3n
 Block: 000009a1c1d92998f549588a45b7e02e...  Started: [12:00:15]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: 175.5/177.0Mh/s | A:12 R:8 HW:0 U:0.76/m I: 3
--------------------------------------------------------------------------------

 [2012-04-29 12:04:35] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:04:35] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:04:50] Accepted e21a4f4b.4dc06629 GPU 0 pool 1
 [2012-04-29 12:04:52] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:04:52] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:05:28] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:05:28] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:05:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:05:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:05:42] Switching to http://127.0.0.1:8332
 [2012-04-29 12:06:48] Rejected 64925d81.ce5c01c9 GPU 0 pool 1
 [2012-04-29 12:08:22] Rejected 572279b5.61cac453 GPU 0 pool 1
 [2012-04-29 12:08:32] Rejected 556a41ee.ba4efcd9 GPU 0 pool 1
 [2012-04-29 12:10:11] Rejected 679c5f04.3a787434 GPU 0 pool 1
 [2012-04-29 12:10:26] Rejected ab41137c.ecf79943 GPU 0 pool 1
 [2012-04-29 12:10:52] Switching to http://127.0.0.1:9332
 [2012-04-29 12:11:06] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:11:06] LONGPOLL from pool 1 requested work restart

 cgminer version 2.3.6 - Started: [2012-04-29 11:55:19]
--------------------------------------------------------------------------------
 (5s):180.5 (avg):176.6 Mh/s | Q:459  A:20  R:9  HW:0  E:4%  U:0.9/m
 TQ: 2  ST: 17  SS: 0  DW: 340  NB: 3  LW: 112  GF: 0  RF: 0
 Connected to http://127.0.0.1:8332 with LP as user rav3n
 Block: 0000058aa86cb9c14a8c9f239ca0cdf6...  Started: [12:16:08]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: 181.5/176.9Mh/s | A:20 R:9 HW:0 U:0.94/m I: 3
--------------------------------------------------------------------------------

 [2012-04-29 12:14:48] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:14:48] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:08] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:08] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:18] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:18] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:30] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:30] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:38] Accepted d445d664.c921e2ae GPU 0 pool 1
 [2012-04-29 12:15:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:00] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:00] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:02] Accepted 3d3a090e.b69fc955 GPU 0 pool 1
 [2012-04-29 12:16:02] Switching to http://127.0.0.1:8332
 [2012-04-29 12:16:06] Accepted 443cb3cf.36b05263 GPU 0 pool 1
 [2012-04-29 12:16:08] LONGPOLL from pool 1 detected new block
 [2012-04-29 12:16:21] Rejected 4a3aab37.77f73240 GPU 0 pool 1

 cgminer version 2.3.6 - Started: [2012-04-29 11:55:19]
--------------------------------------------------------------------------------
 (5s):182.7 (avg):176.8 Mh/s | Q:478  A:20  R:12  HW:0  E:4%  U:0.9/m
 TQ: 1  ST: 28  SS: 0  DW: 342  NB: 3  LW: 112  GF: 0  RF: 0
 Connected to http://127.0.0.1:8332 with LP as user rav3n
 Block: 0000058aa86cb9c14a8c9f239ca0cdf6...  Started: [12:16:08]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0: 182.2/177.1Mh/s | A:20 R:12 HW:0 U:0.88/m I: 3
--------------------------------------------------------------------------------

 [2012-04-29 12:15:08] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:18] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:18] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:30] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:30] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:38] Accepted d445d664.c921e2ae GPU 0 pool 1
 [2012-04-29 12:15:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:15:42] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:00] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:00] LONGPOLL from pool 1 requested work restart
 [2012-04-29 12:16:02] Accepted 3d3a090e.b69fc955 GPU 0 pool 1
 [2012-04-29 12:16:02] Switching to http://127.0.0.1:8332
 [2012-04-29 12:16:06] Accepted 443cb3cf.36b05263 GPU 0 pool 1
 [2012-04-29 12:16:08] LONGPOLL from pool 1 detected new block
 [2012-04-29 12:16:21] Rejected 4a3aab37.77f73240 GPU 0 pool 1
 [2012-04-29 12:16:54] Rejected ab491e32.d193c100 GPU 0 pool 1
 [2012-04-29 12:17:30] Rejected e28c40e0.f5110ff6 GPU 0 pool 1
 [2012-04-29 12:17:48] Rejected 7ca983c4.59160c69 GPU 0 pool 1

I have run something wrong or better to run 2 miners one for solo and second for pool?

[1714794265]

1714794265

[1714794265]

1714794265

[1714794265]

1714794265

[1714794265]

1714794265

[kinlo]

A few remarks:

- Solo mining using bitcoin is not optimal: bitcoind does NOT support longpoll.  So doing solo mining directly on the bitcoin daemon is less optimal as you will do some work on old work

- Afaik cgminer tries to be smart and use all pools to see when a new block is present, and use that to trigger new getwork from other pools.  In other words, this is an advantage as it will compensate the missing LP from the bitcoin client

- 180 MH/s is not enough to do solo mining.  You're better of mining in a pool.  Your variance will be too high.

- You should consider p2pool as solo mining: higer profits with higher variance.  I would only use a real pool if I'd only have 180MH/s, as p2pool has a higher difficulty.

[Red Emerald]

- You should consider p2pool as solo mining: higer profits with higher variance.  I would only use a real centralized pool if I'd only have 180MH/s, as p2pool has a higher difficulty.

FTFY

[rav3n_pl]

- 180 MH/s is not enough to do solo mining.  You're better of mining in a pool.  Your variance will be too high.

I`m getting about 0.015 BTC per block... it is 10x more than i get from slush pool. But still to make 50BTC i need 9 YEARS of pooled mining. Thats why i want to try solo aside of pool.

[Red Emerald]

- 180 MH/s is not enough to do solo mining.  You're better of mining in a pool.  Your variance will be too high.

I`m getting about 0.015 BTC per block... it is 10x more than i get from slush pool. But still to make 50BTC i need 9 YEARS of pooled mining. Thats why i want to try solo aside of pool.

Just FYI, that is the exact opposite reason most people solo mine. You you will likely never see any BTC. And definitely none before the reward halves in December.

[rav3n_pl]

Thats why I want to switch between solo and pool.
It is even funniest in 2.3.3
When I switch to solo (or even DISABLE pool in options) it is still getting LP messages and sending shares to pool!
I`m just curious what happen when I found block by accident? It will be send to me (as solo) or to pool?

[Gladamas]

- 180 MH/s is not enough to do solo mining.  You're better of mining in a pool.  Your variance will be too high.

I agree. You should not solo mine if you want any return in the near future.

To prove this point, let's do the math:

• The current difficulty is ~1508590.
• This means that for every share with difficulty of 1, there is a 1/1,508,590 chance of it being a block.
• For shares with a difficulty of 1 there is a 1/(16^8) or 1/4,294,967,296 of any computed hash being a share.
• At 180,000,000 hashes/second, on average it will take (4,294,967,296*1,508,590)/180,000,000 seconds (of continuous 24/7 mining) to find a block.
• That is 35996360 seconds, or ~416 days (1 year + 1 month + 20 days) to find a block. By then the difficulty would have increased drastically, and you will get only 25 bitcoins for your over 1 year of mining because of the reward halving in December.

Do you still want to solo mine? If so, I would look on the CGMiner thread (https://bitcointalk.org/index.php?topic=28402.0) for how to set it up properly. Otherwise I would recommend a pool with merged (Bitcoin+Namecoin) mining where you can set your donation/fee percentage, such as EclipseMC (https://eclipsemc.com/) or Ozcoin (http://ozco.in/). I would not recommend P2Pool for your current setup, because of the increased difficulty for shares (600 vs. 1).

[-ck]

When you run connected to a pool/server that doesn't support longpoll, cgminer will find a longpoll from another server and use that to help it detect block changes (as kinlo said). Also, some work will always go to the backup pools (which is why you still get accepted shares from p2pool while connected to your bitcoind) unless you enable the --failover-option. The  large number of longpolls is perfectly normal on p2pool.

[rav3n_pl]

When you run connected to a pool/server that doesn't support longpoll, cgminer will find a longpoll from another server and use that to help it detect block changes (as kinlo said). Also, some work will always go to the backup pools (which is why you still get accepted shares from p2pool while connected to your bitcoind) unless you enable the --failover-option. The  large number of longpolls is perfectly normal on p2pool.

Thanks for info
My question stays: if I`m connected to bicoind and p2pool is longpooling when I found block where it will be sent? Directly to bicoind and count as mine only or to pool?
I`m currently using cgminer 2.3.3 where I can even DISABLE p2pool from pool menu and it is still working, longpool is sending data and miner is sending shares...

[energiel]

Normally the block will be send to your bitcoind, where your miner get the work, the longpool message from p2pool is just used to get fresh work for your miner from bitcoind.
But not sure it's a good idea, because you will get half the revenue from p2pool and very title chance to find a block in solo,  may be your lucky enough can try !

[rav3n_pl]

Yes, I know this is loooooongshoot, but I`m getting 0.01-0.02/block on pool so.... ;]

[-ck]

Yes, I know this is loooooongshoot, but I`m getting 0.01-0.02/block on pool so.... ;]

bitcoind does not accept "shares", only p2pool does. If you're mining in bitcoind, it only accepts block attempts and nothing else. If you're mining on both bitcoind and p2pool, then you'll see shares going to p2pool and pretty much nothing while you're on bitcoind unless you hit the jackpot. The longpolls will keep coming in and that has pretty much nothing to do with bitcoind since they're coming from p2pool, and when a longpoll comes in, some work is sneaking to p2pool in the process. In short, these miniscule amounts you're earning are coming from p2pool. If you found a block, cgminer would also add the words BLOCK! to a share, and you'd earn 50+ BTC.