Author

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

hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....

Is your bitcoind running? If it is, you have maxed out on your bitcoind connection limit - try restarting your bitcoind.......

yes,, i was restarting bitcoind and still problem like that sir..

Is your bitcoind running on the same machine as your p2pool client? Also, have you port forwarded it's ports?

Yes ..my bitcoind and p2pool client on same machine ..how to forwarding port sir...?

What OS are you using? Please post your bitcoin .conf file.
full member
Activity: 193
Merit: 100

Is your bitcoind running? If it is, you have maxed out on your bitcoind connection limit - try restarting your bitcoind.......

yes,, i was restarting bitcoind and still problem like that sir..

Is your bitcoind running on the same machine as your p2pool client? Also, have you port forwarded it's ports?

Yes ..my bitcoind and p2pool client on same machine ..how to forwarding port sir...?
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Who's feeling brave today?  Wink

https://github.com/forrestv/p2pool/pull/243

Not me......not today  Cheesy
So, when does it decide when to use a different address?

If you have multiple addresses per block, that will of course increase the size of the p2pool coinbase txn.
If many p2pool miners are submitting shares with multiple addresses per block, then it will increasing the size of the coinbase txn dramatically and also decrease the size of your payouts - not total payout, but divide up your payout to multiple addresses and result in higher average txn size (i.e. higher default txn fees) when you use the payouts.

