A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux

[IYFTech]

Is there a definitive list anywhere of what coins can be merge mined together with the ports they use on p2pool?

I see so many conflicting posts about what ports to use it's not funny.... I recently added Huntercoin to my node, but there's a crash glitch with the daemon at present, & I've no idea what port to use with it.

Thanks.

Edit:

Or, to put it another way, would anybody like to share what ports they are using with IXC, I0C, DVC, GRP, HUC, NMC & any other coin they are merge mining?

Thanks again  

--merged http://nmcuser:jj@127.0.0.1:7332/ --merged http://ixcuser:jj@127.0.0.1:7342/ --merged http://dvcuser:jj@127.0.0.1:7362/ --merged http://i0cuser:jj@127.0.0.1:7382/

gotta add GRP
whats HUC

Thanks bitpop, a couple of those rpc ports are different to mine, as I feared. What about the actual ports - what are you using? For GRouPcoin I'm using rpc=51332 & port=51333 FYI. HUC is Huntercoin, it's also merge mined & becoming quite popular due to it's human mineable gameplay - very original.

Thanks again 

[1714021275]

1714021275

[1714021275]

1714021275

[1714021275]

1714021275

[1714021275]

1714021275

[1714021275]

1714021275

[1714021275]

1714021275

[bitpop]

Yes I lost track so I started using my own

btc
rpcport=8332
port=8333

nmc
rpcport=7332
port=7333

ixc
rpcport=7342
port=7343

dvc
rpcport=7362
port=7363

i0c
rpcport=7382
port=7383

[IYFTech]

Yes I lost track so I started using my own

btc
rpcport=8332
port=8333

nmc
rpcport=7332
port=7333

ixc
rpcport=7342
port=7343

dvc
rpcport=7362
port=7363

i0c
rpcport=7382
port=7383

Perfect! Thanks bitpop 

[bitpop]

GRP seems to be

rpcport=51332
port=51333

[IYFTech]

GRP seems to be

rpcport=51332
port=51333

Yeah, I got that one right....

[IYFTech]

Hi all, gave up trying to get any help on the p2pool thread - like getting blood out of a stone, so thought I'd try here instead 

I noticed this has started appearing when I start p2pool after doing some compiling on my node:

"/usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module twisted was already imported from /usr/lib/python2.7/dist-packages/twisted/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/autobahn-0.7.4-py2.7.egg is being added to sys.path"

It appears right at the start before p2pool does it's thing - but everything seems to be working OK with no errors. Have I accidentally added something I don't need - and should I get rid of it?

Thanks.

[hoquet]

Hi all, gave up trying to get any help on the p2pool thread - like getting blood out of a stone, so thought I'd try here instead 

I noticed this has started appearing when I start p2pool after doing some compiling on my node:

"/usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module twisted was already imported from /usr/lib/python2.7/dist-packages/twisted/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/autobahn-0.7.4-py2.7.egg is being added to sys.path"

It appears right at the start before p2pool does it's thing - but everything seems to be working OK with no errors. Have I accidentally added something I don't need - and should I get rid of it?

Thanks.

Is this the first time you have started p2pool? What are you using in your command line to start the pool? Have you run the setup in litecoin_scrypt?

[IYFTech]

Hi all, gave up trying to get any help on the p2pool thread - like getting blood out of a stone, so thought I'd try here instead 

I noticed this has started appearing when I start p2pool after doing some compiling on my node:

"/usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module twisted was already imported from /usr/lib/python2.7/dist-packages/twisted/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/autobahn-0.7.4-py2.7.egg is being added to sys.path"

It appears right at the start before p2pool does it's thing - but everything seems to be working OK with no errors. Have I accidentally added something I don't need - and should I get rid of it?

Thanks.

Is this the first time you have started p2pool? What are you using in your command line to start the pool? Have you run the setup in litecoin_scrypt?

Hi hoquet,

Thanks for answering. No, I've been using p2pool on & off for over one & a half years mining sha256.

[hoquet]

Hi all, gave up trying to get any help on the p2pool thread - like getting blood out of a stone, so thought I'd try here instead 

I noticed this has started appearing when I start p2pool after doing some compiling on my node:

"/usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module twisted was already imported from /usr/lib/python2.7/dist-packages/twisted/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/autobahn-0.7.4-py2.7.egg is being added to sys.path"

It appears right at the start before p2pool does it's thing - but everything seems to be working OK with no errors. Have I accidentally added something I don't need - and should I get rid of it?

Thanks.

Is this the first time you have started p2pool? What are you using in your command line to start the pool? Have you run the setup in litecoin_scrypt?

Hi hoquet,

Thanks for answering. No, I've been using p2pool on & off for over one & a half years mining sha256.

Wow, you are a seasoned veteran then. I've been running for just a couple of weeks now, but really starting to understand it more and more. I have not come across this error myself. Have you made any code mods to the p2pool software or running this vanilla? Is this the first time you are starting up this particular p2pool instance? Has it run before on this machine? Did the issues appear after making the changes to the networks.py files?

[roy7]

Odds are the setup script for twisted or autobahn has an error and it adds that library to the path even if it already exists. It's a warning you can ignore.

[hoquet]

If anyone could help,

I used both networks.py file from Rav's site. It has most of the coins that I need. I currently have the settings for litecoin, dogecoin, and worldcoin. I would like to run all 3, I tried to run commands to start up all 3. Dogecoin works fine:

Code:

screen -d -m -S dogep2pool ~/p2pool/run_p2pool.py --give-author 0 --net dogecoin --bitcoind-rpc-port 22555 dogecoinrpc rpcpassword=xxxxxxxxxxxxxxxx

Then when I try to run the same type of command to start litecoin:

Code:

screen -d -m -S litep2pool ~/p2pool/run_p2pool.py --give-author 0 --net litecoin --bitcoind-rpc-port 9334 litecoinrpc rpcpassword=xxxxxxxxxxxxxxxx

I get errors that keeps repeating:

Testing bitcoind RPC connection to 'http://127.0.0.1:9334/' with username 'litecoinrpc'...

Code:

2014-02-24 16:39:57.880662 > Error while checking Bitcoin connection:
2014-02-24 16:39:57.880713 > Traceback (most recent call last):
2014-02-24 16:39:57.880752 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 545, in _runCallbacks
2014-02-24 16:39:57.880793 >     current.result = callback(current.result, *args, **kw)
2014-02-24 16:39:57.880832 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1095, in gotResult
2014-02-24 16:39:57.880870 >     _inlineCallbacks(r, g, deferred)
2014-02-24 16:39:57.880906 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-02-24 16:39:57.880944 >     result = result.throwExceptionIntoGenerator(g)
2014-02-24 16:39:57.880983 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-02-24 16:39:57.881022 >     return g.throw(self.type, self.value, self.tb)
2014-02-24 16:39:57.881058 > --- <exception caught here> ---
2014-02-24 16:39:57.881092 >   File "/home/pooladmin/p2pool/p2pool/util/deferral.py", line 41, in f
2014-02-24 16:39:57.881129 >     result = yield func(*args, **kwargs)
2014-02-24 16:39:57.881164 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-02-24 16:39:57.881209 >     result = result.throwExceptionIntoGenerator(g)
2014-02-24 16:39:57.881246 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-02-24 16:39:57.881285 >     return g.throw(self.type, self.value, self.tb)
2014-02-24 16:39:57.881321 >   File "/home/pooladmin/p2pool/p2pool/bitcoin/helper.py", line 13, in check
2014-02-24 16:39:57.881359 >     if not (yield net.PARENT.RPC_CHECK(bitcoind)):
2014-02-24 16:39:57.881395 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-02-24 16:39:57.881435 >     result = result.throwExceptionIntoGenerator(g)
2014-02-24 16:39:57.881471 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-02-24 16:39:57.881510 >     return g.throw(self.type, self.value, self.tb)
2014-02-24 16:39:57.881546 >   File "/home/pooladmin/p2pool/p2pool/bitcoin/networks.py", line 67, in <lambda>
2014-02-24 16:39:57.881584 >     'litecoinaddress' in (yield bitcoind.rpc_help()) and
2014-02-24 16:39:57.881621 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1037, in _inlineCallbacks
2014-02-24 16:39:57.881930 >     result = result.throwExceptionIntoGenerator(g)
2014-02-24 16:39:57.881967 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 382, in throwExceptionIntoGenerator
2014-02-24 16:39:57.882070 >     return g.throw(self.type, self.value, self.tb)
2014-02-24 16:39:57.882108 >   File "/home/pooladmin/p2pool/p2pool/util/jsonrpc.py", line 126, in _http_do
2014-02-24 16:39:57.882146 >     raise e
2014-02-24 16:39:57.882181 > twisted.web.error.Error: 401 Authorization Required

Here is my litecoin.conf file:

Code:

server=1
daemon=1
rpcuser=litecoinrpc
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
rpcallowip=127.0.0.1
rpcallowip=192.168.0.165
rpcport=9334
port=9335
gen=0

Here is the p2pool/networks.py file entry for litecoin:
    

Code:

litecoin=math.Object(
        PARENT=networks.nets['litecoin'],
        SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=3, # blocks
        IDENTIFIER='e037d5b8c6923410'.decode('hex'),
        PREFIX='7208c1a53ef629b0'.decode('hex'),
        P2P_PORT=9338,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9327,
        BOOTSTRAP_ADDRS='forre.st vps.forre.st liteco.in 95.211.21.103 37.229.117.57 66.228.48.21 180.169.60.179 112.84.181.102 74.214.62.115 209.141.46.154 78.27.191.182 66.187.70.88 88.190.223.96 78.47.242.59 158.182.39.43 180.177.114.80 216.230.232.35 94.231.56.87 62.38.194.17 82.67.167.12 183.129.157.220 71.19.240.182 216.177.81.88 109.106.0.130 113.10.168.210 218.22.102.12 85.69.35.7:54396 201.52.162.167 95.66.173.110:8331 109.65.171.93 95.243.237.90 208.68.17.67 87.103.197.163 101.1.25.211 144.76.17.34 209.99.52.72 198.23.245.250 46.151.21.226 66.43.209.193 59.127.188.231 178.194.42.169 85.10.35.90 110.175.53.212 98.232.129.196 116.228.192.46 94.251.42.75 195.216.115.94 24.49.138.81 61.158.7.36 213.168.187.27 37.59.10.166 72.44.88.49 98.221.44.200 178.19.104.251 87.198.219.221 85.237.59.130:9310 218.16.251.86 151.236.11.119 94.23.215.27 60.190.203.228 176.31.208.222 46.163.105.201 198.84.186.74 199.175.50.102 188.142.102.15 202.191.108.46 125.65.108.19 15.185.107.232 108.161.131.248 188.116.33.39 78.142.148.62 69.42.217.130 213.110.14.23 185.10.51.18 74.71.113.207 77.89.41.253 69.171.153.219 58.210.42.10 174.107.165.198 50.53.105.6 116.213.73.50 83.150.90.211 210.28.136.11 86.58.41.122 70.63.34.88 78.155.217.76 68.193.128.182 198.199.73.40 193.6.148.18 188.177.188.189 83.109.6.82 204.10.105.113 64.91.214.180 46.4.74.44 98.234.11.149 71.189.207.226'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-ltc',
        VERSION_CHECK=lambda v: True,
        VERSION_WARNING=lambda v: 'Upgrade Litecoin to >=0.8.5.1!' if v < 80501 else None,

Here is the p2pool/bitcoin/networks.py file:
    

Code:

litecoin=math.Object(
        P2P_PREFIX='fbc0b6db'.decode('hex'),
        P2P_PORT=9333,
        ADDRESS_VERSION=48,
        RPC_PORT=9332,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'litecoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//840000,
        POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
        BLOCK_PERIOD=150, # s
        SYMBOL='LTC',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Litecoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Litecoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.litecoin'), 'litecoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/block/',
        ADDRESS_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/address/',
        TX_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/tx/',
        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
        DUMB_SCRYPT_DIFF=2**16,
        DUST_THRESHOLD=0.03e8,

Any help would be so greatly appreaciated! Please leave your BTC or LTC wallet address.

Quick Update

Stopped dogecoin and attempted to start litecoin. - same error
Tried to restart dogecoin - now it gives the same error. wow, it's like viral...

I have been trying to walk through the code to see where it fails, it is in the inital RPC connection that can't be created.

Thanks

[cr1776]

I think the key is here:
twisted.web.error.Error: 401 Authorization Required

I do not think that this is correct:
rpcpassword=xxxxxxxxxxxxxxxx

My understanding from here (https://en.bitcoin.it/wiki/P2Pool) is that the rpcpassword= is not used on the command line so you might need to make it:

Code:

--bitcoind-rpc-port 9334 litecoinrpc xxxxxxxxxxxxxxxx

Try that and see if it helps - that is how it looks for our setup.

:-)

[hoquet]

by removing both the username and password from the command line, p2pool looks for the .conf file for the user/password. This fixed my issue of my coin not running with Authorization issues.

I am able to run any single coin. So I started dogecoin and started mining again just fine.

Now I tried to start worldcoin. It seemed to get past the Authorization error, however, it gets stuck while starting up:

Code:

2014-02-26 09:31:48.533024 Testing bitcoind P2P connection to '127.0.0.1:11083'...
2014-02-26 09:31:53.533303     ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...
...

So either the coin daemon can't accept any more connections or p2pool's connections are maxed out.

I am going to restart things and provide some parameters around max connections and have a go at it again.

[smooth]

Maybe one day p2pool will allow the fee amount to be recorded in the share, like the donation amount is, so it can be paid exactly when each share is paid and all shares remain with the miner.

The issue with this would be dust. If you have a 1% fee on your node then your node hash rate would have to be such that 1% of that wouldn't create dust on every block.

[roy7]

The issue with this would be dust. If you have a 1% fee on your node then your node hash rate would have to be such that 1% of that wouldn't create dust on every block.

One thing to keep in mind though is that you'd be getting 1% of every share your node found. So if there are lots of shares in the share chain, you'd add up 1% of each of them and the pool receives that one single payment like any other miner in the payouts list. If the fee to the node operator is so small it's just useless dust he can't spend anyway, then he should either get more miners to use his node or drop the fee to 0.

[smooth]

One thing to keep in mind though is that you'd be getting 1% of every share your node found. So if there are lots of shares in the share chain, you'd add up 1% of each of them and the pool receives that one single payment like any other miner in the payouts list. If the fee to the node operator is so small it's just useless dust he can't spend anyway, then he should either get more miners to use his node or drop the fee to 0.

Looking at the public node list, most of the public nodes are well under 1 TH. (That shouldn't be a surprise given the total hash rate for p2pool as a whole.) If you have a 500 GH node and take 1% that means your fee hash rate is 5 GH, making your fee payments quite small. Maybe not technically dust, but small enough to be annoying. Opinions differ but personally I'd rather get at least a 1-share fee occasionally.

[jedimstr]

So I've had merged mining setup on my local node for the last month or so with IXCoin, Devcoin, and Namecoin, alongside BTC, and I do see the "Got new merged mining work!" message occasionally (all three during startup of the node)... previously was only set to mine Namecoin and BTC going back over 3 months merged. My local hashrate is about 700GH/s to 1200GH/s depending who joined my node and my personal miners.  

I have received a whole lot of nothing in my merged mining wallets.  I know merged mining is more like Solo mining with P2Pool, but with this somewhat middling hashpower I would have expected to have gotten something within this timeframe.  So do I have something setup wrong or is the probability really that bad with around a 1TH of power?  Even Namecoin has only the few bits I got from failover to BTCGuild and nothing from my merged p2pool node even after being active for over 3 months.

[roy7]

I have received a whole lot of nothing in my merged mining wallets.  I know merged mining is more like Solo mining with P2Pool, but with this somewhat middling hashpower I would have expected to have gotten something within this timeframe.  So do I have something setup wrong or is the probability really that bad with around a 1TH of power?  Even Namecoin has only the few bits I got from failover to BTCGuild and nothing from my merged p2pool node even after being active for over 3 months.

When I did the math the other day, I think Namecoin merge mining with my 180GH miner on my Un node is about 2 years average time to find a namecoin block. I'd need to be more around 10 TH to get blocks on a regular enough basis to consider that a legitimate source of income to pay for the pool overhead.

It'd be nice if there was a namecoin p2pool network, and p2pool could merge mine off of that extra p2pool network somehow.

[PatMan]

With merge mining BTC you are pretty much solo mining the other coins - it's pot luck. Unless you have insane hashing power like a large pool you're relying on luck, basically. Having said that, I got 3 I0C yesterday - first payment in over a month with that coin!! 

[Tegija]

I have received a whole lot of nothing in my merged mining wallets.  I know merged mining is more like Solo mining with P2Pool, but with this somewhat middling hashpower I would have expected to have gotten something within this timeframe.  So do I have something setup wrong or is the probability really that bad with around a 1TH of power?  Even Namecoin has only the few bits I got from failover to BTCGuild and nothing from my merged p2pool node even after being active for over 3 months.

When I did the math the other day, I think Namecoin merge mining with my 180GH miner on my Un node is about 2 years average time to find a namecoin block. I'd need to be more around 10 TH to get blocks on a regular enough basis to consider that a legitimate source of income to pay for the pool overhead.

It'd be nice if there was a namecoin p2pool network, and p2pool could merge mine off of that extra p2pool network somehow.

With merge mining BTC you are pretty much solo mining the other coins - it's pot luck. Unless you have insane hashing power like a large pool you're relying on luck, basically. Having said that, I got 3 I0C yesterday - first payment in over a month with that coin!! 

merged mining in p2pool node is wast of resources. latency will go higher and memory usage is very high too. my experience says that it is contra productive to mine them.
when i tested to mine merged coins in my node, efficiency of nod was much lower. most of nodes make merged mining to cover costs, but usually it is not worth it. since i don't have merced coins in my node it functions perfect and payouts are much better than with merged mining.
better set 1% of fee on your public node to cover your costs instead of mining hidden merged coins. if somebody is mining in your node without merged mining, he gets better payouts with 1% of fee than 0% fee and merged mining.