Bitcoin Forum
December 04, 2016, 12:31:46 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 [647] 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029435 times)
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 29, 2015, 09:42:56 PM
 #12921

the rest perhaps use a local node (P2Pool) only for backup ... that why, they don't monitor the command line.  Undecided
perhaps, it's a third-party that it install P2Pool node on server ... like in China farm production.

Anyone running or mining on P2Pool with any significant hash rate should be checking their pool stats regularly, I know I do and I'm relatively small-time.

Backup nodes are not a big deal right now, it would be nice if they upgraded, but we are only concerned with nodes that have an active hash rate.


Thank you for your efforts, windpath!

If the current trend continues (see http://bitcoin.sipa.be/ver-2k.png), BIP66 will take effect in 1.6 days. We are at 63% converted. It looks like at least a substantial fraction of P2Pool's hashrate won't make it in time... I'm a bit surprised that with the warning being displayed, things aren't moving faster. Also a bit angry that some of the alternative frontends hide the warnings.

Happy to help, it's important. Wink

Will keep working it.... Hope others help out...

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Meuh6879
Legendary
*
Offline Offline

Activity: 1078



View Profile
June 29, 2015, 11:42:12 PM
 #12922


French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 29, 2015, 11:50:33 PM
 #12923

Looking good, my node showing 65%...


forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
June 29, 2015, 11:51:41 PM
 #12924

Looking good, my node showing 65%...

Depends on the averaging period. Meuh6879 is using the "Hour" graph.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
yslyung
Legendary
*
Offline Offline

Activity: 1050


Mine Mine Mine


View Profile
June 30, 2015, 01:11:36 AM
 #12925

Looking good, my node showing 65%...

Depends on the averaging period. Meuh6879 is using the "Hour" graph.

hourly says 80% now. almost there.

just a noob question... those who did not update will Huh after bip66.
cwnage
Newbie
*
Offline Offline

Activity: 1


View Profile
June 30, 2015, 01:49:30 AM
 #12926

Stratum Mining on Litecoin appears broken?

If I force getwork/http it is fine.  minerd will follow X-Stratum and begin to fail unless you do --no-stratum.
I did not have this issue in 13.4, only in 14.0

Otherwise everything is difficulty 0, and i get nearly 100% DoA
and lots of messages:

Code:
su - p2pool -s /bin/sh -c "\
   PYTHONPATH=/opt/p2pool-14.0/python-lib/ \
   /opt/p2pool-14.0/run_p2pool.py \
      --net litecoin \
      --p2pool-node XXXXXXXXXXXXXXXX \
      --max-conns 64 \
      --outgoing-conns 10 \
      --address XXXXXXXXXXXXXXXXXXX \
      --fee 0.5  \
      --give-author 0.5" > /var/log/p2pool.log 2>&1 &

Code:
2015-06-29 21:14:13.132642 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.133144     Hash:   1d2eeab7fc4ffc98b8333441748eea519cefdb8da8b71d0b2f52f1fa909f13ae
2015-06-29 21:14:13.133674     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.143137 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.143468     Hash:   31d75b678a45540035edcd637ebea30f02043105c140a5b310ce36b6ca83f699
2015-06-29 21:14:13.143774     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.153865 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.154347     Hash:   76b0173d698ad8523d638469ba37a007cdea3be985976d573840b39df449820
2015-06-29 21:14:13.154546     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.160886 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.161167     Hash:   34675c62113c8611380a39d23258025a2a739114be566a40d77070b29877ccc2
2015-06-29 21:14:13.161326     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.167490 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.167690     Hash:   217f586c11b5524cc0049730118647d01e70435f20cb886a890c20b212e9708
2015-06-29 21:14:13.167878     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.173897 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.174112     Hash:   161c1cc9d7fb45dff96252f2eeaebe610461b2fabfc486872b210576f523ec65
2015-06-29 21:14:13.174257     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.180088 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.180311     Hash:   3d4137074e9b2b856f9d71178eb296963159fad23f21587744f9c374bc9598f4
2015-06-29 21:14:13.180605     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.187318 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.187527     Hash:   a636569c34c8eb72392e9e35ee321cab5463ebcddc4292662a07424d4db215
2015-06-29 21:14:13.187677     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.193268 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.193455     Hash:   29dcadf9157d9394c944e08d25898b1f0ccf473364e7eda3b3e938e7fc924173
2015-06-29 21:14:13.193621     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.199021 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.199202     Hash:   97d55ae789e5f6c675e0b702a230842dbf92cef959052097978ba2ee86d0cab
2015-06-29 21:14:13.199343     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.205663 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.205917     Hash:   eeb44f1c30af85709ab2fb743e559e04d733651f1ef28f99f43e3c658e0c326
2015-06-29 21:14:13.206271     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.212710 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.213022     Hash:   35f1a5ffa66c94272ba6900d88c2303c74988060068b2bbd33383f6997ee8ccc
2015-06-29 21:14:13.213191     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.219176 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.219362     Hash:   112b5f61f2d44780a394e769a091d933a8156319d127b88d9af25f90c29fa27b
2015-06-29 21:14:13.219573     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.226299 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.226499     Hash:   33bec935af85a4f49287a7d278887fc5f13eb12dac09fb04dc32e9a11598c2ed
2015-06-29 21:14:13.226644     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.232642 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.232922     Hash:   1c1cf0d9eb403e8b323951b7079f6557059a6320d98b831ba9ec61e2a8f78017
2015-06-29 21:14:13.233250     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.239681 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.239962     Hash:   3e27e2a5196de848344f4fe6c21c5c182dfb0a8944f581bcf365b28d543339d3
2015-06-29 21:14:13.240115     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.246266 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.246505     Hash:   e5ce2a321e1609c4ffa887061424db0fb65dd893187d61a5e3401012d17d963
2015-06-29 21:14:13.246654     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
2015-06-29 21:14:13.252367 Worker XXXXXXXXXXXX submitted share with hash > target:
2015-06-29 21:14:13.252547     Hash:   39d87af01934f3b9595632c8524a49332a9cdfdbccf7a9a244998ab6cb9ffda8
2015-06-29 21:14:13.252690     Target: 3f8822278f5c840000000000000000000000000000000000000000000000
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
June 30, 2015, 01:56:18 AM
 #12927

Stratum Mining on Litecoin appears broken?

If I force getwork/http it is fine.  minerd will follow X-Stratum and begin to fail unless you do --no-stratum.
I did not have this issue in 13.4, only in 14.0

Otherwise everything is difficulty 0, and i get nearly 100% DoA
and lots of messages:

Hmm, thank you for reporting this. Some ... interesting things ... got merged in in pull request #210. Can you make an issue on GitHub? I'll look into it soon. For now, I don't recommend anyone besides Bitcoin users to use 14.0.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 30, 2015, 02:06:46 AM
 #12928

Looking good, my node showing 65%...

Depends on the averaging period. Meuh6879 is using the "Hour" graph.

Yep hour at 73....

CartmanSPC
Legendary
*
Offline Offline

Activity: 1148



View Profile WWW
June 30, 2015, 06:43:09 AM
 #12929

just thought I'd pop by here and post a little "keep a local copy of
p2pool up to date" I noticed windpath back there with a
rm -rf p2pool ; git clone p2pool - shocking display man!

Wow, good stuff Polyatomic...Thank you! Been looking for something like this.

CartmanSPC
Legendary
*
Offline Offline

Activity: 1148



View Profile WWW
June 30, 2015, 06:55:30 AM
 #12930

Stratum Mining on Litecoin appears broken?

i get nearly 100% DoA
and lots of messages:

Hmm, thank you for reporting this. Some ... interesting things ... got merged in in pull request #210. Can you make an issue on GitHub? I'll look into it soon. For now, I don't recommend anyone besides Bitcoin users to use 14.0.

forrestv, I saw his github issue and replied there before I saw it was being discussed in this thread (spent the better part of the day catching up).

As I replied on github I believe it is ce9e5a2 causing the problem as reverting that got him (and one other person) working. I myself saw this happening when trying to use that commit (with alts) some time ago and had to revert it.

jtoomim
Hero Member
*****
Offline Offline

Activity: 555


View Profile WWW
June 30, 2015, 07:06:36 AM
 #12931

We're not going to make it at this rate.

I see 65% are using version 14. Since we have to achieve 95%, it might sound like we're 2/3 of the way there. In reality, it's much worse than that. What we actually have to do is reduce the amount of hashrate still on the old version by a factor of 7. We need to cut the amount of hashrate using the old version in half almost three times to get there.

Each effort we make to publish about the hard fork will convince the easiest people to reach. The ones left behind will be harder. This means that going from 70% to 85% will be harder than going from 0% to 50% was.

Let's assume we only make it to 94%. If we continue to reward people on version 13 even after BIP66 takes effect, then both those on version 13 and 14 will get about 94% of what their work is worth (assuming 80% conversion to 14). Since the ones on 14 are the people who are paying attention, they will quickly notice that they're not getting paid as much as they ought to, and a few will abandon p2pool. This will increase the proportion using 13, which strengthens the incentive for v14 users to leave. The end result is that p2pool is left to a handful of people who aren't paying attention and aren't making any revenue. Basically, p2pool dies, and during its death throes the people who are slow to leave lose out on mining revenue.

On the other hand, if we stop rewarding v13 before BIP66, then a few people who aren't paying attention lose some money. They might notice that their stale share rate increases dramatically, or they might not. People who are on v14 continue to make as much revenue as they deserve, and as soon as a person on v13 notices something is wrong, they either switch to a traditional pool or they upgrade to v14. The end result is that p2pool shrinks at most by whatever percentage is left on v13. A few people will get butthurt. P2pool survives.

I think that the amount of time during which both BIP66 is in effect and which v13 users are rewarded for their efforts should be zero. My preference would be to publish a version of p2pool that excludes v13 from the share chain 12 to 24 hours before BIP66.

Forrestv, if we did this, would we have to hard fork again to v15, and have another consensus detection round to eliminate v13, or is it possible to make existing v14 nodes exclude v13 without another software upgrade?

Would it be better to just initiate a new p2pool share chain with no v13 (or v14) blocks in it, and have it be a parallel system to the existing long p2pool share chain?

Hosting bitcoin miners for $75 to $90/kW/month on clean, cheap hydro power.
http://Toom.im
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
June 30, 2015, 07:34:12 AM
 #12932

jtoomim, did you see my last response to you? The situation is dire, but nowhere near as dire as you think. All non-14.0 miners can be separated from once BIP66 takes effect, so people who have upgraded will be at no disadvantage.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
jtoomim
Hero Member
*****
Offline Offline

Activity: 555


View Profile WWW
June 30, 2015, 09:05:47 AM
 #12933

That's the point at which the automatic switchover would take place, but it's possible to manually trigger it too. I'll do that once BIP66 takes effect, if necessary.

Yes, I saw this, but I guess I misunderstood it. When you said "manually trigger it", I didn't understand exactly what you meant. In the absence of details of how that manual trigger would occur, I presumed that it would mean a local configuration change on each p2pool node or a small code change, requiring another update. Do you have a key that allows you to broadcast a message that tells all v14 nodes to switch over to v14 exclusive mode, or something like that?

Hosting bitcoin miners for $75 to $90/kW/month on clean, cheap hydro power.
http://Toom.im
Meuh6879
Legendary
*
Offline Offline

Activity: 1078



View Profile
June 30, 2015, 12:35:51 PM
 #12934


French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
June 30, 2015, 10:07:44 PM
 #12935

My bitcoind GetBlockTemplate latency is really suffering - I presume it's due to the clown who decided to "stress test" the network with spam?  Angry
jtoomim
Hero Member
*****
Offline Offline

Activity: 555


View Profile WWW
July 01, 2015, 01:35:32 AM
 #12936

My bitcoind GetBlockTemplate latency is really suffering - I presume it's due to the clown who decided to "stress test" the network with spam?  Angry

Yes. This is mostly due to more transactions in mempool, if my understanding is correct. This affects all of us on p2pool. This means that everybody's DOA and stale share rates will go up while the stress test is in progress. As such, your mining efficiency will only change if your GetBlockTemplate latency is affected more (or less) than other p2pool nodes' latencies.

http://statoshi.info/dashboard/db/transactions

Compare the GBT latency graph with the blue line (txInMemoryPool) in the graph below it in this image:


Hosting bitcoin miners for $75 to $90/kW/month on clean, cheap hydro power.
http://Toom.im
Meuh6879
Legendary
*
Offline Offline

Activity: 1078



View Profile
July 02, 2015, 01:44:02 PM
 #12937

Not high, the indicator on the command box ...  Tongue

Code:
2015-07-02 02:45:17.763000 Switchover imminent. Upgraded: 67.436% Threshold: 95.000%

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
yslyung
Legendary
*
Offline Offline

Activity: 1050


Mine Mine Mine


View Profile
July 02, 2015, 04:49:00 PM
 #12938

yeah i see that too

2015-07-03 00:50:49.745000  Pool: 2163TH/s Stale rate: 14.9% Expected time to block: 1.1 days
2015-07-03 00:50:50.927000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.927000
2015-07-03 00:50:50.958000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.958000
2015-07-03 00:50:50.983000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:50.984000
2015-07-03 00:50:51.018000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.018000
2015-07-03 00:50:51.042000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.042000
2015-07-03 00:50:51.066000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.066000
2015-07-03 00:50:51.096000 Switchover imminent. Upgraded: 67.767% Threshold: 95.000%
2015-07-03 00:50:51.096000
2015-07-03 00:50:52.763000 P2Pool: 17357 shares in chain (17361 verified/17361 total) Peers: 10 (0 incoming)


still got the blanks.
luthermarcus
Full Member
***
Offline Offline

Activity: 206



View Profile
July 03, 2015, 01:06:24 AM
 #12939

still got the blanks.
[/quote]

I just upgraded and I don't see any off the blanks you guys are getting.
jtoomim
Hero Member
*****
Offline Offline

Activity: 555


View Profile WWW
July 03, 2015, 05:56:57 AM
 #12940

Has BIP66 taken effect yet?

Hosting bitcoin miners for $75 to $90/kW/month on clean, cheap hydro power.
http://Toom.im
Pages: « 1 ... 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 [647] 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 ... 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!