Bitcoin Forum
December 03, 2016, 06:48:24 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 [358] 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2028804 times)
IYFTech
Hero Member
*****
Offline Offline

Activity: 686


WANTED: Active dev to fix & re-write p2pool in C


View Profile
December 09, 2013, 12:43:32 PM
 #7141

I think I get it. Sounds OK to my non tech head anyway - at least it's a start..... Grin

-- Smiley  Thank you for smoking  Smiley --  If you paid VAT to dogie for items you should read this thread:  https://bitcointalk.org/index.php?topic=1018906.0
1480747704
Hero Member
*
Offline Offline

Posts: 1480747704

View Profile Personal Message (Offline)

Ignore
1480747704
Reply with quote  #2

1480747704
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480747704
Hero Member
*
Offline Offline

Posts: 1480747704

View Profile Personal Message (Offline)

Ignore
1480747704
Reply with quote  #2

1480747704
Report to moderator
1480747704
Hero Member
*
Offline Offline

Posts: 1480747704

View Profile Personal Message (Offline)

Ignore
1480747704
Reply with quote  #2

1480747704
Report to moderator
1480747704
Hero Member
*
Offline Offline

Posts: 1480747704

View Profile Personal Message (Offline)

Ignore
1480747704
Reply with quote  #2

1480747704
Report to moderator
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
December 09, 2013, 12:44:27 PM
 #7142

How many times must I say I was on p2pool for months and months. How long is "over time"?

I would go with "over time" = at least 100 times whatever your expected time to find a share is.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
December 09, 2013, 12:50:37 PM
 #7143

As you see, p2pool is not good for small miners anymore.

p2pool have never been good for small miners.  All that has changed is how much hashrate qualifies as a "small miner".  Bitcoin difficulty has increased 1000x in the last 18 months.  Today's 10 GH/s miner is just as screwed as a 10 MH/s miner from 18 months ago.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
December 09, 2013, 01:04:48 PM
 #7144

But, now difficulty has hit the threshold where I will always make more on BTCGuild with less power on it than I do at p2pool.

There is no such threshold.  Well, there might be one down in the 0-10 megahash range with the CPUs where the expected number of shares earned between now and infinity is less than a half.  But 20 Ghash/sec is nowhere near that.  Once again, I'm mining with about 7 Ghash/sec, and while I see plenty of variance, sometimes going 4 or 5 days without a payout, I still get paid, and my running averages are hovering rather close to my ideal expected payout.  (I'm actually up a fair bit right now because I had shares active during the very recent string of crazy good luck, including that block with the 20 BTC fee.)

p2pcoin: a USB/CD/PXE p2pool miner - 1N8ZXx2cuMzqBYSK72X4DAy1UdDbZQNPLf - todo
I routinely ignore posters with paid advertising in their sigs.  You should too.
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
December 09, 2013, 02:56:39 PM
 #7145

But, now difficulty has hit the threshold where I will always make more on BTCGuild with less power on it than I do at p2pool.

There is no such threshold.  Well, there might be one down in the 0-10 megahash range with the CPUs where the expected number of shares earned between now and infinity is less than a half.  But 20 Ghash/sec is nowhere near that.  Once again, I'm mining with about 7 Ghash/sec, and while I see plenty of variance, sometimes going 4 or 5 days without a payout, I still get paid, and my running averages are hovering rather close to my ideal expected payout.  (I'm actually up a fair bit right now because I had shares active during the very recent string of crazy good luck, including that block with the 20 BTC fee.)

Well goody for you... you seem to be the only one... read all the posts above yours and you'll see what the threshold is.  Glad you're getting something.  I was not... so for me the decision was easy since I already had some test miners on other pools types that made more with less power over the course of months.

Good luck.  Hope you keep getting lucky.

maqifrnswa
Sr. Member
****
Offline Offline

Activity: 454


View Profile
December 09, 2013, 03:13:12 PM
 #7146

But, now difficulty has hit the threshold where I will always make more on BTCGuild with less power on it than I do at p2pool.

There is no such threshold.  Well, there might be one down in the 0-10 megahash range with the CPUs where the expected number of shares earned between now and infinity is less than a half.  But 20 Ghash/sec is nowhere near that.  Once again, I'm mining with about 7 Ghash/sec, and while I see plenty of variance, sometimes going 4 or 5 days without a payout, I still get paid, and my running averages are hovering rather close to my ideal expected payout.  (I'm actually up a fair bit right now because I had shares active during the very recent string of crazy good luck, including that block with the 20 BTC fee.)

Well goody for you... you seem to be the only one... read all the posts above yours and you'll see what the threshold is.  Glad you're getting something.  I was not... so for me the decision was easy since I already had some test miners on other pools types that made more with less power over the course of months.

Good luck.  Hope you keep getting lucky.

I solo mined and found a block in 30 minutes. Over the same time I only earned 0.000002 BTC on BTCGuild. Solo mining is WAY better than any pool! You get paid SO MUCH more solo mining.

that is the logical equivalent of what you're saying. kjj is right, there is no threshold. The only threshold is how much variance is worth to you. When you cross that threshold, like you found, it is no longer fun to mine on p2pool. It's ok, p2pool has high variance for small miners - and to many/most it is not worth it. I'm a huge fan of p2pool, but I stopped since my personal value of variance is exceeding my interest in p2pool
Schleicher
Hero Member
*****
Offline Offline

Activity: 630



View Profile
December 09, 2013, 05:24:57 PM
 #7147

I would go with "over time" = at least 100 times whatever your expected time to find a share is.
In lenny's example that would be 17 years.

Bitcoin donations: 1H2BHSyuwLP9vqt2p3bK9G3mDJsAi7qChw
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
December 09, 2013, 06:16:13 PM
 #7148

Ok, I guess "Threshold" is a bad word...

How about this.

There's Variance, and then there's "A Snowball's Chance in Hell".

Right now at my Hashrate based on my experience with the difficulty rises over the last few months, I've gradually crossed over into "A Snowball's Chance in Hell" of getting a regular share and payout.  

Meanwhile in BTC Guild... I currently get 12564 - 13168 shares per round with my miniscule output, so I'm virtually guaranteed a reward even if it's theoretically lower than what would have gotten if I win the Lotto and somehow out of the blue get one measly share within a 24 hour period on P2Pool.  You're right, I might as well have run Solo.... oh wait, there are other choices for us lowly bottom feeders.  

How's that sound?

A year ago, did anyone in this forum think that a miner running around 100Ghs and lower would be considered a bottom feeder?

twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
December 09, 2013, 06:17:45 PM
 #7149

I would go with "over time" = at least 100 times whatever your expected time to find a share is.
In lenny's example that would be 17 years.

Yes, and in that example case making any statement of "what I earned over the past couple months" is not statistically meaningful.

That example was for 322 MH/s which is insanely small given current bitcoin difficulties.  The only reason to be mining with 300 MH/s at all is if you are betting on another 100-fold increase in the BTC/USD exchange rate making your handful of satoshis valuable someday.  Or alternatively if you don't care about profits and are just mining for the fun of it.  Whatever the reason, definitely don't bother mining on p2pool with that amount of hashrate.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
December 09, 2013, 06:32:31 PM
 #7150

I would go with "over time" = at least 100 times whatever your expected time to find a share is.
In lenny's example that would be 17 years.

Yes, and in that example case making any statement of "what I earned over the past couple months" is not statistically meaningful.

That example was for 322 MH/s which is insanely small given current bitcoin difficulties.  The only reason to be mining with 300 MH/s at all is if you are betting on another 100-fold increase in the BTC/USD exchange rate making your handful of satoshis valuable someday.  Or alternatively if you don't care about profits and are just mining for the fun of it.  Whatever the reason, definitely don't bother mining on p2pool with that amount of hashrate.

Perfect pool should be profitable for any miner. p2pool is very unfriendly for anything smaller than 10-30 GH/s. I am working to change that - for future of p2pool, which can do good for any miner on the planet, using distributed p2p network of miners. Right now you make profit only if you have lots of expensive ASIC miners.
And yes, I am mining for fun, not for profits - all my Jupiters are sitting on Eligius pool.
K1773R
Legendary
*
Offline Offline

Activity: 1526


/dev/null


View Profile
December 09, 2013, 06:44:42 PM
 #7151

I would go with "over time" = at least 100 times whatever your expected time to find a share is.
In lenny's example that would be 17 years.

Yes, and in that example case making any statement of "what I earned over the past couple months" is not statistically meaningful.

That example was for 322 MH/s which is insanely small given current bitcoin difficulties.  The only reason to be mining with 300 MH/s at all is if you are betting on another 100-fold increase in the BTC/USD exchange rate making your handful of satoshis valuable someday.  Or alternatively if you don't care about profits and are just mining for the fun of it.  Whatever the reason, definitely don't bother mining on p2pool with that amount of hashrate.

