Bitcoin Forum
April 25, 2024, 12:02:29 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 698 699 700 701 702 703 704 705 706 [707] 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 ... 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2591624 times)
notbatman
Legendary
*
Offline Offline

Activity: 2212
Merit: 1038



View Profile
January 11, 2016, 02:53:01 AM
Last edit: January 11, 2016, 04:40:00 AM by notbatman
 #14121

I've been running the p2pool v15.0 windows binary (sandboxed) for a bit now but I've noticed that every incoming connection is from a v14 client:

2016-01-10 18:38:20.709000 Incoming connection to peer 195.208.39.210:4647 established. p2pool version: 1400 '14.0
2016-01-10 18:38:49.754000 Incoming connection to peer 80.169.241.69:38395 established. p2pool version: 1400 '14.0-23-g6514fd8-dirty'
2016-01-10 18:39:50.613000 Incoming connection to peer 71.8.220.126:39040 established. p2pool version: 1400 '14.0'
2016-01-10 18:41:11.713000 Incoming connection to peer 208.111.52.2:59707 established. p2pool version: 1400 '14.0-9-g4e5afe9'
2016-01-10 18:42:01.361000 Incoming connection to peer 89.22.129.82:50956 established. p2pool version: 1400 '14.0-9-g4e5afe9'
2016-01-10 18:44:14.349000 Incoming connection to peer 212.18.229.18:37078 established. p2pool version: 1400 '14.0-23-g6514fd8'

2016-01-10 18:52:31.344000 P2Pool: 17354 shares in chain (9147 verified/17359 total) Peers: 6 (0 incoming)


Am I the only user running p2pool v15 what's going on here?

Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714046549
Hero Member
*
Offline Offline

Posts: 1714046549

View Profile Personal Message (Offline)

Ignore
1714046549
Reply with quote  #2

1714046549
Report to moderator
1714046549
Hero Member
*
Offline Offline

Posts: 1714046549

View Profile Personal Message (Offline)

Ignore
1714046549
Reply with quote  #2

1714046549
Report to moderator
notbatman
Legendary
*
Offline Offline

Activity: 2212
Merit: 1038



View Profile
January 11, 2016, 03:39:48 AM
 #14122

Now some kind of surge/EMP just shut down both my bitcoind/p2pool node and my Ethereum GPU rig that are on separate circuits I might add. Lights that are on the same circuits didn't even flicker, 'the hell man?
nicklello
Member
**
Offline Offline

Activity: 193
Merit: 10


View Profile
January 11, 2016, 10:06:53 AM
 #14123


I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?
notbatman
Legendary
*
Offline Offline

Activity: 2212
Merit: 1038



View Profile
January 11, 2016, 10:42:42 AM
 #14124

Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !

I get extremely bad vibes looking at that picture, she's definitely attractive but I don't think she's a nice person to be around. There's a lot of talk about satanic/psychopathic people in Hollywood.

To stay on-topic I agree, p2pool isn't going away any time soon.
-ck
Legendary
*
Offline Offline

Activity: 4088
Merit: 1631


Ruu \o/


View Profile WWW
January 11, 2016, 10:53:07 AM
 #14125


I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?
Nothing quite like a conspiracy theory... they come up every time luck doesn't look so good. Nope, it's just that p2pool's hashrate is insignificant.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
notbatman
Legendary
*
Offline Offline

Activity: 2212
Merit: 1038



View Profile
January 11, 2016, 10:55:10 AM
 #14126


I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?

The luck of one pool has absolutely no effect on the luck of other pools. Rapidly rising difficulty is to blame here.
nicklello
Member
**
Offline Offline

Activity: 193
Merit: 10


View Profile
January 11, 2016, 10:57:04 AM
 #14127


I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?
Nothing quite like a conspiracy theory... they come up every time luck doesn't look so good. Nope, it's just that p2pool's hashrate is insignificant.

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...
-ck
Legendary
*
Offline Offline

Activity: 4088
Merit: 1631


Ruu \o/


View Profile WWW
January 11, 2016, 11:21:01 AM
 #14128

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...
Same thing - bad luck. Look around and you'll see not all pools are having bad luck. Overall luck is "average" across all the pools. Some are having a streak of good luck.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
idonothave
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
January 11, 2016, 12:34:11 PM
 #14129

hypotethical question
if kano used his pool to mine with p2pool as a node, would it be more efficient mining fot his pool or not?
nicklello
Member
**
Offline Offline

Activity: 193
Merit: 10


View Profile
January 11, 2016, 12:40:32 PM
 #14130

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...
Same thing - bad luck. Look around and you'll see not all pools are having bad luck. Overall luck is "average" across all the pools. Some are having a streak of good luck.

I guess I've just selected a bad set of pools to look at then.
nicklello
Member
**
Offline Offline

Activity: 193
Merit: 10


View Profile
January 11, 2016, 12:47:19 PM
 #14131

hypotethical question
if kano used his pool to mine with p2pool as a node, would it be more efficient mining fot his pool or not?

Interesting idea... however I suspect Kano wouldn't want to risk the stability of his pool software (I'm assuming you mean altering/extending ckpool so shares are distributed with/like p2pool).

I'd prefer to ask: What would need to be different within bitcoin to make solo mining feasible again ?

I suspect Smaller (not Larger) blocks would be the solution as it would give the 'small' guy (< 1Th/s) a better chance of an income......
notbatman
Legendary
*
Offline Offline

Activity: 2212
Merit: 1038



View Profile
January 11, 2016, 02:10:32 PM
 #14132

OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.
windpath
Legendary
*
Offline Offline

Activity: 1258
Merit: 1027


View Profile WWW
January 11, 2016, 02:47:00 PM
 #14133

OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

Just wrap them in tinfoil, then you'll be protected... Wink
AndreyNag
Member
**
Offline Offline

Activity: 88
Merit: 10


View Profile WWW
January 11, 2016, 02:53:37 PM
 #14134

Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !
Tell me "Big boy" why P2pool is here since 2011, but now falls in a deep hole. And when the falls end and pool rise up?
Today global power is from 0.7 to 1Ph and 123 hours of waiting - do You think this is normal and nothing to worry about?
If you really think that you have leed balls.

Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1011



View Profile
January 11, 2016, 03:53:00 PM
 #14135

P2Pool is a support (backup) for all pools of bitcoin around the world ... usually farm start, on P2Pool, different grid to measure the performance, and then switch to local stratum server.

P2Pool never die at the end, because, it's the last wall of mining process (DDoS proof).

The power of P2Pool, you earn the SAME AMOUNT of bitcoins when you are on a big pool or on the P2Pool ... after 3 months.  Roll Eyes

I mine on P2Pool since 2 years.
Cassey
Sr. Member
****
Offline Offline

Activity: 470
Merit: 250

Better to have 100 friends than 100 rubles


View Profile
January 11, 2016, 05:09:16 PM
Last edit: January 11, 2016, 07:48:07 PM by Cassey
 #14136

Hi all.  Thought I'd check out p2pool for my local 16.5TH of mining.

Happy to say it all went smoothly for doing straight bitcoin mining.  Saw a few python exceptions during startup, but once it got initialized, it appears to be working fine.

I'm not having as much luck with merged mining bitcoin and namecoin.

Syntactically all appears fine, and initialization proceeds as above.  However I see:



Reoccurring frequently in the console output.  All my miners are also showing a Diff of 1, which is a change.

Any thoughts?

Edit:  Also seem to be stuck at 8 connections, even though I'm starting up with " --max-conns=256" and my bitcoind has 19 connections.

Pool stats at:  http://ngspoe.carpenter-farms.us:9332/static/

Update:  Found my stupid mistake, was specifying namecoins coin port instead of the rpcport on the --merged line.  The Diff of 1 also cleared itself up after a few minutes.

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Cassey
windpath
Legendary
*
Offline Offline

Activity: 1258
Merit: 1027


View Profile WWW
January 11, 2016, 08:56:34 PM
 #14137

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...
Cassey
Sr. Member
****
Offline Offline

Activity: 470
Merit: 250

Better to have 100 friends than 100 rubles


View Profile
January 11, 2016, 09:08:52 PM
 #14138

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.

Cassey
idonothave
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
January 12, 2016, 07:49:22 AM
 #14139

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.

you do not need to bind with every existing node. I run my node satisfied with 3 out 1 in connections and relaynode by Matt. I use github bitcoind with no conf change with <0.2s gbt latency (0.165s daily average just now, monthly average 0.188s) and github p2pool 15.0-11 keeping both in last version.
idonothave
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
January 12, 2016, 11:16:23 AM
 #14140

if anybody interested to mine in central Europe, Czech republic, there is a node http://185.73.103.2:9332/
fee 0.9%, author donation 0.1%
johndoe stats @ http://185.73.103.2:9332/static/jd/

plans

to add spare hw to backup it using load balancing tools
to backup it via another independent internet connection
to build website @ sexy domain name
Pages: « 1 ... 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 698 699 700 701 702 703 704 705 706 [707] 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 ... 814 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!