Bitcoin Forum
December 09, 2016, 05:34:14 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2033421 times)
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 01:51:55 AM
 #7441

I've never seen anyone say good things about QoS.  In fact, I've seen lots of people say turn it off, it hoses things, and I've seen it here in this thread.

I really don't care about what people say but about what is doable. I've configured QoS on my Linux server, it works, end of story. If people use QoS on their Linux server and it doesn't work for them I can provide tips.

That might be the difference.  The average person isn't going to use QoS on a Linux server.  The average person is going to have a cheap router that touts QoS, but the reality is it doesn't work well.

Who doesn't use the bandwidth for anything else?

You misunderstood. QoS allows bandwidth for other traffic but for it to work you must have some headroom, if you need all of your available bandwidth for other traffics you can't use p2pool, if you only need what's above 256-512kbps in both directions then you can fit p2pool and bitcoind in with various levels of efficiency.

I know what QoS is.  I have theoretical 768k up.  If I need p2pool and bitcoin to use 2/3's of that, I'm in trouble.

Quote
You don't have to ask here, the information is already public. Go to p2pool.info and you'll have data for a theoretical 100% efficient p2pool node.

I don't care what theoretical is.  I want to know what people are really getting! Smiley

Quote
Given that you mentioned a cube I suppose you have an ASICMiner cube. Unless they have a different miner implementation than the blades you are probably out of luck on p2pool. IIRC the blade miner could only do getwork and poorly: it didn't work well on several pools including p2pool because of their implementation. If this didn't change you are probably better off letting the beast mine on whatever pools you could find that worked fine with it.

If I was to attempt it I'd run it through a stratum proxy, as I'm doing now.  But as I've implied a few times, there's no way I'm pointing 38gh/s at 1m share difficulty.

M

I would have to say if you have a good switch and aren't using a mickey mouse home one you should be good to go. Home managed switches have very low forwarding rates thus they can't move higher volumes of traffic over them compared to the enterprise class managed switches. So if you a good switch and are using good cabling, I would certainly enable jumbo frames before messing with the QOS. My firewall, Dell PowerConnect 6224 and my openSUSE (p2pool server) have jumbo frames enabled.
1481304854
Hero Member
*
Offline Offline

Posts: 1481304854

View Profile Personal Message (Offline)

Ignore
1481304854
Reply with quote  #2

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

Posts: 1481304854

View Profile Personal Message (Offline)

Ignore
1481304854
Reply with quote  #2

1481304854
Report to moderator
1481304854
Hero Member
*
Offline Offline

Posts: 1481304854

View Profile Personal Message (Offline)

Ignore
1481304854
Reply with quote  #2

1481304854
Report to moderator
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 01:57:51 AM
 #7442

is there a users page add-on for p2pool other than the front-end add-on?

Thanks,
gyverlb
Hero Member
*****
Offline Offline

Activity: 896



View Profile
January 19, 2014, 02:29:32 AM
 #7443

Quote
You don't have to ask here, the information is already public. Go to p2pool.info and you'll have data for a theoretical 100% efficient p2pool node.

I don't care what theoretical is.  I want to know what people are really getting! Smiley

They are getting what the blocks found by p2pool pay them. These blocks aren't theoretical only a 100% efficient node is.

If your node is averaging around 103% efficiency like mine for example you will get 103% of what p2pool.info reports. That's pure math.

P2pool tuning guide
Trade BTC for €/$ at bitcoin.de (referral), it's cheaper and faster (acts as escrow and lets the buyers do bank transfers).
Tip: 17bdPfKXXvr7zETKRkPG14dEjfgBt5k2dd
bkminer
Full Member
***
Offline Offline

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 19, 2014, 04:19:04 AM
 #7444

I'm running a node for testing right now in a 2.6 Ghz Core i7 16GB RAM PCI-e SSD...and Ubuntu Server 12.04

My question is, I'm getting periodic spikes in both the getblocktemploate latency (upwards of 30s for a spike) and DOAs reported up from 4% to almost 30% then it calms down and I get a share.  I have 17 shares 1 orphan 117% Efficiency.  I've got about 1.4TH/s on the node. When this happens the p2pool app pegs CPU and then slowly calms down. I've tuned bitcoind for max block size etc. from the tuning guide as well. I have 6 out and 8 in p2pool connections.

I've also noticed my bitcoind has 98 connections and some of them have huge Recv-Q and Send-Q numbers... I'm on a 50 down 5 up cable modem so the connection shouldn't be the problem.  I'm thinking those "dead" connections to bitcoind aren't doing me any good.

My payouts are going up for each share found, but the Spikes in DOA don't seem right.  Any ideas what could be happening?
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 04:27:59 AM
 #7445

I'm running a node for testing right now in a 2.6 Ghz Core i7 16GB RAM PCI-e SSD...and Ubuntu Server 12.04

My question is, I'm getting periodic spikes in both the getblocktemploate latency (upwards of 30s for a spike) and DOAs reported up from 4% to almost 30% then it calms down and I get a share.  I have 17 shares 1 orphan 117% Efficiency.  I've got about 1.4TH/s on the node. When this happens the p2pool app pegs CPU and then slowly calms down. I've tuned bitcoind for max block size etc. from the tuning guide as well. I have 6 out and 8 in p2pool connections.

I've also noticed my bitcoind has 98 connections and some of them have huge Recv-Q and Send-Q numbers... I'm on a 50 down 5 up cable modem so the connection shouldn't be the problem.  I'm thinking those "dead" connections to bitcoind aren't doing me any good.

My payouts are going up for each share found, but the Spikes in DOA don't seem right.  Any ideas what could be happening?

How long have you been running for?

I haven't been running for very long, a about 6 hours. But my DOA is 3% at 276GH/s my I have only have 2 shares but efficiency is 129%. I have been hitting 30s a couple of times but it doesn't seem to affect me much. I am using a Xi3 Z3RO Pro computer (4GB Ram, 120GB mSATA, dual core 1.65GHz AMD) running openSUSE not Ubuntu. The only other thing I have differently on my network is my CISCO firewall, managed switch, and P2Pool server have Jumbo Frames enabled. I use jumbo frames on other pieces of hardware in my network, such as my SAN and ESXi server so I figured I would give a try on the Z3RO Pro.

ikolubr
Newbie
*
Offline Offline

Activity: 13


View Profile
January 19, 2014, 05:11:57 AM
 #7446

Code:
Share check failed:
2014-01-18 21:03:38.148653 > Traceback (most recent call last):
2014-01-18 21:03:38.148709 >   File "/home/breeba/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-18 21:03:38.148784 >     self.node.handle_shares(result, self)
2014-01-18 21:03:38.148835 >   File "/home/breeba/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-18 21:03:38.148890 >     self.node.set_best_share()
2014-01-18 21:03:38.148946 >   File "/home/breeba/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-18 21:03:38.149002 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-18 21:03:38.149056 >   File "/home/breeba/p2pool/p2pool/data.py", line 452, in think
2014-01-18 21:03:38.149113 >     if self.attempt_verify(share):
2014-01-18 21:03:38.149163 > --- <exception caught here> ---
2014-01-18 21:03:38.149217 >   File "/home/breeba/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-18 21:03:38.149271 >     share.check(self)
2014-01-18 21:03:38.149326 >   File "/home/breeba/p2pool/p2pool/data.py", line 320, in check
2014-01-18 21:03:38.149380 >     raise ValueError('share_info invalid')
2014-01-18 21:03:38.149436 > exceptions.ValueError: share_info invalid

I'm getting this error on p2pool and my cpu goes 100%. The error is continuos. I've tried to delete the data folder, then it works nice for few hours and baam the error starts again!

Another doubt: I've set up the pool to collect 2%, why may pout amount is always 0 and I just see payments eery 4 or 5 days?

Any ideas?!

Thank you,
Igor

my node: bitcoin.breeba.com:3330
bkminer
Full Member
***
Offline Offline

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 19, 2014, 05:27:13 AM
 #7447

Igor,

I get the same error and the same spikes in getblocktemplate latency you're getting.  And it seems getting a share isn't related to it as I originally thought.

-Rick
nreal
Full Member
***
Offline Offline

Activity: 182


View Profile
January 19, 2014, 06:55:20 AM
 #7448

I'm running a node for testing right now in a 2.6 Ghz Core i7 16GB RAM PCI-e SSD...and Ubuntu Server 12.04

My question is, I'm getting periodic spikes in both the getblocktemploate latency (upwards of 30s for a spike) and DOAs reported up from 4% to almost 30% then it calms down and I get a share.  I have 17 shares 1 orphan 117% Efficiency.  I've got about 1.4TH/s on the node. When this happens the p2pool app pegs CPU and then slowly calms down. I've tuned bitcoind for max block size etc. from the tuning guide as well. I have 6 out and 8 in p2pool connections.

I've also noticed my bitcoind has 98 connections and some of them have huge Recv-Q and Send-Q numbers... I'm on a 50 down 5 up cable modem so the connection shouldn't be the problem.  I'm thinking those "dead" connections to bitcoind aren't doing me any good.

My payouts are going up for each share found, but the Spikes in DOA don't seem right.  Any ideas what could be happening?

I think that with your 5mbit upload the most you can handle is 10-15 bitcoind connections, more if you choose them carefully. Those random connections eats your upload bandwith - because theres allways someone downloading blockchain..
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 19, 2014, 10:18:03 AM
 #7449

Quote
You don't have to ask here, the information is already public. Go to p2pool.info and you'll have data for a theoretical 100% efficient p2pool node.

I don't care what theoretical is.  I want to know what people are really getting! Smiley

They are getting what the blocks found by p2pool pay them. These blocks aren't theoretical only a 100% efficient node is.

If your node is averaging around 103% efficiency like mine for example you will get 103% of what p2pool.info reports. That's pure math.

Yes, I understand that.  I still want to see some numbers! Smiley You keep claiming you do better in p2pool than a conventional pool.  Let's see numbers to prove it!  We know theory and reality usually don't meet.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
January 19, 2014, 11:32:36 AM
 #7450

Today I found my p2pool BTC crashed, it was running fine for couple of days, but today I looked there and stats were not loading, so I logged via ssh to my machine and found this:

Code:
2014-01-19 11:28:39.698426 >     share.check(self)
2014-01-19 11:28:39.698468 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.698510 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.698550 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.710423 > Share check failed:
2014-01-19 11:28:39.710527 > Traceback (most recent call last):
2014-01-19 11:28:39.710573 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.710623 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.710683 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.710725 >     self.node.set_best_share()
2014-01-19 11:28:39.710770 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.710812 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.710855 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.710892 >     if self.attempt_verify(share):
2014-01-19 11:28:39.710935 > --- <exception caught here> ---
2014-01-19 11:28:39.710976 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.711017 >     share.check(self)
2014-01-19 11:28:39.711060 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.711100 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.711139 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.723094 > Share check failed:
2014-01-19 11:28:39.723195 > Traceback (most recent call last):
2014-01-19 11:28:39.723243 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.723289 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.723334 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.723386 >     self.node.set_best_share()
2014-01-19 11:28:39.723427 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.723469 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.723513 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.723550 >     if self.attempt_verify(share):
2014-01-19 11:28:39.723589 > --- <exception caught here> ---
2014-01-19 11:28:39.723636 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.723677 >     share.check(self)
2014-01-19 11:28:39.723720 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.723766 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.723808 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.742410 > Share check failed:
2014-01-19 11:28:39.742704 > Traceback (most recent call last):
2014-01-19 11:28:39.742866 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.743012 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.743167 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.743315 >     self.node.set_best_share()
2014-01-19 11:28:39.743469 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.743625 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.743776 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.743925 >     if self.attempt_verify(share):
2014-01-19 11:28:39.744068 > --- <exception caught here> ---
2014-01-19 11:28:39.744218 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.744400 >     share.check(self)
2014-01-19 11:28:39.744553 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.744699 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.744848 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.770142 > Share check failed:
2014-01-19 11:28:39.770299 > Traceback (most recent call last):
2014-01-19 11:28:39.770385 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.770468 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.770549 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.770661 >     self.node.set_best_share()
2014-01-19 11:28:39.770708 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.770755 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.770798 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.770842 >     if self.attempt_verify(share):
2014-01-19 11:28:39.770885 > --- <exception caught here> ---
2014-01-19 11:28:39.770928 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.770972 >     share.check(self)
2014-01-19 11:28:39.771013 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.771052 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.771095 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.782044 > Share check failed:
2014-01-19 11:28:39.782151 > Traceback (most recent call last):
2014-01-19 11:28:39.782199 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.782246 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.782293 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.782333 >     self.node.set_best_share()
2014-01-19 11:28:39.782377 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.782424 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.782466 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.782505 >     if self.attempt_verify(share):
2014-01-19 11:28:39.782547 > --- <exception caught here> ---
2014-01-19 11:28:39.782589 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.782652 >     share.check(self)
2014-01-19 11:28:39.782699 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.782743 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.782787 > exceptions.ValueError: share_info invalid
2014-01-19 11:28:39.792553 > Share check failed:
2014-01-19 11:28:39.792661 > Traceback (most recent call last):
2014-01-19 11:28:39.792708 >   File "/home/pioruns1/p2pool/p2pool/p2p.py", line 283, in handle_shares
2014-01-19 11:28:39.792753 >     self.node.handle_shares(result, self)
2014-01-19 11:28:39.792799 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 48, in handle_shares
2014-01-19 11:28:39.792844 >     self.node.set_best_share()
2014-01-19 11:28:39.792888 >   File "/home/pioruns1/p2pool/p2pool/node.py", line 295, in set_best_share
2014-01-19 11:28:39.792934 >     best, desired, decorated_heads = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-01-19 11:28:39.792982 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 452, in think
2014-01-19 11:28:39.793024 >     if self.attempt_verify(share):
2014-01-19 11:28:39.793063 > --- <exception caught here> ---
2014-01-19 11:28:39.793118 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 431, in attempt_verify
2014-01-19 11:28:39.793163 >     share.check(self)
2014-01-19 11:28:39.793207 >   File "/home/pioruns1/p2pool/p2pool/data.py", line 320, in check
2014-01-19 11:28:39.793246 >     raise ValueError('share_info invalid')
2014-01-19 11:28:39.793287 > exceptions.ValueError: share_info invalid
Log was completely full of this crap.
Litecoin p2pool on same machine is running fine now, so I presume it's not my PC problem.
My PC details:
Code:
Linux 3.11.0-15-generic x86_64 GNU/Linux
Description: Ubuntu 13.10
Python 2.7.5+
Current p2pool version: 13.4-4-ge66e6d5
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 01:18:43 PM
 #7451

Have you restarted your Ubuntu to see if bitcoind and the P2Pool server startup again?

xgtele
Sr. Member
****
Offline Offline

Activity: 265



View Profile
January 19, 2014, 01:22:20 PM
 #7452

May be its time to do sudo apt-get update and sudo apt-get upgrade for your Ubuntu?

clown
Member
**
Offline Offline

Activity: 70


View Profile
January 19, 2014, 01:51:53 PM
 #7453

Is there a way to calculate (or even approximate) the current expected payout given the amount of pseudo shares accumulated?

My Dogecoin mining pool. 0% fee, proxypool into p2pool network
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 19, 2014, 01:57:26 PM
 #7454

Is there a way to calculate (or even approximate) the current expected payout given the amount of pseudo shares accumulated?

I believe it tells you on the p2pool output.  You should also be able to divide your number of shares by the number of shares in the chain and multiply that times 25 to get an approximate value.  (I think...)

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
clown
Member
**
Offline Offline

Activity: 70


View Profile
January 19, 2014, 02:16:46 PM
 #7455

I believe it tells you on the p2pool output.  You should also be able to divide your number of shares by the number of shares in the chain and multiply that times 25 to get an approximate value.  (I think...)

M

I was under the impression that pseudo shares are not included in the share chain, only shares with diff above the p2pool diff are included.

Another question. Let's pretend for a moment the p2pool share difficulty is at 10. A miner submits a share with difficulty 20 and the share goes into the share chain. During payout, is the value of the share capped to the share difficulty at the time of submission (10)?

I'm trying to build a proxy pool that'd would be able to payout to miners on a pseudo share basis (much less variance for miners at higher risk to pool operator). And perhaps have a vardiff system based on the pseudo shares. Has anything like this been attempted before?

My Dogecoin mining pool. 0% fee, proxypool into p2pool network
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 19, 2014, 02:38:51 PM
 #7456

I believe it tells you on the p2pool output.  You should also be able to divide your number of shares by the number of shares in the chain and multiply that times 25 to get an approximate value.  (I think...)

M

I was under the impression that pseudo shares are not included in the share chain, only shares with diff above the p2pool diff are included.

Perhaps I misunderstood.  I was referring to the shares above the p2pool diff share, which is what I thought you were asking.

Quote
Another question. Let's pretend for a moment the p2pool share difficulty is at 10. A miner submits a share with difficulty 20 and the share goes into the share chain. During payout, is the value of the share capped to the share difficulty at the time of submission (10)?

It's capped at 10, like most pools.  AFAIK ozcoin is the only one that has an option to go by share value, and it uses a much different payout system.

Quote
I'm trying to build a proxy pool that'd would be able to payout to miners on a pseudo share basis (much less variance for miners at higher risk to pool operator). And perhaps have a vardiff system based on the pseudo shares. Has anything like this been attempted before?

It has been attempted before.  I forget what it was called ... someone put up a server to do just that, complete with merged mining.  It was fairly popular until it was hacked.  I think you search the forums you can find it, I think the source might be available as well.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
clown
Member
**
Offline Offline

Activity: 70


View Profile
January 19, 2014, 02:42:00 PM
 #7457


It has been attempted before.  I forget what it was called ... someone put up a server to do just that, complete with merged mining.  It was fairly popular until it was hacked.  I think you search the forums you can find it, I think the source might be available as well.

M

You'll have to enlighten me, I've searched long and hard before I made this post and didn't see anything. Care to drop a name?

My Dogecoin mining pool. 0% fee, proxypool into p2pool network
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 19, 2014, 02:49:21 PM
 #7458


It has been attempted before.  I forget what it was called ... someone put up a server to do just that, complete with merged mining.  It was fairly popular until it was hacked.  I think you search the forums you can find it, I think the source might be available as well.

M

You'll have to enlighten me, I've searched long and hard and didn't see anything. Care to drop a name?

I just remembered the name.  Was p2pmining. 

https://bitcointalk.org/index.php?topic=66202.0

There wasn't any risk to the pool operator, to my knowledge.  The basic principle was the subpool had it's own share chain (or equiv - could manage with a properly designed database) to track the p2pmining users.  Each share was also submitted to the real chain under the p2pmining address.  When a payout occurred, it was divided among the users in the subpool based on their piece of the subchain.  This also allowed merged mining to occur at a sub pool level, instead of basically solo, which is what p2pool is now.

The downside, of course, was it was a mini centralized pool, subject to possible pool operator abuse and hacking.  Hacking is what brought it down..

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
January 19, 2014, 02:57:23 PM
 #7459

I was under the impression that pseudo shares are not included in the share chain, only shares with diff above the p2pool diff are included.

Another question. Let's pretend for a moment the p2pool share difficulty is at 10. A miner submits a share with difficulty 20 and the share goes into the share chain. During payout, is the value of the share capped to the share difficulty at the time of submission (10)?

I'm trying to build a proxy pool that'd would be able to payout to miners on a pseudo share basis (much less variance for miners at higher risk to pool operator). And perhaps have a vardiff system based on the pseudo shares. Has anything like this been attempted before?

Miners can intentionally pick a higher difficulty for themselves.  These higher difficulty shares give a higher payout and free up space in the share window.

This was discussed to death a few pages back.

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

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 19, 2014, 03:33:35 PM
 #7460


I think that with your 5mbit upload the most you can handle is 10-15 bitcoind connections, more if you choose them carefully. Those random connections eats your upload bandwith - because theres allways someone downloading blockchain..

Thanks, nreal, I've adjusted the bitcoind connections down.  Also I'm on Time Warner Cable and they have a habit of shaping large outbound transfers, or any P2P traffic they see.  I'm trying to get my landlord to get FiOS but he doesn't seem interested.

Pages: « 1 ... 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 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 ... 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!