Perfect pool should be profitable for any miner. p2pool is very unfriendly for anything smaller than 10-30 GH/s. I am working to change that - for future of p2pool, which can do good for any miner on the planet, using distributed p2p network of miners. Right now you make profit only if you have lots of expensive ASIC miners.
And yes, I am mining for fun, not for profits - all my Jupiters are sitting on Eligius pool.
how about taking a look at what variance is? if you would read and understand it, you would see your wrong...

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
wlz2011
Member
**
Offline Offline

Activity: 71


View Profile
December 09, 2013, 07:29:59 PM
 #7152

P2Pool release 13.4 - commit hash: 8e7cb8223a38bdd4ff55971d2945f5ccb571e063

Windows binary: http://u.forre.st/u/wftncvpn/p2pool_win32_13.4.zip
Windows binary signature: http://u.forre.st/u/eoietnxc/p2pool_win32_13.4.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.4
Source tarball: https://github.com/forrestv/p2pool/tarball/13.4

Changes:
* Require Litecoin >=0.8.5.1
* Warn about old versions of Bitcoin and Terracoin
* Many improvements to web interface and graphs
* Fixed error messages being created in bitcoind's debug.log due to invalid message being sent

P2Pool is a decentralized pool that works by creating a P2P network of miner nodes. These nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself. There is no central point of failure, making it DoS resistant.

Related:
P2Pool homepage: http://p2pool.in/
P2Pool stats page, made by twmz: http://p2pool.info/
P2Pool subsidies - Several people are donating to all people using P2Pool in order to promote its decentralized nature - https://bitcointalk.org/index.php?topic=57027.0
Litecoin P2Pool status - http://p2pool.litecointools.com/

Things that are not P2Pool (and just people running P2Pool): p2pool.org

Graphs: http://p2pool.info/ http://forre.st:9332/

P2Pool wiki page | GitHub project page
New: Mailing list for urgent news (updates, bugs): http://groups.google.com/group/p2pool-notifications

List of all blocks found: http://blockexplorer.com/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4

Getting P2Pool

  • Run bitcoin with the RPC interface enabled - see the next section for instructions on how to do this
  • Download p2pool: (see links at top for binaries!)
    • git: git clone git://github.com/forrestv/p2pool.git
  • Run p2pool:
    • Windows py2exe: run_p2pool.exe
    • Source: python run_p2pool.py
  • Run a miner daemon (see https://en.bitcoin.it/wiki/P2Pool#Miners ) with long polling connecting to 127.0.0.1 on port 9332 with any username and password
    • With all miners, using a high FPS target (30?) or a low intensity (7?) helps a lot with reducing stales.

HOWTO: Bitcoin server mode
You must be running the Bitcoin client, and it must have its RPC interface enabled.

Open the Bitcoin data folder. See https://en.bitcoin.it/wiki/Data_directory

Make a new file named bitcoin.conf (not bitcoin.conf.txt! You might have to go into Control Panel > Appearance and Personalization > Folder Options > View and uncheck 'Hide extensions for known file types'). Paste this into it:

rpcpassword=<A LONG RANDOM PASSWORD THAT YOU DON'T HAVE TO REMEMBER>
server=1


Dependencies for running FROM SOURCE:
  • Bitcoin 0.5.0 or higher
  • Python 2.5 or higher
  • python-argparse for Python 2.6 and lower
  • Twisted (Ubuntu package python-twisted)

Additional options of interest:
    -w PORT: Listen for workers on a port other than 9332.
    -a BITCOIN_ADDRESS: Mine to this address instead of requesting one from Bitcoin.

Last, forward port 9333 through your firewall to the host running p2pool! (Oh, and join #p2pool on freenode!)


嗨,你好!
你不觉得分配制度出问题了吗?110G阿瓦隆没有收获,其它的小算力也支撑不了多久。而难度已经要900M, Share difficulty: 478000,你一天能挖到多少SHARE ?如果我把中国的P2POOL节点矿池关闭,至少有15T算力丢失。而更多的算力也将会陆续丢失。我一直努力尝试让更多人使用P2POOL,但是我失望了。请考虑降低SHARE难度,Share difficulty: 500000在我的矿池4T算力,竟然一小时都很难挖到SHARE。如果这种情况不能得到改善,我和伙伴们2个多月的努力将会丢失。而P2POOL也将损失更多算力,最终会因此而灭亡。希望你能考虑降低Share difficulty。


非常抱歉,我不得不使用谷歌翻译。


http://lis1718.com:9332

来自中国的P2POOL爱好者。

Hi, hello!
Do not you think the distribution system wrong? 110G Avalon no gain, other small force also can not count how long. The difficulty has been to 900M, Share difficulty: 478000, how much of your day can be dug SHARE? If I put mine in China P2POOL node pool is closed, at least 15T force lost count. And more force will also continue to lose count. I have been trying to make more people use P2POOL, but I was disappointed. Please consider reducing the difficulty of SHARE, Share difficulty: 500000 4T pool in my mine operator force, even one hour are hard to dig SHARE. If this situation does not improve, I and partners over two months of hard work will be lost. And P2POOL will lose count more force will thus eventually perish. I hope you can consider reducing Share difficulty.


Very sorry, I had to use Google Translate.


http://lis1718.com:9332

From China P2POOL enthusiasts.
Polyatomic
Sr. Member
****
Offline Offline

Activity: 256


View Profile
December 11, 2013, 01:57:07 PM
 #7153

Quote
Do not you think the distribution system wrong? 110G Avalon no gain, other small force also can not count how long. The difficulty has been to 900M, Share difficulty: 478000, how much of your day can be dug SHARE? If I put mine in China P2POOL node pool is closed, at least 15T force lost count. And more force will also continue to lose count. I have been trying to make more people use P2POOL, but I was disappointed. Please consider reducing the difficulty of SHARE, Share difficulty: 500000 4T pool in my mine operator force, even one hour are hard to dig SHARE. If this situation does not improve, I and partners over two months of hard work will be lost. And P2POOL will lose count more force will thus eventually perish. I hope you can consider reducing Share difficulty.

Just keep mining man , the minimum share diff always goes up and down. Your Avalon will still get shares.
nibor
Sr. Member
****
Offline Offline

Activity: 348


View Profile
December 11, 2013, 10:14:45 PM
 #7154

I am suggesting to change this behaviour to formula:

* If address (miner) is finding shares in less than 60 minutes, increase his node share diff so he will find share in exactly 60 minutes

This will be independent from current pool hashrate, last implementation (percentage of pool hashrate) doesn't work anymore with such big miners we have there now.

Avg. of 24 beefy shares per day will be enough even for largest miners, they shouldn't complain about variance, as their sacrifice will enable small miners to mine again on p2pool, total pool hashrate will increase, so total variance for pool will decrease (profit for all miners).

What you guys think?

Rather than 60 mins a share you should do 60 shares (or fewer) in the paying sharechain? As if p2pool gets very large the 3 block window could reduce to an hour or 2. And then 60 mins per share will mean big miners do not get enough shares to and we will lose the big miners too!
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
December 12, 2013, 01:09:36 AM
 #7155

I got error when I found a share today:
Code:
2013-12-12 01:01:36.423805 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:36.423930  Local: 2356GH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:36.423978  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:36.424015  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:39.436918 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:39.437093  Local: 2357GH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:39.437174  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:39.437264  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:41.593547 GOT SHARE! Jupiter 23877a5a prev a9d32777 age 80.86s
2013-12-12 01:01:41.622728 > Error while processing Event callbacks:
2013-12-12 01:01:41.622811 > Traceback (most recent call last):
2013-12-12 01:01:41.622846 >   File "/home/user/p2pool/p2pool/bitcoin/worker_interface.py", line 136, in <lambda>
2013-12-12 01:01:41.622882 >     lambda header, user, coinbase_nonce: handler(header, user, pack.IntType(self._my_bits).pack(nonce) + coinbase_nonce),
2013-12-12 01:01:41.622915 >   File "/home/user/p2pool/p2pool/work.py", line 403, in got_response
2013-12-12 01:01:41.622981 >     self.node.set_best_share()
2013-12-12 01:01:41.623012 >   File "/home/user/p2pool/p2pool/node.py", line 297, in set_best_share
2013-12-12 01:01:41.623043 >     self.best_share_var.set(best)
2013-12-12 01:01:41.623073 >   File "/home/user/p2pool/p2pool/util/variable.py", line 74, in set
2013-12-12 01:01:41.623103 >     self.changed.happened(value)
2013-12-12 01:01:41.623133 > --- <exception caught here> ---
2013-12-12 01:01:41.623162 >   File "/home/user/p2pool/p2pool/util/variable.py", line 42, in happened
2013-12-12 01:01:41.623192 >     func(*event)
2013-12-12 01:01:41.623232 >   File "/home/user/p2pool/p2pool/node.py", line 96, in broadcast_share
2013-12-12 01:01:41.623271 >     peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.valu
e, include_txs_with=[share_hash])
2013-12-12 01:01:41.623322 >   File "/home/user/p2pool/p2pool/p2p.py", line 291, in sendShares
2013-12-12 01:01:41.623355 >     assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-12-12 01:01:41.623394 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-12-12 01:01:41.660075 New work for worker! Difficulty: 599.266435 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:41.691285 New work for worker! Difficulty: 200.000000 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:42.448631 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:42.448763  Local: 2360GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:42.448800  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
2013-12-12 01:01:42.448837  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:45.462377 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:45.462555  Local: 2369GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:45.462638  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
Then found another share and it was fine:
Code:
2013-12-12 01:04:22.130684  Local: 2329GH/s in last 10.0 minutes Local dead on arrival: ~1.6% (1-3%) Expected time to share: 30.1 minutes
2013-12-12 01:04:22.130717  Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:22.130754  Pool: 115TH/s Stale rate: 20.5% Expected time to block: 9.4 hours
2013-12-12 01:04:22.335429 New work for worker! Difficulty: 691.171186 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:22.377099 New work for worker! Difficulty: 200.000000 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:25.143566 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:04:25.143681  Local: 2325GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:25.143714  Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:25.143750  Pool: 120TH/s Stale rate: 20.5% Expected time to block: 9.0 hours
2013-12-12 01:04:27.234256 GOT SHARE! Jupiter3 89d9ea47 prev faed7137 age 4.87s
2013-12-12 01:04:27.349609 New work for worker! Difficulty: 614.131984 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:27.391143 New work for worker! Difficulty: 200.000000 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:28.156049 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
2013-12-12 01:04:28.156144  Local: 2327GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:28.156176  Shares: 2 (1 orphan, 0 dead) Stale rate: ~50.0% (9-91%) Efficiency: ~63.3% (11-115%) Current payout: 0.0114 BTC
2013-12-12 01:04:28.156213  Pool: 121TH/s Stale rate: 21.1% Expected time to block: 8.9 hours
2013-12-12 01:04:30.834454 Peer sent entire transaction 90e0bb504ac630d2e08ddf489731341236812c22179e74fedde6a6b5d96282ad that was already received
2013-12-12 01:04:31.166570 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
Also, adjusting share diff works for my node, just fine. p2pool gives work to my workers and reporting share time:
Code:
2013-12-12 01:06:00.703104 Got new merged mining work!
2013-12-12 01:06:00.740053 New work for worker! Difficulty: 570.368318 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:00.767854 New work for worker! Difficulty: 200.000000 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:01.621688 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:06:01.621786  Local: 2352GH/s in last 10.0 minutes Local dead on arrival: ~1.8% (1-3%) Expected time to share: 30.4 minutes
But on webpage it says:
Code:
Pool rate: 121TH/s (21% DOA+orphan) Share difficulty: 487000

Node uptime: 4.0 days Peers: 10 out, 21 in

Local rate: 2.41TH/s (1.5% DOA) Expected time to share: 14.5 minutes
So we have different share diff and ETA for workers in p2pool log, and different share diff nad ETA on p2pool front page. But adjusting itself works very good, I have Expected time to share in p2pool log always auto-adjusted to ~30 minutes.

EDIT:
Both shares I found has been orphaned couple of minutes later!!! :O With series of errors. Whole log here:
http://lenny.dnsd.me/p2pool.log

Shares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC
 Angry Can someone explain how it happened?
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
December 12, 2013, 05:29:27 AM
 #7156

I switched back one worker, I have now 500GH/s less hashrate, but adjusting share difficulty works fine, it's still targeting for 30 minutes:
Before:
Code:
2013-12-12 01:25:39.378616 Got new merged mining work!
2013-12-12 01:25:39.467493 New work for worker! Difficulty: 524.676247 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:39.536678 New work for worker! Difficulty: 200.000000 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:39.943825 New work for worker! Difficulty: 524.676247 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:40.014058 New work for worker! Difficulty: 200.000000 Share difficulty: 942532.952855 Total block value: 25.136015 BTC including 618 transac
tions
2013-12-12 01:25:40.431869 P2Pool: 17329 shares in chain (17333 verified/17333 total) Peers: 30 (20 incoming)
2013-12-12 01:25:40.431971  Local: 2312GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.8 minutes
2013-12-12 01:25:40.432022  Shares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC
2013-12-12 01:25:40.432066  Pool: 113TH/s Stale rate: 17.2% Expected time to block: 9.6 hours
After switching back one Jupiter:
Code:
2013-12-12 01:38:35.039265 Got new merged mining work!
2013-12-12 01:38:35.081103 New work for worker! Difficulty: 460.471053 Share difficulty: 827194.125247 Total block value: 25.045982 BTC including 227 transac
tions
2013-12-12 01:38:35.110148 New work for worker! Difficulty: 200.000000 Share difficulty: 827194.125247 Total block value: 25.045982 BTC including 227 transac
tions
2013-12-12 01:38:35.294612 P2Pool: 17341 shares in chain (17345 verified/17345 total) Peers: 30 (20 incoming)
2013-12-12 01:38:35.294721  Local: 1922GH/s in last 10.0 minutes Local dead on arrival: ~2.4% (1-4%) Expected time to share: 29.4 minutes
2013-12-12 01:38:35.294754  Shares: 3 (2 orphan, 0 dead) Stale rate: ~66.7% (20-94%) Efficiency: ~40.0% (7-96%) Current payout: 0.0080 BTC
2013-12-12 01:38:35.294790  Pool: 113TH/s Stale rate: 16.7% Expected time to block: 9.5 hours
After switching another one:
Code:
2013-12-12 01:49:11.751705 Got new merged mining work!
2013-12-12 01:49:11.779507 New work for worker! Difficulty: 315.541941 Share difficulty: 566841.961741 Total block value: 25.063109 BTC including 155 transactions
2013-12-12 01:49:11.802853 New work for worker! Difficulty: 200.000000 Share difficulty: 566841.961741 Total block value: 25.063109 BTC including 155 transactions
2013-12-12 01:49:13.899286 Peer sent entire transaction 25702c285a2b64d0abb7c0421a01dc68159428b594491a318870a652016fa6d5 that was already received
2013-12-12 01:49:14.122667 P2Pool: 17328 shares in chain (17332 verified/17332 total) Peers: 30 (20 incoming)
2013-12-12 01:49:14.122844  Local: 1435GH/s in last 10.0 minutes Local dead on arrival: ~2.1% (1-4%) Expected time to share: 30.6 minutes
2013-12-12 01:49:14.122970  Shares: 4 (2 orphan, 0 dead) Stale rate: ~50.0% (15-85%) Efficiency: ~60.0% (18-102%) Current payout: 0.0124 BTC
2013-12-12 01:49:14.123066  Pool: 109TH/s Stale rate: 16.7% Expected time to block: 9.9 hours

At this point, I think, that adjusting code should be simpified to one rule:

if your expected time to share is less than 60 minutes, adjust share diff so expected time to share is again 60 minutes.

This will work with all miners, big and biggest ones, gives more room for smaller miners like less than 50, 100 GH/s again.
nreal
Full Member
***
Offline Offline

Activity: 182


View Profile
December 12, 2013, 05:49:30 AM
 #7157

I got error when I found a share today:
Code:
2013-12-12 01:01:36.423805 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:36.423930  Local: 2356GH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:36.423978  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:36.424015  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:39.436918 P2Pool: 17345 shares in chain (17349 verified/17349 total) Peers: 31 (21 incoming)
2013-12-12 01:01:39.437093  Local: 2357GH/s in last 10.0 minutes Local dead on arrival: ~1.3% (0-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:39.437174  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-12-12 01:01:39.437264  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:41.593547 GOT SHARE! Jupiter 23877a5a prev a9d32777 age 80.86s
2013-12-12 01:01:41.622728 > Error while processing Event callbacks:
2013-12-12 01:01:41.622811 > Traceback (most recent call last):
2013-12-12 01:01:41.622846 >   File "/home/user/p2pool/p2pool/bitcoin/worker_interface.py", line 136, in <lambda>
2013-12-12 01:01:41.622882 >     lambda header, user, coinbase_nonce: handler(header, user, pack.IntType(self._my_bits).pack(nonce) + coinbase_nonce),
2013-12-12 01:01:41.622915 >   File "/home/user/p2pool/p2pool/work.py", line 403, in got_response
2013-12-12 01:01:41.622981 >     self.node.set_best_share()
2013-12-12 01:01:41.623012 >   File "/home/user/p2pool/p2pool/node.py", line 297, in set_best_share
2013-12-12 01:01:41.623043 >     self.best_share_var.set(best)
2013-12-12 01:01:41.623073 >   File "/home/user/p2pool/p2pool/util/variable.py", line 74, in set
2013-12-12 01:01:41.623103 >     self.changed.happened(value)
2013-12-12 01:01:41.623133 > --- <exception caught here> ---
2013-12-12 01:01:41.623162 >   File "/home/user/p2pool/p2pool/util/variable.py", line 42, in happened
2013-12-12 01:01:41.623192 >     func(*event)
2013-12-12 01:01:41.623232 >   File "/home/user/p2pool/p2pool/node.py", line 96, in broadcast_share
2013-12-12 01:01:41.623271 >     peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.valu
e, include_txs_with=[share_hash])
2013-12-12 01:01:41.623322 >   File "/home/user/p2pool/p2pool/p2p.py", line 291, in sendShares
2013-12-12 01:01:41.623355 >     assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-12-12 01:01:41.623394 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-12-12 01:01:41.660075 New work for worker! Difficulty: 599.266435 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:41.691285 New work for worker! Difficulty: 200.000000 Share difficulty: 1076527.143944 Total block value: 25.061445 BTC including 243 transa
ctions
2013-12-12 01:01:42.448631 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:42.448763  Local: 2360GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:42.448800  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
2013-12-12 01:01:42.448837  Pool: 116TH/s Stale rate: 20.5% Expected time to block: 9.3 hours
2013-12-12 01:01:45.462377 P2Pool: 17346 shares in chain (17350 verified/17350 total) Peers: 31 (21 incoming)
2013-12-12 01:01:45.462555  Local: 2369GH/s in last 10.0 minutes Local dead on arrival: ~1.5% (1-3%) Expected time to share: 29.2 minutes
2013-12-12 01:01:45.462638  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~125.8% (25-126%) Current payout: 0.0080 BTC
Then found another share and it was fine:
Code:
2013-12-12 01:04:22.130684  Local: 2329GH/s in last 10.0 minutes Local dead on arrival: ~1.6% (1-3%) Expected time to share: 30.1 minutes
2013-12-12 01:04:22.130717  Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:22.130754  Pool: 115TH/s Stale rate: 20.5% Expected time to block: 9.4 hours
2013-12-12 01:04:22.335429 New work for worker! Difficulty: 691.171186 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:22.377099 New work for worker! Difficulty: 200.000000 Share difficulty: 1241624.893775 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:25.143566 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:04:25.143681  Local: 2325GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:25.143714  Shares: 1 (1 orphan, 0 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-100%) Current payout: 0.0000 BTC
2013-12-12 01:04:25.143750  Pool: 120TH/s Stale rate: 20.5% Expected time to block: 9.0 hours
2013-12-12 01:04:27.234256 GOT SHARE! Jupiter3 89d9ea47 prev faed7137 age 4.87s
2013-12-12 01:04:27.349609 New work for worker! Difficulty: 614.131984 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:27.391143 New work for worker! Difficulty: 200.000000 Share difficulty: 1103231.495636 Total block value: 25.087831 BTC including 352 transa
ctions
2013-12-12 01:04:28.156049 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
2013-12-12 01:04:28.156144  Local: 2327GH/s in last 10.0 minutes Local dead on arrival: ~1.7% (1-3%) Expected time to share: 30.2 minutes
2013-12-12 01:04:28.156176  Shares: 2 (1 orphan, 0 dead) Stale rate: ~50.0% (9-91%) Efficiency: ~63.3% (11-115%) Current payout: 0.0114 BTC
2013-12-12 01:04:28.156213  Pool: 121TH/s Stale rate: 21.1% Expected time to block: 8.9 hours
2013-12-12 01:04:30.834454 Peer sent entire transaction 90e0bb504ac630d2e08ddf489731341236812c22179e74fedde6a6b5d96282ad that was already received
2013-12-12 01:04:31.166570 P2Pool: 17352 shares in chain (17356 verified/17356 total) Peers: 31 (21 incoming)
Also, adjusting share diff works for my node, just fine. p2pool gives work to my workers and reporting share time:
Code:
2013-12-12 01:06:00.703104 Got new merged mining work!
2013-12-12 01:06:00.740053 New work for worker! Difficulty: 570.368318 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:00.767854 New work for worker! Difficulty: 200.000000 Share difficulty: 1024614.009517 Total block value: 25.021775 BTC including 157 transactions
2013-12-12 01:06:01.621688 P2Pool: 17351 shares in chain (17355 verified/17355 total) Peers: 31 (21 incoming)
2013-12-12 01:06:01.621786  Local: 2352GH/s in last 10.0 minutes Local dead on arrival: ~1.8% (1-3%) Expected time to share: 30.4 minutes
But on webpage it says:
Code:
Pool rate: 121TH/s (21% DOA+orphan) Share difficulty: 487000

Node uptime: 4.0 days Peers: 10 out, 21 in

Local rate: 2.41TH/s (1.5% DOA) Expected time to share: 14.5 minutes
So we have different share diff and ETA for workers in p2pool log, and different share diff nad ETA on p2pool front page. But adjusting itself works very good, I have Expected time to share in p2pool log always auto-adjusted to ~30 minutes.

EDIT:
Both shares I found has been orphaned couple of minutes later!!! :O With series of errors. Whole log here:
http://lenny.dnsd.me/p2pool.log

Shares: 2 (2 orphan, 0 dead) Stale rate: ~100.0% (34-100%) Efficiency: ~0.0% (0-80%) Current payout: 0.0000 BTC
 Angry Can someone explain how it happened?


I did have same thing going with my node, what i did was rebuild everything needed with p2pool with useflag soap enabled, havent seen that error since. Not sure if it was that, but that error doesnt show up anymore..
nreal
Full Member
***
Offline Offline

Activity: 182


View Profile
December 12, 2013, 08:01:09 AM
 #7158

To start p2pool as daemon, not sure if its explained somewhere but didnt found it.

One can start it like this: nohup python run_p2pool.py ....... > /dev/null 2>&1 &

So then you can restart X or even logout without killing p2pool.

> /dev/null 2>&1 & at the end makes nohup not to log anything and the & makes it run as a daemon

If you want to read that useless log it can be done  - tail -f /p2pool/data/bitcoin/log

domob
Legendary
*
Offline Offline

Activity: 936


View Profile WWW
December 13, 2013, 10:40:12 AM
 #7159

This has probably been asked before somewhere, but please excuse that I'm not going to read through all pages here.  It seems to me that you need a large hash rate in order to use P2Pool reasonably, right?  The current rate of P2Pool is reported as 121 TH/s.  It is scheduled to produce 8,640 shares per day (?), which means that on average, to get a share per day, you need 14 GH/s.  And one share per day on average is not that great, IMHO, in order to get reasonably steady payouts.

Am I correct to assume that it makes no sense to use P2Pool without 10-100 GH/s?  I would love to use it instead of a centralised pool, but it really seems not a good idea for me (I have around 1.5 GH/s, not to make a profit, more for the fun - but I still get a couple mBTC per week, which is not bad).  Wouldn't it be possible in theory (if the system is changed a bit, I understand that) to create a P2Pool for P2Pool and so on, building a hierarchy of networks, which allow even smaller rates?  It probably would not be worth the effort just to make it usable to small miners, I guess.

Use your Namecoin identity as OpenID: https://nameid.org/
Donations: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737
K1773R
Legendary
*
Offline Offline

Activity: 1526


/dev/null


View Profile
December 13, 2013, 11:24:43 AM
 #7160

This has probably been asked before somewhere, but please excuse that I'm not going to read through all pages here.  It seems to me that you need a large hash rate in order to use P2Pool reasonably, right?  The current rate of P2Pool is reported as 121 TH/s.  It is scheduled to produce 8,640 shares per day (?), which means that on average, to get a share per day, you need 14 GH/s.  And one share per day on average is not that great, IMHO, in order to get reasonably steady payouts.

Am I correct to assume that it makes no sense to use P2Pool without 10-100 GH/s?  I would love to use it instead of a centralised pool, but it really seems not a good idea for me (I have around 1.5 GH/s, not to make a profit, more for the fun - but I still get a couple mBTC per week, which is not bad).  Wouldn't it be possible in theory (if the system is changed a bit, I understand that) to create a P2Pool for P2Pool and so on, building a hierarchy of networks, which allow even smaller rates?  It probably would not be worth the effort just to make it usable to small miners, I guess.
p2pool isnt good at payout out steady in this case, but you get more coins than anywhere long-term.

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
Pages: « 1 ... 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 [358] 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!