Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 334. (Read 2591964 times)

legendary
Activity: 1258
Merit: 1027
Reserved for updates and FAQ


FAQ


1. Will S3 support p2pool?

The simple answer is we will. Bitmain has a very sincere interesting with p2pool, and we have invest human resource into this area. Sadly our firmware may not be able to give you a firm yes that we support p2pool right now, but we promise we will contribute much more to the p2pool mining idea than most of those who support p2pool mining well already.


legendary
Activity: 1540
Merit: 1001
Quote
Petahash predictions

With the network running at roughly 140 petahashes per second, moderator Jez asked the mining panel how much hashing power they foresee by year’s end. Here’s what they had to say:

Timo Hanke: 600 PH/s.

Naveen Sherwani: 350-400 PH/s.

Dave Carlson: 350-400 PH/s.

Marc Aafjes: More than 600 PH/s.

http://www.coindesk.com/coinsummit-day-two-mining-superpowers-51-challenge/

And none of it usable with p2pool due to lack of compatibility....... Roll Eyes

Pat, I get your frustration, but stating that "none" of it is compatible is just blatantly false.

Spondoolies gear is working fine and Bitmain has assured us S3s will be compatible... There are many other pieces of mining hardware that work just fine on p2pool...

In fact the only 2 pieces I'm aware of that don't work as expected are the S2 and BitFury, and that stinks, but it's hardly all encompassing...

The silence from Bitmain makes me skeptical the S3s will work with p2pool.  Especially since the requests to them came very late in their development, if not at the end.  Personally, I'll believe it when I see it.

M
legendary
Activity: 1258
Merit: 1027
Quote
Petahash predictions

With the network running at roughly 140 petahashes per second, moderator Jez asked the mining panel how much hashing power they foresee by year’s end. Here’s what they had to say:

Timo Hanke: 600 PH/s.

Naveen Sherwani: 350-400 PH/s.

Dave Carlson: 350-400 PH/s.

Marc Aafjes: More than 600 PH/s.

http://www.coindesk.com/coinsummit-day-two-mining-superpowers-51-challenge/

And none of it usable with p2pool due to lack of compatibility....... Roll Eyes

Pat, I get your frustration, but stating that "none" of it is compatible is just blatantly false.

Spondoolies gear is working fine and Bitmain has assured us S3s will be compatible... There are many other pieces of mining hardware that work just fine on p2pool...

In fact the only 2 pieces I'm aware of that don't work as expected are the S2 and BitFury, and that stinks, but it's hardly all encompassing...

 

hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Quote
Petahash predictions

With the network running at roughly 140 petahashes per second, moderator Jez asked the mining panel how much hashing power they foresee by year’s end. Here’s what they had to say:

Timo Hanke: 600 PH/s.

Naveen Sherwani: 350-400 PH/s.

Dave Carlson: 350-400 PH/s.

Marc Aafjes: More than 600 PH/s.

http://www.coindesk.com/coinsummit-day-two-mining-superpowers-51-challenge/

And none of it usable with p2pool due to lack of compatibility....... Roll Eyes
legendary
Activity: 1258
Merit: 1027
Quote
Petahash predictions

With the network running at roughly 140 petahashes per second, moderator Jez asked the mining panel how much hashing power they foresee by year’s end. Here’s what they had to say:

Timo Hanke: 600 PH/s.

Naveen Sherwani: 350-400 PH/s.

Dave Carlson: 350-400 PH/s.

Marc Aafjes: More than 600 PH/s.

http://www.coindesk.com/coinsummit-day-two-mining-superpowers-51-challenge/
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Wow, aren't we lucky, scrypt updates and a fixed formatting in file.  What an amazing update!!!  It'd be nice to see some actual updates applied for bitcoin.  Let's post a month ago crying about donations going down and then not support the group you just whined to at all.  Glad I didn't decide to turn my donations back on and I won't until we get someone running this project that can actually do some meaningful updates.

Exactly - this is what I said when I saw the "updates"  Roll Eyes

Great. More alt-coins that can't be mined....... Roll Eyes

Really, wtf is he doing faffing around with alt-coin additions when there are far more urgent things to be done? Concentrate on the btc side of p2pool - there are plenty of forks for alt-coins already, ffs.

Waste of time & space.
sr. member
Activity: 543
Merit: 250
Orjinal üyelik ToRiKaN banlanalı asır ol
Wow, aren't we lucky, scrypt updates and a fixed formatting in file.  What an amazing update!!!  It'd be nice to see some actual updates applied for bitcoin.  Let's post a month ago crying about donations going down and then not support the group you just whined to at all.  Glad I didn't decide to turn my donations back on and I won't until we get someone running this project that can actually do some meaningful updates.
sr. member
Activity: 543
Merit: 250
Orjinal üyelik ToRiKaN banlanalı asır ol
The 51% on p2pool would not be an issue.