i.e. does it switch each p2pool block change (which of course p2pool doesn't see all the p2pool blocks) or does is switch based on some other requirement?

It uses a user defined time frame for address cycling.

I would like to think it preserves shares across the address change, so only the newest address is paid out, but I cant quite wrap my head around how you would do that.

Here are the changes if you feel like taking a look:

https://github.com/forrestv/p2pool/pull/230/files

You can't change in p2pool the address a share pays out to.
That would make p2pool unusable due to having no security to stop people from stealing other's payouts.

Yes I looked at the code the other day, but it's written in python which is one of the few languages I completely avoid for a good reason Smiley

So I guess from your comment, if someone chooses the address change close to a block they will probably have divided payments on average every 2nd block.
It would make sense to default to only have it change on a block/payout change boundary.

Cycling, not on a block boundary, wouldn't make it all that difficult to associate address pairs, then over a period of time, if the address list was not unlimited, that association would spread between address pairs and so on making it far from impossible to circumvent identifying the associations.

All good questions......it would be nice if the author of the merge, midnightmagic, would post some more detailed information about what it is & how it works - as there is quite a bit of confusion about it.

Unless forrestv fancies making a long overdue post of course....... Huh
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....

Is your bitcoind running? If it is, you have maxed out on your bitcoind connection limit - try restarting your bitcoind.......

yes,, i was restarting bitcoind and still problem like that sir..

Is your bitcoind running on the same machine as your p2pool client? Also, have you port forwarded it's ports?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Who's feeling brave today?  Wink

https://github.com/forrestv/p2pool/pull/243

Not me......not today  Cheesy
So, when does it decide when to use a different address?

If you have multiple addresses per block, that will of course increase the size of the p2pool coinbase txn.
If many p2pool miners are submitting shares with multiple addresses per block, then it will increasing the size of the coinbase txn dramatically and also decrease the size of your payouts - not total payout, but divide up your payout to multiple addresses and result in higher average txn size (i.e. higher default txn fees) when you use the payouts.

i.e. does it switch each p2pool block change (which of course p2pool doesn't see all the p2pool blocks) or does is switch based on some other requirement?

It uses a user defined time frame for address cycling.

I would like to think it preserves shares across the address change, so only the newest address is paid out, but I cant quite wrap my head around how you would do that.

Here are the changes if you feel like taking a look:

https://github.com/forrestv/p2pool/pull/230/files

You can't change in p2pool the address a share pays out to.
That would make p2pool unusable due to having no security to stop people from stealing other's payouts.

Yes I looked at the code the other day, but it's written in python which is one of the few languages I completely avoid for a good reason Smiley

So I guess from your comment, if someone chooses the address change close to a block they will probably have divided payments on average every 2nd block.
It would make sense to default to only have it change on a block/payout change boundary.

Cycling, not on a block boundary, wouldn't make it all that difficult to associate address pairs, then over a period of time, if the address list was not unlimited, that association would spread between address pairs and so on making it far from impossible to circumvent identifying the associations.
full member
Activity: 193
Merit: 100

Is your bitcoind running? If it is, you have maxed out on your bitcoind connection limit - try restarting your bitcoind.......

yes,, i was restarting bitcoind and still problem like that sir..
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
hi..
this my first time setup p2pool to my vps [Ubuntu 14.04]

i'm using method from this thread https://bitcointalksearch.org/topic/how-to-run-your-own-p2pool-in-ubuntu-1404-lts-with-merged-mining-651819 , when i start p2pool my screen stuck from this process

anybody can give me a solution.

thanks before..

Is your bitcoind running? If it is, you have maxed out on your bitcoind connection limit - try restarting your bitcoind.......
full member
Activity: 193
Merit: 100
hi..
this my first time setup p2pool to my vps [Ubuntu 14.04]

i'm using method from this thread https://bitcointalksearch.org/topic/how-to-run-your-own-p2pool-in-ubuntu-1404-lts-with-merged-mining-651819 , when i start p2pool my screen stuck from this process

anybody can give me a solution.

thanks before..
legendary
Activity: 1258
Merit: 1027
Who's feeling brave today?  Wink

https://github.com/forrestv/p2pool/pull/243

Not me......not today  Cheesy
So, when does it decide when to use a different address?

If you have multiple addresses per block, that will of course increase the size of the p2pool coinbase txn.
If many p2pool miners are submitting shares with multiple addresses per block, then it will increasing the size of the coinbase txn dramatically and also decrease the size of your payouts - not total payout, but divide up your payout to multiple addresses and result in higher average txn size (i.e. higher default txn fees) when you use the payouts.

i.e. does it switch each p2pool block change (which of course p2pool doesn't see all the p2pool blocks) or does is switch based on some other requirement?

It uses a user defined time frame for address cycling.

I would like to think it preserves shares across the address change, so only the newest address is paid out, but I cant quite wrap my head around how you would do that.

Here are the changes if you feel like taking a look:

https://github.com/forrestv/p2pool/pull/230/files
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Who's feeling brave today?  Wink

https://github.com/forrestv/p2pool/pull/243

Not me......not today  Cheesy
So, when does it decide when to use a different address?

If you have multiple addresses per block, that will of course increase the size of the p2pool coinbase txn.
If many p2pool miners are submitting shares with multiple addresses per block, then it will increasing the size of the coinbase txn dramatically and also decrease the size of your payouts - not total payout, but divide up your payout to multiple addresses and result in higher average txn size (i.e. higher default txn fees) when you use the payouts.

i.e. does it switch each p2pool block change (which of course p2pool doesn't see all the p2pool blocks) or does is switch based on some other requirement?
full member
Activity: 238
Merit: 100
Wow. I'm merge mining, so doubt I'll be able to use it then - might have a tinker later. What about CPU usage - any noticeable difference?

load 0.2 just now but previous was similar, so if any change than it is not worse for sure
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Wow. I'm merge mining, so doubt I'll be able to use it then - might have a tinker later. What about CPU usage - any noticeable difference?
full member
Activity: 238
Merit: 100
....(memory usage went up too from 500MB+ to 1500MB+)...

Seriously!? 3 x more memory?

yes! Smiley this is what I noticed the first. But if better efficiency and there is enough memory... why not. Maybe I will try later compile pypy from sources if possible, this time I used the easiest way, precompiled binary.
I was curious about if it works and it works, so if anybody interested, give it a try. But I am running backup p2pool node beside, so if You do not want to loose hashtime do the same.
It does not seem we will have another then python version so why not to try something potentially faster.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
....(memory usage went up too from 500MB+ to 1500MB+)...

Seriously!? 3 x more memory?
full member
Activity: 238
Merit: 100
small pypy howto

... download pypy binary, I choosed 64 bit version to my ubuntu 14.04 LTS
wget https://bitbucket.org/pypy/pypy/downloads/pypy-2.4.0-linux64.tar.bz2
... untar it
tar xvf pypy-2.4.0-linux64.tar.bz2
... create symbolic link
sudo ln -sf /where_untared/pypy-2.4.0-linux64/bin/pypy /usr/bin/pypy
... download pip manager
wget https://bootstrap.pypa.io/get-pip.py
... install pip manager
pypy get-pip.py
... install twisted
pip install twisted
... done

use pypy instead python

optional

... download latest forrestv p2pool version
git clone https://github.com/forrestv/p2pool.git
... run it
... make coffee

I try just now with latest git p2pool version 13.4-62-g077b2c1, seems well

Have you noticed any improvement using pypy? I've often thought about trying it, as it's claimed to be much faster.

I run it too short time to say definitely. But for the first view it seems be better. Efficiency went up (memory usage went up too from 500MB+ to 1500MB+), lower DOA. I have also installed latest bitcoind 0.9.4 (from git)... getblock template latencies seem went down. Previous average was 241ms, will see where it will move.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
small pypy howto

... download pypy binary, I choosed 64 bit version to my ubuntu 14.04 LTS
wget https://bitbucket.org/pypy/pypy/downloads/pypy-2.4.0-linux64.tar.bz2
... untar it
tar xvf pypy-2.4.0-linux64.tar.bz2
... create symbolic link
sudo ln -sf /where_untared/pypy-2.4.0-linux64/bin/pypy /usr/bin/pypy
... download pip manager
wget https://bootstrap.pypa.io/get-pip.py
... install pip manager
pypy get-pip.py
... install twisted
pip install twisted
... done

use pypy instead python

optional

... download latest forrestv p2pool version
git clone https://github.com/forrestv/p2pool.git
... run it
... make coffee

I try just now with latest git p2pool version 13.4-62-g077b2c1, seems well

Have you noticed any improvement using pypy? I've often thought about trying it, as it's claimed to be much faster.
full member
Activity: 238
Merit: 100
small pypy howto

... download pypy binary, I choosed 64 bit version to my ubuntu 14.04 LTS
wget https://bitbucket.org/pypy/pypy/downloads/pypy-2.4.0-linux64.tar.bz2
... untar it
tar xvf pypy-2.4.0-linux64.tar.bz2
... create symbolic link
sudo ln -sf /where_untared/pypy-2.4.0-linux64/bin/pypy /usr/bin/pypy
... download pip manager
wget https://bootstrap.pypa.io/get-pip.py
... install pip manager
pypy get-pip.py
... install twisted
pip install twisted
... done

use pypy instead python

optional

... download latest forrestv p2pool version
git clone https://github.com/forrestv/p2pool.git
... run it
... make coffee

I try just now with latest git p2pool version 13.4-62-g077b2c1, seems well
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Who's feeling brave today?  Wink

https://github.com/forrestv/p2pool/pull/243

Not me......not today  Cheesy
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool

While I understand the concept of rotating addresses, I don't understand how it's useful here.  Let's say that this was properly implemented in p2pool.  Who does it benefit?  As a miner, I still have to connect to a node using a BTC address.  I can't change that address constantly, or I'd always be ramping up shares on the chain for payout, which is exactly the opposite of what I want in a PPLNS pool.

What am I missing?

The benefit is specifically for the node owner using the bitcoind wallet on the node for mining income.

By using this, rather then setting an address with the miner you can simply use a name like AntS3 or SP20, the hash power will go to the node default address, which will now be cycled automatically increasing privacy and security.

To be honest the security benefits are a trade off, I would still feel better about not keeping any private keys on the node itself, but if privacy is a big concern for you this is probably a good trade off.
I get the concept behind it, and you cited precisely the example I was thinking about in my head.  However, this example still fails to benefit the node owner because the mining address is constantly cycling, which still means the node owner's address is ramping up on shares.  Sure, I suppose at the end of the day it would add up to the same thing - you'd just get a whole bunch of per share payouts to your node's cycling addresses instead of a larger payout to a single address.  However, that increases your transaction fees for spending those coins in the future because there'd have to be far more inputs.

Like I wrote, I just don't see how this could possibly benefit anyone except for the most paranoid tin-hat wearing folks running their own nodes.  For example, I run my own node locally, as well as a VPS-hosted node for backup when I travel.  I also fall back on your node in case neither of mine is available.  On my own nodes, sure I could put in something like a name of "S3_1" or "SP20" for each of my miners; however, configuration for your node forces me back into using a proper BTC address (which does not cycle)... unless of course I wish to donate my hashing power to you Smiley
legendary
Activity: 1258
Merit: 1027

While I understand the concept of rotating addresses, I don't understand how it's useful here.  Let's say that this was properly implemented in p2pool.  Who does it benefit?  As a miner, I still have to connect to a node using a BTC address.  I can't change that address constantly, or I'd always be ramping up shares on the chain for payout, which is exactly the opposite of what I want in a PPLNS pool.

What am I missing?

The benefit is specifically for the node owner using the bitcoind wallet on the node for mining income.

By using this, rather then setting an address with the miner you can simply use a name like AntS3 or SP20, the hash power will go to the node default address, which will now be cycled automatically increasing privacy and security.

To be honest the security benefits are a trade off, I would still feel better about not keeping any private keys on the node itself, but if privacy is a big concern for you this is probably a good trade off.
Jump to: