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

[RandomQ]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

I just did an update to (version 0.11.2-10-g34c9e88)

is this the update you are talking about?

[1714007096]

1714007096

[1714007096]

1714007096

[1714007096]

1714007096

[rav3n_pl]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

I just did an update to (version 0.11.2-10-g34c9e88)

is this the update you are talking about?

forrestv-p2pool-0.11.2-10-g34c9e88 is latest atm.
Using link https://github.com/forrestv/p2pool/zipball/master you will download latest source zip.

[rav3n_pl]

windpws?

Complied w/o litecoin_script - works only on bitcoin network!
forrestv-p2pool-0.11.2-10-g34c9e88_win32_nolitecoin.zip
http://sdrv.ms/MMLxhq
Happy mining

[Ente]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

Not to be a dick and all.. But why is not forrestv announcing this? The (main? only?) developer, you know? I am somewhat careful with code from the Bitcoin universe, where wallets are involved and stuff. "Prattler" has a low postcount, shouts, makes large promises and makes it totally urgent with the possibility to lose (forked) Bitcoin if one is not to react immediately.

I am sure there is an easy explanation to this, but still my eyebrow stays raised until I hear more. Forrestv is logged in, too, actually.

Ente

[rav3n_pl]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

Not to be a dick and all.. But why is not forrestv announcing this? The (main? only?) developer, you know? I am somewhat careful with code from the Bitcoin universe, where wallets are involved and stuff. "Prattler" has a low postcount, shouts, makes large promises and makes it totally urgent with the possibility to lose (forked) Bitcoin if one is not to react immediately.

I am sure there is an easy explanation to this, but still my eyebrow stays raised until I hear more. Forrestv is logged in, too, actually.

Ente

There is one big change in block detection: new block is passed thru pool nodes quicker than trhu bitcoin network. This should make orphans much less likely to occur.
Time to update IMO

[kano]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

Not to be a dick and all.. But why is not forrestv announcing this? The (main? only?) developer, you know? I am somewhat careful with code from the Bitcoin universe, where wallets are involved and stuff. "Prattler" has a low postcount, shouts, makes large promises and makes it totally urgent with the possibility to lose (forked) Bitcoin if one is not to react immediately.

I am sure there is an easy explanation to this, but still my eyebrow stays raised until I hear more. Forrestv is logged in, too, actually.

Ente

Except it's forrestv's git ... so unless someone compromised it ...

[stevegee58]

I'm waiting for forrestv personally.

[Ente]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

Not to be a dick and all.. But why is not forrestv announcing this? The (main? only?) developer, you know? I am somewhat careful with code from the Bitcoin universe, where wallets are involved and stuff. "Prattler" has a low postcount, shouts, makes large promises and makes it totally urgent with the possibility to lose (forked) Bitcoin if one is not to react immediately.

I am sure there is an easy explanation to this, but still my eyebrow stays raised until I hear more. Forrestv is logged in, too, actually.

Ente

Except it's forrestv's git ... so unless someone compromised it ...

Exactly. That's why I have a "raised eyebrow", and am not running around in circles, shouting and having foam on my mouth ;-)

But in this combination, I don't trust GIT (which I do not understand in every detail) enough without having more info.

Ente

[Prattler]

Not to be a dick and all.. But why is not forrestv announcing this?

It's not being rushed, because it needs more testing. So update and be that tester, because due to very high orphans we're losing money (>2%) NOW!

And yeah, it's all in the official p2pool git run by forrestv.

[Ente]

It's not being rushed[..]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

If this is not rushing, I don't know what is..

[..]we're losing money (>2%) NOW!

"Now"? If we are, we are since months now!

And yeah, it's all in the official p2pool git run by forrestv.

My skeptizism boils down to: Who are you, in respect to p2pool? User, dev, guy who had forrestv on the phone an hour ago?

Ente

[Prattler]

If this is not rushing, I don't know what is..

The dev(s) are not rushing this change and I'm just urging them to be more aggressive about it Because the change looks very useful.

My skeptizism boils down to: Who are you, in respect to p2pool? User, dev, guy who had forrestv on the phone an hour ago?

A user.

[Ente]

If this is not rushing, I don't know what is..

The dev(s) are not rushing this change and I'm just urging them to be more aggressive about it Because the change looks very useful.

My skeptizism boils down to: Who are you, in respect to p2pool? User, dev, guy who had forrestv on the phone an hour ago?

A user.

Thank you for your patience and explaining the situation! :-)

Ente

[Ed]

Because the change looks very useful.

is still happen

Code:

2012-06-15 14:38:14.391000 Skipping from block 6b72058de518d5ba2687969e85a49054bed97dbe6d24b824aae to block 59a1df0c90c7fff4adf5e25ebf13b6b1f18b93bd8d73145c79c!
2012-06-15 14:38:15.654000 > ---> LOST CONTACT WITH BITCOIND for 1.0 minutes! Check that it isn't frozen or dead! <---

not as very often as last night, but reject level is too high

[kjj]

Because the change looks very useful.

is still happen

Code:

2012-06-15 14:38:14.391000 Skipping from block 6b72058de518d5ba2687969e85a49054bed97dbe6d24b824aae to block 59a1df0c90c7fff4adf5e25ebf13b6b1f18b93bd8d73145c79c!
2012-06-15 14:38:15.654000 > ---> LOST CONTACT WITH BITCOIND for 1.0 minutes! Check that it isn't frozen or dead! <---

not as very often as last night, but reject level is too high

Did you upgrade to 0.6.2?  I've been getting TONS of these since I upgraded my p2pcoin nodes to 0.6.2.  I just posted in dev/tech about the CPU usage in that release.  Probably going to have to downgrade until it gets sorted out.

[Aseras]

It's not being rushed[..]

Some very important optimization changes have been made! It could reduce the block orphan rate from current 5%-15% to <1% (ideally).

https://github.com/forrestv/p2pool/commits/master

Everyone, please go update NOW!

Devs, please force this upgrade by splitting the chain, people will not update voluntarily

If this is not rushing, I don't know what is..

The last time a "forced change" and a fork happened, p2pool lost a third of it's hashes and they never returned. There's still 10% running the old version getting forked out there.

Worse when the force was implemented it kicked everyone out until a fixed version was updated and forced out again.

Forks are bad. Forced updates are bad. Rushing is very bad.

[Ed]

Did you upgrade to 0.6.2?

yes

Code:

"version" : 60200,
"protocolversion" : 60001,
"walletversion" : 10500,

problems started last night without any changes at my side

[cabin]

If I try and run the latest from git on windows it hangs at the line below. Nothing changed with my bitcoind, it is still 0.6.2.

2012-06-15 09:31:50.716000 p2pool (version 0.11.2-19-g27ae8fc)
2012-06-15 09:31:50.716000
2012-06-15 09:31:50.716000 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xx'...
2012-06-15 09:31:53.391000     ...success!
2012-06-15 09:31:53.392000     Current block hash: 842665768b48a6f558417d420f41904f973d3ad8e463284afde
2012-06-15 09:31:53.392000
2012-06-15 09:31:53.392000 Testing bitcoind P2P connection to '127.0.0.1:8333'...

EDIT: after restarting everything it seem to connect now.. will see how this new version goes.

[RandomQ]

Only been running the new build for 12 hours or so.

stale rate has jumped to 20%
efficiency has dropped to 86%
DOA % ~ 1-3% higher

maybe just some bad luck on my end or something.

Or p2pool showing better reporting of stats.
My local MH/s appears to be very precise now compared to jumping 100-300 MH/s .

my normal efficiency is around ~102-110.

[rav3n_pl]

Our block:184666
Relayed By    Donate@Home ?

[Schleicher]

Code:

2012-06-15 16:31:41.969000 GOT BLOCK FROM PEER! Passing to bitcoind! af9ce4f2 bitcoin: http://blockexplorer.com/block/0000000000000943c19cb9910ab539f29ce274329c1cfb86ad67efa6af9ce4f2

Sure, why not?