Does it work well with a pruned blockchain?
No.
you can't mine with pruning activate.
https://bitcointalksearch.org/topic/m.12155718
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 105. (Read 2591920 times)
January 22, 2016, 09:26:15 AM
No.
you can't mine with pruning activate.
https://bitcointalksearch.org/topic/m.12155718
January 21, 2016, 07:09:19 PM
So I'm looking at my p2pool window and see that my hash rate has suddenly dropped by 50% but no messages about losing contact with bitcoind. Then I look at my geth window and it starts complaining about having 0 peers. A few minutes pass and geth stops complaining and my p2pool hash rate returns to normal.
It would appear that now that I've plugged the python exploit causing the bitcoind memory leak with sandboxing and put a lid on the spam attack by boosting the txfees they've changed gears yet again and have found a new DoS attack to disconnect my connected peers. Looking at my p2pool graph I can see a 75% drop on peers for the last 5 hours.
It would appear that now that I've plugged the python exploit causing the bitcoind memory leak with sandboxing and put a lid on the spam attack by boosting the txfees they've changed gears yet again and have found a new DoS attack to disconnect my connected peers. Looking at my p2pool graph I can see a 75% drop on peers for the last 5 hours.
January 21, 2016, 05:33:46 AM
So it sounds like I need to be running a separate bitcoind for p2pool. Does it work well with a pruned blockchain?
Never tested, but should not be an issue, P2Pool only cares about the chain tip...
I had tried long ago...but I get the message from p2pool that were missing xx blocks (maybe I had too much "pruned")
January 20, 2016, 12:53:40 PM
So it sounds like I need to be running a separate bitcoind for p2pool. Does it work well with a pruned blockchain?
Never tested, but should not be an issue, P2Pool only cares about the chain tip...
January 20, 2016, 11:59:19 AM
So it sounds like I need to be running a separate bitcoind for p2pool. Does it work well with a pruned blockchain?
January 20, 2016, 09:58:10 AM
I think the thing keeping people away from p2pool is the variance. It's kind-of a self fulfilling thing though since it would be better with more hashrate.
I don't think there's a good way of doing much about it without making p2pool look more like a regular pool. Possibly more publicity about being able to mine on p2pools that are already set up...
It is what it is though. Still my favorite pool.
I don't think there's a good way of doing much about it without making p2pool look more like a regular pool. Possibly more publicity about being able to mine on p2pools that are already set up...
It is what it is though. Still my favorite pool.
January 20, 2016, 09:52:04 AM
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.confAnd 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.........It's not really helpful but it just works for me. It grabs the rpc credentials from bitcoin.conf. Are you running it as the same user? (Wait, I see you're using Windows so you probably are)
January 20, 2016, 09:49:51 AM
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.........The format is:
Code:
run_p2pool.exe -a BTC_ADDRESS (other options) RPC_USER RPC_PASS
January 20, 2016, 09:47:28 AM
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?
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?
I have not had trouble per say, but its important to recognize that GetBlockTemplate is an expensive call overhead wise, and its made often by p2pool. Keeping your eye on GBT latency in the graphs is a good way to gauge how its effecting your node.
January 20, 2016, 07:59:58 AM
Interesting quote on Bitcoinclassic github page:
If only........
Quote
Sure, this shouldn't be in the first hardfork. But something like this needs to happen. I thought the "enforced p2pool" concept was better. IE: no such thing as a pool that doesn't use p2pool. therefore there's no need to join a centralized pool, because p2pool is going to work better. which means pools lose power and machine owners get it back.
If only........
January 20, 2016, 05:03:30 AM
Do you think a regularly-updated VM image would help promote pickup ?
I'm thinking something pre-configured (with the exception of the bitcoin wallet and payment address which will be created once the VM starts)
I'm thinking something pre-configured (with the exception of the bitcoin wallet and payment address which will be created once the VM starts)
I don't think it's necessary to go this far. Some more details in the step-by-step instructions, so that they work without assuming the user's setup is 100% default would be enough.
For instance, the instructions on http://p2pool.in/ might work for a user with a default setup (data folder for Bitcoin Core not modified) and who doesn't care about not knowing where the mined BTCs will arrive, but it's not enough for a user who moved around their data folder or wants to specify at the pool level the address where to receive BTCs. Also, it's not the case for me but maybe instructions to use a custom port (+/-IP) for Bitcoin RPC would be useful too.
January 20, 2016, 04:47:28 AM
I think the reason so few people use it is because, years after the first release, it's still so complicated to set up.
Do you think a regularly-updated VM image would help promote pickup ?
I'm thinking something pre-configured (with the exception of the bitcoin wallet and payment address which will be created once the VM starts)
January 20, 2016, 04:27:24 AM
run_p2pool.exe me youwish -a yourbitcoinaddress
EDIT: lack of concentration
Thanks, the logs looked better this way (tries to connect with the proper rpcuser, at least)... but still failed.EDIT: lack of concentration
I ended up running
Code:
run_p2pool.exe --bitcoind-config-path "C:\thisway\to\bitcoin.conf" -a myrichwalletiwish
which finally worked January 20, 2016, 03:58:29 AM
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:
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:
So I went back and set rpcuser='' in bitcoin.conf
And I ran p2pool again this way:
And still it didn't work. So I went back to a normal pool, because I have other things to do today.........
I did configure Bitcoin Core to run that RPC server, here's bitcoin.conf:
Code:
server=1
rpcuser='me'
rpcpassword='youwish'
In the log I noticed:
Code:
Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username ''
And I ran p2pool again this way:
Code:
run_p2pool.exe -a myrichwalletiwish youwish
run_p2pool.exe me youwish -a yourbitcoinaddress
EDIT: lack of concentration
January 20, 2016, 03:52:08 AM
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:
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:
So I went back and set rpcuser='' in bitcoin.conf
And I ran p2pool again this way:
And still it didn't work. So I went back to a normal pool, because I have other things to do today.........
I did configure Bitcoin Core to run that RPC server, here's bitcoin.conf:
Code:
server=1
rpcuser='me'
rpcpassword='youwish'
In the log I noticed:
Code:
Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username ''
And I ran p2pool again this way:
Code:
run_p2pool.exe -a myrichwalletiwish youwish
January 20, 2016, 02:49:39 AM
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?
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.
January 20, 2016, 12:51:44 AM
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?
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?
January 19, 2016, 06:31:45 PM
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. 
January 19, 2016, 01:24:58 AM
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?
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 "
January 18, 2016, 08:23:21 PM
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?
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.
Jump to: