[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[IYFTech]

Seasons greetings everyone!

More xmas blocks on the way - I feel it in my bonez 

Happy Christmas!  Looks like there was a block under the tree

Just found one in my stocking too!! 

[PatMan]

Seasons greetings everyone!

More xmas blocks on the way - I feel it in my bonez 

Five xmas day blocks - my bonez was right! 

[yslyung]

ho ho ho merry xmas to all !

back to p2p 0% Fees captminerp2pool.ddns.net:9332 60+ TH/s p2pool & hungry for more !

Running on 6 cores (12 threads) @ 4.0ghz, 16GB ram @ 2400mhz, qt & p2p running on real-time priority, 256gb SSD

All miners from all over are more than welcomed to join my pool especially to those who are located in asia.

many more blocks to come !

how can i be added to the p2pool list ? I'm also looking to expand further & add more nodes too.  

[idonothave]

ho ho ho merry xmas to all !

back to p2p 0% Fees captminerp2pool.ddns.net:9332 60+ TH/s p2pool & hungry for more !

Running on 6 cores (12 threads) @ 4.0ghz, 16GB ram @ 2400mhz, qt & p2p running on real-time priority, 256gb SSD

All miners from all over are more than welcomed to join my pool especially to those who are located in asia.

many more blocks to come !

how can i be added to the p2pool list ? I'm also looking to expand further & add more nodes too.  

It seems there are no income peers to Your node. Is it because of behind NAT or You did not allow it? It would be useful even for You even for other nodes to allow incomming peers if possible.

[yslyung]

ho ho ho merry xmas to all !

back to p2p 0% Fees captminerp2pool.ddns.net:9332 60+ TH/s p2pool & hungry for more !

Running on 6 cores (12 threads) @ 4.0ghz, 16GB ram @ 2400mhz, qt & p2p running on real-time priority, 256gb SSD

All miners from all over are more than welcomed to join my pool especially to those who are located in asia.

many more blocks to come !

how can i be added to the p2pool list ? I'm also looking to expand further & add more nodes too. 

It seems there are no income peers to Your node. Is it because of behind NAT or You did not allow it? It would be useful even for You even for other nodes to allow incomming peers if possible.

Just started the server, the incoming does come, they come & go, all ports open did not block anything but any tip will be greatly appreciated.

thx

[jcumins]

HMMM thats strange

I only show:

3 Blocks on 24th Ca local time
3 Blocks on 24th California local time.

Thats great.

[jcumins]

OOOOPS just checked that's a time zone issue.

[windpath]

Still hoping for a Bitcoin Bowl block!

[jedimstr]

Still hoping for a Bitcoin Bowl block!

+1

[windpath]

Still hoping for a Bitcoin Bowl block!

+1

Would be cool

Hell of a job by BitPay

"Our team has a goal to have 1,000,000 merchants accepting bitcoin within 2 years"



Edit: Image proxy not working: https://twitter.com/CoinCadence/status/548678314743705600

[jedimstr]

So the binaries are available now for Bitcoin Core 0.10 rc1

Here are the release notes:
https://github.com/bitcoin/bitcoin/blob/0.10/doc/release-notes.md

Anyone try it yet on their p2pool node. Curious if the new block out of order, header, and RPC changes have any compatibility issues with p2pool. The release notes make mention that some software may no longer be compatible with the way core works with blocks.

[yslyung]

So the binaries are available now for Bitcoin Core 0.10 rc1

Here are the release notes:
https://github.com/bitcoin/bitcoin/blob/0.10/doc/release-notes.md

Anyone try it yet on their p2pool node. Curious if the new block out of order, header, and RPC changes have any compatibility issues with p2pool. The release notes make mention that some software may no longer be compatible with the way core works with blocks.

ain't broken, don't fix it

just fine tuned my p2pool, working nicely now. will wait and see if there's any improvements later on with the new 0.10rc1

[PatMan]

Same here, I'll wait until the stable version is out.

[jedimstr]

The problem with everyone waiting for the stable version to be out is that it will leave no time for anyone to execute any fixes needed to make p2pool compatible for 0.10.0 if needed. Release candidates (and betas) are sent out for testing for a reason.

That said, I'm probably gonna wait as well.  At least until the later Release Candidates (which there are always multiple).

As far as the "if it ain't broke" philosophy, I would follow that for certain things like miner configurations and hardware setup, but for something as important as Bitcoin Core, its a good idea to keep up with the rest of the network.  I wouldn't expect anyone here to still be running BitcoinD version 0.7.x or 0.8.x. Everyone should be on 0.9.3. Though we're not talking about a soft or hard fork situation, it helps the network to always be up-to-date with its core functionality.

[windpath]

I think this is relevant:

http://www.reddit.com/r/Bitcoin/comments/2qmrh8/bitcoin_093_came_out_in_september_but_still/

The question:

Bitcoin 0.9.3 came out in September but still doesn't even make up 50% of the network. Why? (self.Bitcoin)

As far as I know there is nothing controversial about 9.3 and yet it has been rejected by over half of the network. What is happening?

It seems weird if the answer is just laziness. Someone that runs a bitcoin node would presumably be a person that is fairly deep into bitcoin.

Is this effect a thing we are going to start to run into issues with? If non-controversial branches are failing to hit 50% is there a big risk that a branch that had more far reaching changes would struggle? Or is the consensus that all these updates are worthless to the normal person and a big update would excite the crowd into action?

Theymos's response (which I agree with):

Older versions are still supported, and they still contribute to the network. 0.10 can efficiently download the chain from nodes as old as 0.3.18, for example. Each new version tends to add a few new protocol features and improvements, but it's not necessary for everyone to upgrade. In fact, it's probably good if the majority of the network doesn't upgrade for several months in case the new version has a serious bug.

I don't think it is a huge concern short term, long term if there is a problem we will have to figure out how to get it fixed...

[jonnybravo0311]

I think this is relevant:

http://www.reddit.com/r/Bitcoin/comments/2qmrh8/bitcoin_093_came_out_in_september_but_still/

The question:

Bitcoin 0.9.3 came out in September but still doesn't even make up 50% of the network. Why? (self.Bitcoin)

As far as I know there is nothing controversial about 9.3 and yet it has been rejected by over half of the network. What is happening?

It seems weird if the answer is just laziness. Someone that runs a bitcoin node would presumably be a person that is fairly deep into bitcoin.

Is this effect a thing we are going to start to run into issues with? If non-controversial branches are failing to hit 50% is there a big risk that a branch that had more far reaching changes would struggle? Or is the consensus that all these updates are worthless to the normal person and a big update would excite the crowd into action?

Theymos's response (which I agree with):

Older versions are still supported, and they still contribute to the network. 0.10 can efficiently download the chain from nodes as old as 0.3.18, for example. Each new version tends to add a few new protocol features and improvements, but it's not necessary for everyone to upgrade. In fact, it's probably good if the majority of the network doesn't upgrade for several months in case the new version has a serious bug.

I don't think it is a huge concern short term, long term if there is a problem we will have to figure out how to get it fixed...

When the 0.9.x core was released, there was that whole heart bleed issue.  A lot of people never bothered upgrading from the 0.8.x version because of this.

[windpath]

...

When the 0.9.x core was released, there was that whole heart bleed issue.  A lot of people never bothered upgrading from the 0.8.x version because of this.

Agreed, I jumped into that upgrade and was vulnerable when Heartbleed was discovered (don't keep coins on my nodes so no worries).

It's worth noting that Heartbleed had nothing to do with Bitcoin but was a bug in OpenSSL...

[PatMan]

Soooo, fired up the S5 and......it's a dud 



One board not hashing.......hay ho.

[PatMan]

Update: Make that a half dead dud........

[jonnybravo0311]

Update: Make that a half dead dud........

Awww man... that sucks .  Hopefully Bitmain will hook you up with a speedy RMA and a bit of compensation (good luck with that, by the way).