Author

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

legendary
Activity: 1257
Merit: 1004
pool.sexy
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.

Probable it's a bitcoin core problem of memory usage not DoS (the problem is mempool flooding), i have same problems on my 4 nodes.

This should help you https://gist.github.com/laanwj/efe29c7661ce9b6620a7

With bitcoin core v 0.12 should solve.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Centralisation ... yeah that's gotta be the best solution Tongue
full member
Activity: 124
Merit: 100
does it mean that the best ever would be p2pool was mining to just one address and then as coins mature it would be redistributed? is not this what nasty is doing?

That is our vision (credit to nonnakip for the work he's done on it), only we also distribute based on hashrate and not accepted p2pool shares to be fair to the little guys.  I think it is a much better solution than to run a centralized pool out of the gate.  I would love to see more p2pool sub-pools pop up with their own unique features, the way NastyPool offers our unique payout method and mining credits.  It sounds like -ck is working to help make his proxy more stable for this use which may be a huge step forward in bringing more users to the p2pool network.

+1

@OgNasty

Sub-pools like NastyPool and Cloudminer.com play an important part in the expansion of the p2pool network. Known scaling issues of p2pool causing high variance for smaller miners are addressed very well with alternate payout methods. Cloudminer.com distributes rewards based on CPPSRB. We also offer features to BUY and SELL hashes.

legendary
Activity: 2212
Merit: 1038
Well I'll have to say that adding rpcthreads=100 to bitcoin.conf has really helped with my issues weather it's windowz dozing, being short on ram, a memory leak or most likely a DoS mirror attack, until bitcoind finally crash & burns my orphan rate stays at 0, DOA at 1% and GBT latency staying real low.

I highly recommend this setting.
legendary
Activity: 1512
Merit: 1012
legendary
Activity: 2212
Merit: 1038
Damn that sucks. My latency on my node here is around 2s with an interesting spike to 20s at about 1800 GMT. It slowly creeped up from 1s to 2s.

I think honestly the solution is to run your bitcoind behind a firewall and allow your p2pool node to talk to that. Then the asshats can't fuck with you. But that means you're no longer running a public node, so get another 2tb disk and run a second node externally as a service to the bitcoin community.



I could live as a hermit in the most isolated and desolate region of the Sahara desert and they would still come and piss in my sandbox.
legendary
Activity: 3164
Merit: 2258
I fix broken miners. And make holes in teeth :-)
Damn that sucks. My latency on my node here is around 2s with an interesting spike to 20s at about 1800 GMT. It slowly creeped up from 1s to 2s.

I think honestly the solution is to run your bitcoind behind a firewall and allow your p2pool node to talk to that. Then the asshats can't fuck with you. But that means you're no longer running a public node, so get another 2tb disk and run a second node externally as a service to the bitcoin community.

legendary
Activity: 2212
Merit: 1038
Wake up and check my node and it's fucked... "lost contact with bitcoind" on and off for hours right after I nodd off. I'm guessing it's some kind of reflection attack they're performing on me. The symptoms are a lot like a memory leak.
legendary
Activity: 2212
Merit: 1038
Been hit with attacks 3 times in the last hour, they last for about 90 seconds. Maintaining my GBT latency below 1s and efficiency @ 120%.

Maybe they'll go back to dumping loads of money on the network in another spam attack.  Cheesy
legendary
Activity: 2212
Merit: 1038
Latency remaining well below 1s and efficiency steady at 120%.
legendary
Activity: 2212
Merit: 1038
since 0.11.2 , the bitcoind freeze is resolve in my side ... and the debug.log of bitcoin core is always a plenty of filtered "dust" and "already spend" and "free rate limiter" errors.



You clearly don't have the same issue with "them" as I do.
legendary
Activity: 1512
Merit: 1012
since 0.11.2 , the bitcoind freeze is resolve in my side ... and the debug.log of bitcoin core is always a plenty of filtered "dust" and "already spend" and "free rate limiter" errors.

legendary
Activity: 2212
Merit: 1038
getblocktemplate latency now @ ~0.5s
legendary
Activity: 2212
Merit: 1038
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.

Interesting fix, how's getblocktemplate latency before/after?

From 4.0s to 2.0s, this setting is working like a charm so-far...

That's a great result, thanks for sharing!

It's too soon to come to any conclusions here, gotta wait and see what happens over the next 12h or so.
legendary
Activity: 1258
Merit: 1027
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.

Interesting fix, how's getblocktemplate latency before/after?

From 4.0s to 2.0s, this setting is working like a charm so-far...

That's a great result, thanks for sharing!
legendary
Activity: 2212
Merit: 1038
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.

Interesting fix, how's getblocktemplate latency before/after?

From 4.0s to 2.0s, this setting is working like a charm so-far...
legendary
Activity: 1258
Merit: 1027
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.

Interesting fix, how's getblocktemplate latency before/after?
legendary
Activity: 2212
Merit: 1038
I've added rpcthreads=100 to my bitcoin.conf in an attempt to fight the latest DoS strategy against my node, so-far-so-good. If you're getting constant "lost contact with bitcoind" messages this might help.
newbie
Activity: 21
Merit: 0
well a bit of advert would go a long way
just posted a thing on twitter maybe you could do the same do boost just to get us to the moon
because this concept is way better then what i have seen so far

How True

Start the New Year off with a Block
Then join us now at p2pool where every miner is the boss google for your nearest p2pool
#bitcoin
newbie
Activity: 21
Merit: 0
How True

Start the New Year off with a Block
Then join us now at p2pool where every miner is the boss google for your nearest p2pool
#bitcoin
Jump to: