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

[notbatman]

getblocktemplate latency now @ ~0.5s

[1715251641]

1715251641

[1715251641]

1715251641

[Meuh6879]

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.

[notbatman]

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.

[notbatman]

Latency remaining well below 1s and efficiency steady at 120%.

[notbatman]

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. 

[notbatman]

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.

[lightfoot]

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.

[notbatman]

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.

[Meuh6879]

Well, it's nothing more than Internet ... an IP and a connexion.  

http://www.zerohedge.com/news/2015-12-31/how-isis-broadcasts-its-message-world-satellite-dishes-bought-turkey

[notbatman]

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.

[trendax]

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.

[kano]

Centralisation ... yeah that's gotta be the best solution

[wariner]

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.

[trendax]

Centralisation ... yeah that's gotta be the best solution

@kano

A workable solution yes :p centralized nodes help small and mid market miners which typically avoid p2pool reducing it's network health.

I welcome any miner who use p2pool with a rental proxy like Nicehash, Betarigs or MRR as a backup pool to join us instead.

When buyers and sellers from these proxy pools find p2pool has an option like us, miners will switch to benefit the bitcoin network and further support p2pool.

[aladinsain]

Centralisation ... yeah that's gotta be the best solution

@kano

A workable solution yes :p centralized nodes help small and mid market miners which typically avoid p2pool reducing it's network health.

I welcome any miner who use p2pool with a rental proxy like Nicehash, Betarigs or MRR as a backup pool to join us instead.

When buyers and sellers from these proxy pools find p2pool has an option like us, miners will switch to benefit the bitcoin network and further support p2pool.

How true i also welcome any miner to try p2pools for a week to see the results even if they only put 1 or all there miners on it


if you are looking for nodes to join this cool way of mining keeping mining for the miners look at the links below

http://poolnode.info/ (look for the node that is close to you so you have the least lagg )

http://beam.to/dbp2pool (my friends p2pool node )

[Alfi1966]

Pfff, time for a bit of luck. P2Pool could do with some more hashing power.

[TTravis]

Pfff, time for a bit of luck. P2Pool could do with some more hashing power.

We got a block like two minutes after you left the above comment.  Whatever you did worked.  Keep em coming.

[notbatman]

I've finally got my node running stable, here's the settings I've got.

environment variable:

setx MALLOC_ARENA_MAX 1


bitcoin.conf:

maxconnections=40
rpcthreads=100
blockmaxsize=640000
minrelaytxfee=0.00005
mintxfee=0.00005
limitfreerelay=5

edit:

Looks like I've only extended the period before my node crashes and burns.  

edit2:

I'm compiling bitcoin from the github source, maybe this might work...

edit3:

*yawn* I guess I'll come back some time in 2017 when this has completed...

edit4:

This boost library is massive...

[wariner]

I've finally got my node running stable, here's the settings I've got.

environment variable:

setx MALLOC_ARENA_MAX 1


bitcoin.conf:

maxconnections=40
rpcthreads=100
blockmaxsize=640000
minrelaytxfee=0.00005
mintxfee=0.00005
limitfreerelay=5

edit:

Looks like I've only extended the period before my node crashes and burns.  

edit2:

I'm compiling bitcoin from the github source, maybe this might work...

edit3:

*yawn* I guess I'll come back some time in 2017 when this has completed...

edit4:

This boost library is massive...

try this:
maxconnections=12
minrelaytxfee=0.0005
blockmaxsize=250000
(I know it is not good...but it is only for waiting v 0.12)

"monit" could help you to restart bitcoind if not respond  

[notbatman]

I've finally got my node running stable, here's the settings I've got.

environment variable:

setx MALLOC_ARENA_MAX 1


bitcoin.conf:

maxconnections=40
rpcthreads=100
blockmaxsize=640000
minrelaytxfee=0.00005
mintxfee=0.00005
limitfreerelay=5

edit:

Looks like I've only extended the period before my node crashes and burns.  

edit2:

I'm compiling bitcoin from the github source, maybe this might work...

edit3:

*yawn* I guess I'll come back some time in 2017 when this has completed...

edit4:

This boost library is massive...

try this:
maxconnections=12
minrelaytxfee=0.0005
blockmaxsize=250000

"monit" could help you to restart bitcoind if not respond  

A bit of a cheesy solution IMO, besides when I'm done I'll have all the tools I need to create Batcoin.

Looking at the github readme, apparently nobody has compiled core with windows yet. It just has cross-compiler instructions, I might actually be able to make some sort of contribution and a binary that doesn't leak memory.

edit:

uhg, getting the boost lib installed under msys was an exercise in futility... they said it wouldn't work under msys and sure enough it didn't LOL.

I'm testing out the 32-bit bitcoind binary from bitcoin.org, maybe it works without leaks...

edit:

The 32-bit windows bitcoind leaks even worse.