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

[kano]

I know a lot of us use SSH to manage remote nodes, there was serious SSH security flaw identified, there is an easy short term fix: http://undeadly.org/cgi?action=article&sid=20160114142733

As the flaw states, it's only a problem if you are connecting to something you don't control.

The authentication of the server host key prevents exploitation
   by a man-in-the-middle, so this information leak is restricted
   to connections to malicious or compromised servers.

Usually a good idea to point out something like that rather than cause panic.

[Tibi]

almost 1 week since we found a block ((

[notbatman]

almost 1 week since we found a block ((

Bitcoin Difficulty:   113,354,299,801

[jedimstr]

almost 1 week since we found a block ((

Bitcoin Difficulty:   113,354,299,801

And Hashrate hovering around 1.14PH. 

[notbatman]

almost 1 week since we found a block ((

Bitcoin Difficulty:   113,354,299,801

And Hashrate hovering around 1.14PH. 

...and what happened to Bitfuy's promise to spread the love?

[nicklello]

So....

How do we attract more hashrate to P2Pool ?

[Cassey]

You need a LOT more hashrate.  I'm using a 40PH (more or less) pool and on back-luck weeks its variance is barely tolerable.  I fear the only way this will happen is if several major pools die.

I know that mathematically, variance does not matter - in theory, but that theory does not take into account the changing difficulty, does it?

[notbatman]

So....

How do we attract more hashrate to P2Pool ?

[Tibi]

think we have to kill the dog boss.....

[-ck]

I know that mathematically, variance does not matter - in theory, but that theory does not take into account the changing difficulty, does it?

You are correct mathematically on the latter part and it's not just a hunch. If you have bad luck for a whole diff and the diff is rising, then you will not on average ever make up the difference after the diff rise. However the opposite is also true - if you have good luck during a period and diff is rising, then on average after the diff change you will remain ahead long term.

The practical side of this for those trying to understand it - if diff continues to rise, then short term luck has more long term effects on your overall returns the smaller the pool is.

[Cassey]

Thanks, that makes sense.  However... over the long term, luck should equalize out, since by definition its just statiscal noise.

[CartmanSPC]

When I attach a miner to the p2pool litecoin version, I get nothing but hash > target errors.

Things are set up according to instructions. Any idea what I am doing wrong?

bney,

This is a Bitcoin thread so discussions on Altcoins are not warmly welcomed. :/

That being said you may be able to fix your problem with Litecoin using the following patches:

https://github.com/CartmanSPC/p2pool/commit/742e97a3ddc4683b3a5bd3b0bc849de9ef8b10d1
https://github.com/CartmanSPC/p2pool/commit/614fb94eb3f9bb77a3a0991bed99fa903cdcf814

Good luck!

[p3yot33at3r]

Block!!   

[Cassey]

When I attach a miner to the p2pool litecoin version, I get nothing but hash > target errors.

Things are set up according to instructions. Any idea what I am doing wrong?

bney,

This is a Bitcoin thread so discussions on Altcoins are not warmly welcomed. :/

That being said you may be able to fix your problem with Litecoin using the following patches:

https://github.com/CartmanSPC/p2pool/commit/742e97a3ddc4683b3a5bd3b0bc849de9ef8b10d1
https://github.com/CartmanSPC/p2pool/commit/614fb94eb3f9bb77a3a0991bed99fa903cdcf814

Good luck!

And, of course, make sure your equipment can mine with Litecoins Scrypt algo instead of Bitcoins SHA256.  Few ASICs can do both.

[wariner]

When I attach a miner to the p2pool litecoin version, I get nothing but hash > target errors.

Things are set up according to instructions. Any idea what I am doing wrong?

bney,

This is a Bitcoin thread so discussions on Altcoins are not warmly welcomed. :/

That being said you may be able to fix your problem with Litecoin using the following patches:

https://github.com/CartmanSPC/p2pool/commit/742e97a3ddc4683b3a5bd3b0bc849de9ef8b10d1
https://github.com/CartmanSPC/p2pool/commit/614fb94eb3f9bb77a3a0991bed99fa903cdcf814

Good luck!

And, of course, make sure your equipment can mine with Litecoins Scrypt algo instead of Bitcoins SHA256.  Few ASICs can do both.

and be sure to add " --net litecoin " 

[notbatman]

So I got p2pool sandboxed and a new web browser that doesn't 'sploit while running boxed. Smooth sailing for a bit but just now the assholes have returned to spamming the mempool full of shit; lopped a 0 off my txfees in response. 

[Richy_T]

Has anyone else had any trouble with p2pool interfering with their bitcoind?

I run some software which queries the RPC interface periodically and it's been giving 500 read timeout errors. I bumped my rpc threads up to 100 and it helped but it was still doing it. I just killed p2pool and a lot of the read errors stopped but also the requests I was making were coming back a lot faster. Does p2pool hit RPC pretty hard?

[notbatman]

Has anyone else had any trouble with p2pool interfering with their bitcoind?

I run some software which queries the RPC interface periodically and it's been giving 500 read timeout errors. I bumped my rpc threads up to 100 and it helped but it was still doing it. I just killed p2pool and a lot of the read errors stopped but also the requests I was making were coming back a lot faster. Does p2pool hit RPC pretty hard?

Try sandboxing both p2pool and your web browser. Whatever other app that's online or interacting with bitcoind would also be a good idea. This is just a guess but I think "they" are exploiting a vulnerability in python to cause a memory leak in bitcoind via a ddos mirror attack via multiple entry vectors. Today "they" started screwing with spam tx's to trigger the memory leak now that I've closed off their entry points with sandboxing. Up your mintxfee to filter the spam, that's working for me so far.

[localhost]

So....

How do we attract more hashrate to P2Pool ?

https://i.imgur.com/vBIbAkZ.png

I think the reason so few people use it is because, years after the first release, it's still so complicated to set up.
I did configure Bitcoin Core to run that RPC server, here's bitcoin.conf:

Code:

server=1
rpcuser='me'
rpcpassword='youwish'

Then tried to run run_p2pool.exe, but could find no option to configure the rpcuser there. And of course it failed.

In the log I noticed:

Code:

Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username ''

So I went back and set rpcuser='' in bitcoin.conf
And I ran p2pool again this way:

Code:

run_p2pool.exe -a myrichwalletiwish youwish

And still it didn't work. So I went back to a normal pool, because I have other things to do today.........

[trendax]

So....

How do we attract more hashrate to P2Pool ?

https://i.imgur.com/vBIbAkZ.png

I think the reason so few people use it is because, years after the first release, it's still so complicated to set up.
I did configure Bitcoin Core to run that RPC server, here's bitcoin.conf:

Code:

server=1
rpcuser='me'
rpcpassword='youwish'

Then tried to run run_p2pool.exe, but could find no option to configure the rpcuser there. And of course it failed.

In the log I noticed:

Code:

Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username ''

So I went back and set rpcuser='' in bitcoin.conf
And I ran p2pool again this way:

Code:

run_p2pool.exe -a myrichwalletiwish youwish

And still it didn't work. So I went back to a normal pool, because I have other things to do today.........

run_p2pool.exe me youwish -a yourbitcoinaddress

EDIT: lack of concentration