All that means is that they would get to pick the criteria for transactions included in 51% of the blocks found by the pool. If I'm PETAMINE I'm going to want the juicy transactions just like any other miner...

I'm just trying to understand the technical reason behind this. I've heard a lot of people say "the share chain is vulnerable to a 51% attack just like the block chain", as a reason not to put a lot of hashpower...is it just misinformation?

Well lets follow eleuthria's example, lets assume someone has an absolutely horrible connection, solves a share just behind, or the same time as someone else, but their node hasn't received the new share to the chain.  They now enter a race and the next share solved is the one that creates the chain and orphans the other share.  They have a 50% or better chance of solving that share and forcing the network to accept their share as the valid one.  Now this could result in them finding a higher share % than they would normally have.

Now let's same someone is trying to do this intentionally, if they had 50% or better of the network hashrate, they could more or less reject all shares that aren't theirs, effectively increase everyone else's Orphan/DOA shares and taking a much larger % of the shares that were solved. 

Effectively, P2Pool is subject to all the downfalls of the bitcoin network, but it's a much smaller network, that if you could get all of the current hardware to work properly on, you could more easily take 51% or better of the network's hashrate since our hashrate is only 600TH/s.  Let's say for instance cex.io wanted to hide their network hashrate, if they could get their miners to work on our network, they could effectively mine on P2Pool.  Making the difficulty skyrocket and they could modify the code with the sharechain to only accept their shares, they rendering everyone else's work effectively useless, while making it impossible for the small to midsized miners to mine on it.
hero member
Activity: 994
Merit: 1000
The 51% on p2pool would not be an issue.

All that means is that they would get to pick the criteria for transactions included in 51% of the blocks found by the pool. If I'm PETAMINE I'm going to want the juicy transactions just like any other miner...

I'm just trying to understand the technical reason behind this. I've heard a lot of people say "the share chain is vulnerable to a 51% attack just like the block chain", as a reason not to put a lot of hashpower...is it just misinformation?
sr. member
Activity: 434
Merit: 250
anyone using a neptune on P2Pool? what is your stability like? shares OK?
member
Activity: 85
Merit: 10
Wow did someone big just join the network?  We're up to almost a Petahash currently.


I was just going to say... it has been jumping from 800th to 500 th back to 900 th down to 450 th and now
1 PH...?

And my payouts are dropping big time

Well we when your payouts drop like that the payout frequency corrects it, because at 1 PH we were at an 18-19 hr expected block time, not 1d 7hr.  So in the end you make the same.  Larger and less frequent, or smaller and more frequent, I'd actually vote for smaller and more frequent as that lowers variance.  So each share would get 3-4 payouts, not 2-3.

Yes I see that and would like to see it ..........
sr. member
Activity: 543
Merit: 250
Orjinal üyelik ToRiKaN banlanalı asır ol
Wow did someone big just join the network?  We're up to almost a Petahash currently.


I was just going to say... it has been jumping from 800th to 500 th back to 900 th down to 450 th and now
1 PH...?

And my payouts are dropping big time

Well we when your payouts drop like that the payout frequency corrects it, because at 1 PH we were at an 18-19 hr expected block time, not 1d 7hr.  So in the end you make the same.  Larger and less frequent, or smaller and more frequent, I'd actually vote for smaller and more frequent as that lowers variance.  So each share would get 3-4 payouts, not 2-3.
newbie
Activity: 16
Merit: 0
And back below 1PH Cheesy
member
Activity: 85
Merit: 10
Wow did someone big just join the network?  We're up to almost a Petahash currently.


I was just going to say... it has been jumping from 800th to 500 th back to 900 th down to 450 th and now
1 PH...?

And my payouts are dropping big time
sr. member
Activity: 543
Merit: 250
Orjinal üyelik ToRiKaN banlanalı asır ol
Wow did someone big just join the network?  We're up to almost a Petahash currently.

Edit: Actually broke it while I was writing this.
sr. member
Activity: 434
Merit: 250
newbie
Activity: 16
Merit: 0
Good old variance Tongue
legendary
Activity: 1258
Merit: 1027
Ahhh ok that makes sense, so if I found 100 shares 5 of them would go to the pool

About 5... Also subject to variance so it not always exact...
newbie
Activity: 16
Merit: 0
Ahhh ok that makes sense, so if I found 100 shares 5 of them would go to the pool
legendary
Activity: 1258
Merit: 1027
Quote from: sconklin321

It's actually -a to set the node payout address, -f is the fee %.

That is correct, good catch, thanks!
Jump to: