Bitcoin Forum
December 07, 2016, 10:40:35 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 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 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2032543 times)
notme
Legendary
*
Offline Offline

Activity: 1526


View Profile
August 17, 2013, 08:08:01 AM
 #6461

so if p2pool.info is underreporting the pool hashrate, doesn't that mean it's over estimating our luck?

It isn't underreporting.  It is using a smoother moving average that reacts less to temporary jumps and dips in hashrate.

https://www.bitcoin.org/bitcoin.pdf
While no idea is perfect, some ideas are useful.
12jh3odyAAaR2XedPKZNCR4X4sebuotQzN
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481150435
Hero Member
*
Offline Offline

Posts: 1481150435

View Profile Personal Message (Offline)

Ignore
1481150435
Reply with quote  #2

1481150435
Report to moderator
1481150435
Hero Member
*
Offline Offline

Posts: 1481150435

View Profile Personal Message (Offline)

Ignore
1481150435
Reply with quote  #2

1481150435
Report to moderator
1481150435
Hero Member
*
Offline Offline

Posts: 1481150435

View Profile Personal Message (Offline)

Ignore
1481150435
Reply with quote  #2

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

Activity: 737



View Profile
August 17, 2013, 02:25:28 PM
 #6462

so if p2pool.info is underreporting the pool hashrate, doesn't that mean it's over estimating our luck?

It isn't underreporting.  It is using a smoother moving average that reacts less to temporary jumps and dips in hashrate.

When calculating luck, the full complement of individual 5 minute data points are used.  The smoothing/averaging is only used on the UI/graph shown on the page to reduce the amount of data that has be loaded to the web browser and speed up the page load.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
wtogami
Sr. Member
****
Offline Offline

Activity: 263



View Profile
August 18, 2013, 07:30:51 AM
 #6463

p2pool-13.3 released containing bug fixes primarily for p2pool LTC.  This upgrade is recommended for p2pool LTC miners as it bans v11 nodes, reducing log spam and bandwidth use by a significant amount.

If you appreciate my work please consider making a small donation.
BTC:  1LkYiL3RaouKXTUhGcE84XLece31JjnLc3      LTC:  LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9
GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
August 18, 2013, 07:39:40 AM
 #6464

p2pool-13.3 released containing bug fixes primarily for p2pool LTC.  This upgrade is recommended for p2pool LTC miners as it bans v11 nodes, reducing log spam and bandwidth use by a significant amount.

At least unlike the bitcoin split, the cut-off LTC nodes should solve a few blocks (right now it's at one every 12hrs).  Given the 40% orphan/DOA rate, I've been considering reverting to a lower version and maybe even start my stuff back up to mine litecoins

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
August 18, 2013, 08:05:09 AM
 #6465

P2Pool release 13.3 - commit hash: 3ca723ee19cb8e2ee54e32a81e0d3caa2ff51441

Windows binary: http://u.forre.st/u/zdeurytx/p2pool_win32_13.3.zip
Windows binary signature: http://u.forre.st/u/gpuwkhue/p2pool_win32_13.3.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.3
Source tarball: https://github.com/forrestv/p2pool/tarball/13.3

Changes:
* Changes to make Litecoin switch go more smoothly (drop/ban old peers)
* Fixed startum miner failover not working - P2Pool would keep miners connected during failure conditions (lost connection to bitcoind or all peers)
* Fixed potential memory leak

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
wtogami
Sr. Member
****
Offline Offline

Activity: 263



View Profile
August 18, 2013, 11:01:31 AM
 #6466

p2pool-13.3 released containing bug fixes primarily for p2pool LTC.  This upgrade is recommended for p2pool LTC miners as it bans v11 nodes, reducing log spam and bandwidth use by a significant amount.

At least unlike the bitcoin split, the cut-off LTC nodes should solve a few blocks (right now it's at one every 12hrs).  Given the 40% orphan/DOA rate, I've been considering reverting to a lower version and maybe even start my stuff back up to mine litecoins

40% orphan/DOA rate was a mis-measurement on the v11 side of the fork during a short period while those nodes failed to find each other as they were rejected by the v13 network.  v13 has 15 instead of 10 second average share intervals which has already enabled a measurable improvement to orphan and DOA rates on the v13 network.

Also note that p2pool version 11 was incapable of submitting blocks to litecoin-0.8.3.7, and 0.6.9.2 is considered unsafe to operate due to unpatched vulnerabilities.

Code:
       litecoin=math.Object(
        PARENT=networks.nets['litecoin'],
        SHARE_PERIOD=10, # seconds
        NEW_SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=12, # blocks
        NEW_SPREAD=3, # blocks

Also the share lifetime was reduced from the previous 12 shares to 3, and share difficulty for the first share is increased to such a level that you would have a target minimum dust size of 0.03 LTC.  The combination of these changes has the following effect:

  • Greater Efficiency for the LTC Network: Small miners receive bigger dust payouts, but less often.  This means the reduction of thousands of tiny dust outputs per day, and far lower transaction fees for miners to combine the dust outputs.
  • Lower DOA/orphan rate allows GPU miners to increase Intensity, allowing the entire p2pool LTC network to increase its hashrate with existing hardware.


p2pool-13.3 reduces bandwidth waste and log spam significantly.

If you appreciate my work please consider making a small donation.
BTC:  1LkYiL3RaouKXTUhGcE84XLece31JjnLc3      LTC:  LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9
GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
alatvian
Jr. Member
*
Offline Offline

Activity: 37



View Profile
August 19, 2013, 02:50:19 AM
 #6467

my LTC p2pool v13 reports in the log file that share difficulty is >6, while on the web UI it's around 1.  I'm tending to believe the log file, because cgminer hasn't scored a share in 2 days, but I have several shares over 64K difficulty (which equates to diff=1, if I understand cgminer's stats correctly).  Why does p2pool report 2 different difficulties?

The node is here: http://192.241.177.9:9327/static/.  I've disconnected my miners because I think the difficulty is just too great for my hashing power. 
daemondazz
Sr. Member
****
Offline Offline

Activity: 294



View Profile
August 19, 2013, 09:41:12 AM
 #6468

P2Pool Sub-Pool for Low Hash-Rate Miners

I am planning up modifying the Bitcoin node at cryptominer.org:9332 to act as a sub-pool and be more friendly for low hash-rate miners. I'm looking for some feedback on my scheme to see if there are any glaring holes / vulnerabilities.

My basic plan is:

  • Configure p2pool to have 100% fee so all hash rate goes to the pool
  • A 'shift' is 12 hours in length, based on UTC midnight/noon
  • P2Pool is modified to log all submitted shares with diff >= 25 (this is already completed - my patch provides a command line option to specify a logging function. I plan on submitting this to forrestv for inclusion upstream)
  • The miner score is calculated as the logarithmic of the sum of the submitted difficulty of shares for that miner for that shift
  • The miner is credited for all blocks found during the shift, minus an admin fee, based on the percentage of their score compared to the total

The admin fee will probably be on the order of 5% of the payout the node receives for each block found by the network.

I'm only logging submitted shares with diff >= 25 just so I don't have to log a heap of data but still allow the miners to submit a reasonable number of shares. My USB Erupters seem to find a >25 diff block every few minutes so a 12 hour shift should allow time for even very low rate miners to accrue a score. This value can be tweaked easily enough if needed.

I'm thinking the score will be the logarithmic of the sum of the total diff submitted rather than just the a count of shares that are higher than the threshold to provide a reward finding more difficult hashes, and especially shares and blocks. This is one area I can see there may be holes in the logic in.

If the miner connects to the pool using a valid bitcoin address, they are automatically paid out once a global threshold is reached (such as 0.25 BTC) or they can register on the website and choose more "friendly" usernames and payout threshold/address. This allows existing miners to continue as they are. I want to also modify p2pool so it rejects logins from users which are not a valid address or already registered on the website. If a miner that has mined using a bitcoin address subsequently registers on the website, they will have to sign a message using the address to claim the address and be able to modify settings.

An example: I have 3 miners, which submit scores of 100, 50 and 25 respectively. During a shift the networks finds 3 blocks which I get paid out 0.12412, 0.25121 and 0.16331 BTC.

Total received = 0.53864
Total score = 175
Admin fee (5%) = 0.026932 BTC
Payout for miners = 0.511708 BTC

Miner1 = 100/175*0.511708 = 0.29240457 BTC
Miner2 = 50/175*0.511708  = 0.14620228 BTC
Miner3 = 25/175*0.511708  = 0.07310114 BTC

Any feedback? Does this sound like a reasonable idea? Any big problems with it?

Computers, Amateur Radio, Electronics, Aviation - 1dazzrAbMqNu6cUwh2dtYckNygG7jKs8S
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
August 19, 2013, 12:30:42 PM
 #6469

P2Pool Sub-Pool for Low Hash-Rate Miners
(...)
Any feedback? Does this sound like a reasonable idea? Any big problems with it?
Why not reanimate p2pmining? https://bitcointalk.org/index.php?topic=66202.0
Code available by PMing owner afik.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
daemondazz
Sr. Member
****
Offline Offline

Activity: 294



View Profile
August 19, 2013, 01:21:10 PM
 #6470

P2Pool Sub-Pool for Low Hash-Rate Miners
(...)
Any feedback? Does this sound like a reasonable idea? Any big problems with it?
Why not reanimate p2pmining? https://bitcointalk.org/index.php?topic=66202.0
Code available by PMing owner afik.

I did look at that, if you look at the last few posts in that thread you linked I actually worked out the database schema from the code. The biggest issue I had with it was that it written in PHP and hence doesn't integrate with the python web framework I'm using for cryptominer.org. Also the integration into p2pool was fairly specific and has drifted from HEAD over time.

The changes I've made to p2pool are very simple and also generic. They could easily be used by anybody to create their own modules for doing something similar. You pass in the full python path to a model as a CLI option and it imports it on the fly and then calls it with a predefined list of arguments. The simplest logging function could be:

Code:
def logger(submitted_hash, submitted_diff, found_block, found_share, miner_username):
    print 'Logged share diff %d (score %6.5f) from %s' % (submitted_diff, math.log(submitted_diff), miner_username)

Anyway, the coding side of this is fairly easy, in fact I've already done about 60% of it. I was more after feedback about the concept of running a sub-pool for low hashrate miners and if my methodology had any obvious issues that could be exploited.

Computers, Amateur Radio, Electronics, Aviation - 1dazzrAbMqNu6cUwh2dtYckNygG7jKs8S
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
August 19, 2013, 01:44:08 PM
 #6471

You should log (count) only accepted shares, the way you posted can log both accepted and rejected ones Smiley Or log both but add "accepted" bool field for statistics.
Better way would be log into database not in text file - this way you can run many instances (ie European node and US node) and gather data in one place.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
TierNolan
Legendary
*
Offline Offline

Activity: 1036


View Profile
August 19, 2013, 04:23:21 PM
 #6472

I did look at that, if you look at the last few posts in that thread you linked I actually worked out the database schema from the code. The biggest issue I had with it was that it written in PHP and hence doesn't integrate with the python web framework I'm using for cryptominer.org. Also the integration into p2pool was fairly specific and has drifted from HEAD over time.

Adding support for sub-pools directly into p2pool itself would add value to the p2pool software.

Variance for pools consists of pool variance and share variance.  If the pool is only winning one block every 3-4 days, then pool variance is high.  No matter how many shares are issued, the total variance can never be lower than that.

The more hashing power on the p2pool chain, the lower the variance for p2pool and that applies to all users.

Even, the major pools would benefit from it to, though granted to a lesser extent.  If 2 could be convinced to join, then both benefit from lower variance and reduce variance of all other users of p2pool.

Has anyone considered hierarchical p2pools? 

Using p2pool to mine the p2pool sharechain, in the same way people have modified the pool to mine alt-chains.

You could have 1 root chains and 10 sub-chains mining that chain.  Each sub-chain has 10X lower difficulty.

The risk of a sub-chain dying increases the more hops from the root chain though.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
wtogami
Sr. Member
****
Offline Offline

Activity: 263



View Profile
August 19, 2013, 08:36:43 PM
 #6473

Subpools are fine as long as they build up balances of miners over time in order to avoid dust micropayments that are unhealthy for the network and expensive for the miners to spend.

If you appreciate my work please consider making a small donation.
BTC:  1LkYiL3RaouKXTUhGcE84XLece31JjnLc3      LTC:  LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9
GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
nibor
Sr. Member
****
Offline Offline

Activity: 348


View Profile
August 19, 2013, 11:45:58 PM
 #6474

What are the current recommended bitcoind settings (blocksize etc...). Seen various answers in past but would like to know current thinking. Am mining with a 55ghash asic.

Currently have between 0.1 and 0.3 getwork latency. And have 1.8%DOA from web page. Actual share stats I can not say as only been mining a few hours so are unreliable.

Thanks
daemondazz
Sr. Member
****
Offline Offline

Activity: 294



View Profile
August 20, 2013, 12:13:08 AM
 #6475

Thanks for the feedback guys, it sounds to me like there are no major issues with my concept and there may be some support for the service, so I'll continue with this.

P2Pool is modified to log all submitted shares with diff >= 25 (this is already completed - my patch provides a command line option to specify a logging function. I plan on submitting this to forrestv for inclusion upstream)

I have now done a push request to forrestv's GitHub repo for p2pool for the logging function: https://github.com/forrestv/p2pool/pull/127

The patch calls the logging function for all shares that are submitted by clients, it's up to the called function to perform any filtering needed, such as submitted_diff >= 25.

Computers, Amateur Radio, Electronics, Aviation - 1dazzrAbMqNu6cUwh2dtYckNygG7jKs8S
TreasureSeeker
Sr. Member
****
Offline Offline

Activity: 427



View Profile WWW
August 20, 2013, 02:45:31 AM
 #6476

my LTC p2pool v13 reports in the log file that share difficulty is >6, while on the web UI it's around 1.  I'm tending to believe the log file, because cgminer hasn't scored a share in 2 days, but I have several shares over 64K difficulty (which equates to diff=1, if I understand cgminer's stats correctly).  Why does p2pool report 2 different difficulties?

The node is here: http://192.241.177.9:9327/static/.  I've disconnected my miners because I think the difficulty is just too great for my hashing power. 

I'm getting the same situation at http://treasurequarry.com:9844/static/

At the moment, for example, the logs show Share difficulty: 0.516141 whereas the share difficulty shown on the stats page is  0.0513.

Similarly the logs show  Expected time to share: 27.3 seconds (equivalent to 0.455 minutes) whereas the stats page shows 0.0459 minutes.


Fun & Friendly p2pool Mining at TreasureQuarry.  Litecoin http://litecoin.treasurequarry.com:9327 Dash p2pool  http://dash.treasurequarry.com:7903  Infinitecoin http://treasurequarry.com:9844 Elephantcoin http://elephantcoin.treasurequarry.com:14777
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
August 20, 2013, 09:03:52 PM
 #6477

Well, now that I get a share every 8 hours or so, (yeah, I'll use code, but the log is also at www.nogleg.com/log)

Code:
2013-08-20 15:16:17.565104 P2Pool: 17386 shares in chain (17390 verified/17390 total) Peers: 46 (3 incoming)
2013-08-20 15:16:17.565184  Local: 13365MH/s in last 10.0 minutes Local dead on arrival: ~2.4% (1-4%) Expected time to share: 2.1 hours
2013-08-20 15:16:17.565215  Shares: 2 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~116.7% (39-117%) Current payout: 0.0075 BTC
2013-08-20 15:16:17.565258  Pool: 5019GH/s Stale rate: 14.3% Expected time to block: 12.1 hours
2013-08-20 15:16:18.131509 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:18.158050 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.036400 BTC including 54 transactions
2013-08-20 15:16:18.166192 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.036400 BTC including 54 transactions
2013-08-20 15:16:18.176351 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.036400 BTC including 54 transactions
2013-08-20 15:16:18.205053 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.004000 BTC including 6 transactions
2013-08-20 15:16:18.288808 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.004000 BTC including 6 transactions
2013-08-20 15:16:18.396579 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.004000 BTC including 6 transactions
2013-08-20 15:16:22.574397 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:22.577137 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:27.603467 P2Pool: 17385 shares in chain (17390 verified/17390 total) Peers: 46 (3 incoming)
2013-08-20 15:16:27.603554  Local: 13402MH/s in last 10.0 minutes Local dead on arrival: ~2.7% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:16:27.603579  Shares: 2 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~115.8% (39-116%) Current payout: 0.0075 BTC
2013-08-20 15:16:27.603621  Pool: 5002GH/s Stale rate: 13.7% Expected time to block: 12.1 hours
2013-08-20 15:16:27.606331 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:27.608862 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:32.611694 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:32.614301 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:33.213555 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:33.306933 Peer sent entire transaction c9025e1a4bef77edc8a51741e3379a0cb6f409a22a53f523514ef0464f4d2484 that was already received
2013-08-20 15:16:35.428101 Peer sent entire transaction 24aedb3571c20472a8a2c4e743960be4e1c81187603e534b7160a064a264a9be that was already received
2013-08-20 15:16:37.606924 P2Pool: 17385 shares in chain (17390 verified/17390 total) Peers: 46 (3 incoming)
2013-08-20 15:16:37.607004  Local: 13323MH/s in last 10.0 minutes Local dead on arrival: ~2.7% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:16:37.607040  Shares: 2 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~115.8% (39-116%) Current payout: 0.0075 BTC
2013-08-20 15:16:37.607093  Pool: 5002GH/s Stale rate: 13.7% Expected time to block: 12.1 hours
2013-08-20 15:16:37.617013 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:37.619625 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:42.622433 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:42.625125 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:47.637642 P2Pool: 17385 shares in chain (17390 verified/17390 total) Peers: 46 (3 incoming)
2013-08-20 15:16:47.637713  Local: 13142MH/s in last 10.0 minutes Local dead on arrival: ~2.8% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:16:47.637738  Shares: 2 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~115.8% (39-116%) Current payout: 0.0075 BTC
2013-08-20 15:16:47.637766  Pool: 5002GH/s Stale rate: 13.7% Expected time to block: 12.1 hours
2013-08-20 15:16:47.640420 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:47.642876 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:48.271120 Punishing share for 'Block-stale detected! height(4ac76984242296a478776acd237ea0535efcfef94f9ab7db90) < height(eb69262e94265b0ba230467985fa5067d446b1cb8ad00e345) or 19548732 != 19548732'! Jumping from bc72f1be to 3400b30e!
2013-08-20 15:16:51.838542 GOT SHARE! Ronald McDonald 61f091be prev 3400b30e age 33.66s DEAD ON ARRIVAL
2013-08-20 15:16:51.847710 > Error while processing Event callbacks:
2013-08-20 15:16:51.847775 > Traceback (most recent call last):
2013-08-20 15:16:51.847812 >   File "/home/zevus/p2pool.new/p2pool/bitcoin/worker_interface.py", line 136, in <lambda>
2013-08-20 15:16:51.847853 >     lambda header, user, coinbase_nonce: handler(header, user, pack.IntType(self._my_bits).pack(nonce) + coinbase_nonce),
2013-08-20 15:16:51.847884 >   File "/home/zevus/p2pool.new/p2pool/work.py", line 406, in got_response
2013-08-20 15:16:51.847924 >     self.node.set_best_share()
2013-08-20 15:16:51.847947 >   File "/home/zevus/p2pool.new/p2pool/node.py", line 297, in set_best_share
2013-08-20 15:16:51.847986 >     self.best_share_var.set(best)
2013-08-20 15:16:51.848010 >   File "/home/zevus/p2pool.new/p2pool/util/variable.py", line 74, in set
2013-08-20 15:16:51.848049 >     self.changed.happened(value)
2013-08-20 15:16:51.848071 > --- <exception caught here> ---
2013-08-20 15:16:51.848109 >   File "/home/zevus/p2pool.new/p2pool/util/variable.py", line 42, in happened
2013-08-20 15:16:51.848134 >     func(*event)
2013-08-20 15:16:51.848173 >   File "/home/zevus/p2pool.new/p2pool/node.py", line 96, in broadcast_share
2013-08-20 15:16:51.848196 >     peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.value, include_txs_with=[share_hash])
2013-08-20 15:16:51.848237 >   File "/home/zevus/p2pool.new/p2pool/p2p.py", line 290, in sendShares
2013-08-20 15:16:51.848261 >     assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2013-08-20 15:16:51.848306 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions
2013-08-20 15:16:51.855569 New work for worker! Difficulty: 2.800722 Share difficulty: 23291.224295 Total block value: 25.013000 BTC including 22 transactions
2013-08-20 15:16:51.863598 New work for worker! Difficulty: 2.800722 Share difficulty: 23291.224295 Total block value: 25.013000 BTC including 22 transactions
2013-08-20 15:16:51.869447 New work for worker! Difficulty: 2.800722 Share difficulty: 23291.224295 Total block value: 25.013000 BTC including 22 transactions
2013-08-20 15:16:57.670471 P2Pool: 17319 shares in chain (17323 verified/17323 total) Peers: 46 (3 incoming)
2013-08-20 15:16:57.670541  Local: 13060MH/s in last 10.0 minutes Local dead on arrival: ~3.0% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:16:57.670566  Shares: 3 (0 orphan, 0 dead) Stale rate: ~0.0% (0-57%) Efficiency: ~115.8% (50-116%) Current payout: 0.0113 BTC
2013-08-20 15:16:57.670608  Pool: 4974GH/s Stale rate: 13.7% Expected time to block: 12.2 hours
2013-08-20 15:17:07.705280 P2Pool: 17293 shares in chain (17297 verified/17297 total) Peers: 46 (3 incoming)
2013-08-20 15:17:07.705360  Local: 13103MH/s in last 10.0 minutes Local dead on arrival: ~2.9% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:17:07.705391  Shares: 3 (0 orphan, 0 dead) Stale rate: ~0.0% (0-57%) Efficiency: ~115.8% (50-116%) Current payout: 0.0113 BTC
2013-08-20 15:17:07.705434  Pool: 4974GH/s Stale rate: 13.7% Expected time to block: 12.2 hours
2013-08-20 15:17:15.784084 New work for worker! Difficulty: 2.788098 Share difficulty: 23075.733981 Total block value: 25.016200 BTC including 27 transactions
2013-08-20 15:17:15.789577 New work for worker! Difficulty: 2.788098 Share difficulty: 23075.733981 Total block value: 25.016200 BTC including 27 transactions
2013-08-20 15:17:15.795027 New work for worker! Difficulty: 2.788098 Share difficulty: 23075.733981 Total block value: 25.016200 BTC including 27 transactions
2013-08-20 15:17:17.740349 P2Pool: 17294 shares in chain (17298 verified/17298 total) Peers: 46 (3 incoming)
2013-08-20 15:17:17.740428  Local: 13015MH/s in last 10.0 minutes Local dead on arrival: ~3.1% (1-5%) Expected time to share: 2.1 hours
2013-08-20 15:17:17.740464  Shares: 3 (0 orphan, 1 dead) Stale rate: ~33.3% (6-80%) Efficiency: ~76.7% (23-108%) Current payout: 0.0075 BTC
2013-08-20 15:17:17.740521  Pool: 4862GH/s Stale rate: 13.0% Expected time to block: 12.5 hours

This one is different because it actually gives me an error message.  From what it says, it didn't even broadcast my share?  

It made new work for the new block @ 2013-08-20 15:16:18.396579 New work for worker! Difficulty: 2.584920 Share difficulty: 23330.319027 Total block value: 25.004000 BTC including 6 transactions

all that is between that and the found share is a lot of 'punishing' messages.  It also had 3 shares with 0 deads for 24 seconds, until someone else found a share (because my node never broadcast it, I think).  What's wrong w/ broadcasting a share with 5 transactions?  If I set the block max size to 1000, would it have broadcast it? 

I am guessing it would have, since there wouldn't have been any new transactions to add?

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
August 20, 2013, 09:09:14 PM
 #6478

all that is between that and the found share is a lot of 'punishing' messages.  It also had 3 shares with 0 deads for 24 seconds, until someone else found a share (because my node never broadcast it, I think).  What's wrong w/ broadcasting a share with 5 transactions?  If I set the block max size to 1000, would it have broadcast it? 

I am guessing it would have, since there wouldn't have been any new transactions to add?

i set maxblocksize to 1000 temporarily, unless someone has some better idea

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
TierNolan
Legendary
*
Offline Offline

Activity: 1036


View Profile
August 21, 2013, 01:14:37 PM
 #6479

How does the payout work for small miners?  Is there some kind of rule for dust payments?

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
August 21, 2013, 02:28:38 PM
 #6480

How does the payout work for small miners?  Is there some kind of rule for dust payments?

You get paid for each share you have found within the PPLNS window.  So the smallest payment you can get is for 1 share, which translates to ~0.003-0.004 BTC at the moment. 

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
Pages: « 1 ... 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 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 ... 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!