Search content
Sort by
Showing 20 of 25 results by hoquet
I've had many megashashes to help mine the coin since inception, but was looking for networks.py file for P2pool.
I guess it is not the coin makers problem, but a pool operator problem. I've got 160 other coins I can mine. Peace out!
I guess it is not the coin makers problem, but a pool operator problem. I've got 160 other coins I can mine. Peace out!
My p2pool performance versus publicly hosted large MPOS external site
I have been trying to size up my environment that I built out another pool just to try to size up if mine is performing as it should be. Here are the results of mining the same coin.
I have 2 sets of mining hardware, one at work (~6.50mhs), the other at home (~1.95mhs). I also switched them vice versa as a comparison. The p2pool is running in a VM at work. (Don't ask how or why about work...)
The MPOS pool is a public pool that I have about a ~35.0 ms latency at stratum-us.xxxxxxxxxxxxxx.com. I am not trying to bash the other site or pool, so I am leaving their name out. But I will say that they are a huge player. So naturally, I'm a bit surprised.
Not bad latency, from home to work I get about ~25.0 ms. The dyn diff on my pool is about 32. The diff of shares on mpos pool, cgminer shows at 512. So my p2pool is more chatty and network latency would come into play more if both share difficulty were the same, but my pool is sending 10x more the shares and accepted messages than the mpos pool. It could be the load on the public site playing a big factor when I have next to none? Although I am in a VM and it is drawing less than 120MB RAM. CPU is also flat at less than 10%.
3/10 to 3/12
Pool Type Hashrate Coins Coins/Mhs Timeframe
P2Pool 1.95 19,553.15 10,027.25 48 hours
MPOS 6.50 45,008.11 6,924.32 48 hours
P2pool won again by 30%
Here are the previous results:
3/7 to 3/9
Pool Type Hashrate Coins Coins/Mhs Timeframe
MPOS 1.95 19772.289 10139.63 72 hours
P2Pool 6.832 105237.535 15403.62 72 hours
3/6 to 3/7
Pool Type Hashrate Coins Coins/Mhs Timeframe
MPOS 1.95 5988 3070.76 20 hours
P2Pool 6.832 25376 3714.28 20 hours
Anyone seeing similar results or opposing results? Any other benchmarking of pools?
I have 2 sets of mining hardware, one at work (~6.50mhs), the other at home (~1.95mhs). I also switched them vice versa as a comparison. The p2pool is running in a VM at work. (Don't ask how or why about work...)
The MPOS pool is a public pool that I have about a ~35.0 ms latency at stratum-us.xxxxxxxxxxxxxx.com. I am not trying to bash the other site or pool, so I am leaving their name out. But I will say that they are a huge player. So naturally, I'm a bit surprised.
Not bad latency, from home to work I get about ~25.0 ms. The dyn diff on my pool is about 32. The diff of shares on mpos pool, cgminer shows at 512. So my p2pool is more chatty and network latency would come into play more if both share difficulty were the same, but my pool is sending 10x more the shares and accepted messages than the mpos pool. It could be the load on the public site playing a big factor when I have next to none? Although I am in a VM and it is drawing less than 120MB RAM. CPU is also flat at less than 10%.
3/10 to 3/12
Pool Type Hashrate Coins Coins/Mhs Timeframe
P2Pool 1.95 19,553.15 10,027.25 48 hours
MPOS 6.50 45,008.11 6,924.32 48 hours
P2pool won again by 30%
Here are the previous results:
3/7 to 3/9
Pool Type Hashrate Coins Coins/Mhs Timeframe
MPOS 1.95 19772.289 10139.63 72 hours
P2Pool 6.832 105237.535 15403.62 72 hours
3/6 to 3/7
Pool Type Hashrate Coins Coins/Mhs Timeframe
MPOS 1.95 5988 3070.76 20 hours
P2Pool 6.832 25376 3714.28 20 hours
Anyone seeing similar results or opposing results? Any other benchmarking of pools?
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
I read this guide. I have question
minimum system requirement computer or server to install this P2pool?
minimum bandwidth internet connection to run public p2pool?
which server rent to run public p2pool? caused I have plan to make public p2pool.
minimum system requirement computer or server to install this P2pool?
minimum bandwidth internet connection to run public p2pool?
which server rent to run public p2pool? caused I have plan to make public p2pool.
Much will depend on various factors. For example, is this a p2pool for only bitcoin or many other alts too? How many people do you hope to attract to mine on it? How many incoming/outgoing connections for each *coind server? The more instances of p2pool and *coind you are running the more memory, bandwidth, and CPUs (or cores) you'll need.
I am running 4 coind servers on one virtual machine running Ubuntu Server 12.04 LTS. Each coin I add, adds about 80-100mb or RAM usage. My bandwidth is 50 down, 25 up, so I don't see any issues with bandwidth at all. P2pool does measure network usage, but it is very low in the kbps. I am allocating 2GB of RAM to the VM, 40GB disk, and 2 of my CPU cores dedicated to the VM. I am using VMWare Workstation v5. They have been running solid for a week now with no hiccups, errors, or issues. Performing 25% better than my mpos pool. which is weird.
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
I can't seem to find in the json output, logs, or in the code where I can find out what block number my users are working on. Basically I want to know who is working on what block during what time frame.
In the web/log aside from hashrates, miners, shares, there is BLOCK_VALUE and Attempts_to_share.
In local stats, mostly same information.
In recent_blocks, I have a list of all the block numbers, share hash, and block hash.
In current_payouts I have the block hash and payout addresses and timestamps.
The missing piece of the puzzle here is "what block is my node currently working on?".
Is there any way to find out what block is being worked on and during which time? Don't you guys find payments a bit spontaneous? Some blocks we work but don't get paid. Other blocks we get paid quite a bit? I want to be able to connect all the data points.
In the web/log aside from hashrates, miners, shares, there is BLOCK_VALUE and Attempts_to_share.
In local stats, mostly same information.
In recent_blocks, I have a list of all the block numbers, share hash, and block hash.
In current_payouts I have the block hash and payout addresses and timestamps.
The missing piece of the puzzle here is "what block is my node currently working on?".
Is there any way to find out what block is being worked on and during which time? Don't you guys find payments a bit spontaneous? Some blocks we work but don't get paid. Other blocks we get paid quite a bit? I want to be able to connect all the data points.
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
Can you specify the address that any coins should be sent to or are they just sent to an address generated in your *coind?
They go to the coind wallet unfortunately. There's no easy way to adjust that on the fly since the wallets themselves don't support it.
One could perhaps hack the wallet's API call for getblocktemplate to take an extra "payment address" parameter, and block that into the template returned. This way different miners could get different merged work.
I thought that you could specify in the command line for running p2pool the wallet that payments will go to:
-a ADDRESS, --address ADDRESS
generate payouts to this address (default: requested from bitcoind>)
source:
https://en.bitcoin.it/wiki/P2Pool
I plan on using a windows wallet on another computer that I would like payments to go to. My goal would be to seperate the pool and the wallet.
When you launch p2pool, to see if this is working, one of the first checks it will do is determine the default payment address. The address specified should show up there. I haven't tried it myself, but I'm assuming this is how it will work.
Re: Why am I only getting half the coins that coinwarz estimates?
I'm in the same boat as you. I use coinwarz to help understand what some of the most profitable coins are, then I point my miners accordingly. I don't understand when I enter in my hashrate, it calculates the expected coins per day, but I also get about 1/2 the amount.
In fact, even when I look at the pools themselves, I see pools expected values which are much higher than what I am actually getting. I have almost no hardware errors and very few shares actually get rejected. I took the time once on a particular site to look at a block and see my share contributions. It gets very difficult to analyze since every share that I contribute has a different share difficulty. The share difficulty will change from 32 to 512 especially with those pools using var diff.
I think that those expected amounts are based on the most optimal share diff as well as no dead packets and min latency. I've bounced around multiple pools, but still no dramatic increase. I will say that I have seen better results in pools where there are very few miners. I was on a new coin and a pool where I was the 2nd highest hashrate. In that circumstance I was getting 80-90% of what I expected.
In fact, even when I look at the pools themselves, I see pools expected values which are much higher than what I am actually getting. I have almost no hardware errors and very few shares actually get rejected. I took the time once on a particular site to look at a block and see my share contributions. It gets very difficult to analyze since every share that I contribute has a different share difficulty. The share difficulty will change from 32 to 512 especially with those pools using var diff.
I think that those expected amounts are based on the most optimal share diff as well as no dead packets and min latency. I've bounced around multiple pools, but still no dramatic increase. I will say that I have seen better results in pools where there are very few miners. I was on a new coin and a pool where I was the 2nd highest hashrate. In that circumstance I was getting 80-90% of what I expected.
Does someone have an all inclusive networks.py files for altcoins? The most comprehensive one I have seen is https://github.com/Rav3nPL/p2pool-rav/
However he is missing several coins as well as all the new coins. I am going to create a new github that will merge it all together.
In the meantime, I have been looking for: neocoin, grumpycoin, and Diamondcoin
I would appreciate any leads. I will post my github by the end of the week.
Thanks
However he is missing several coins as well as all the new coins. I am going to create a new github that will merge it all together.
In the meantime, I have been looking for: neocoin, grumpycoin, and Diamondcoin
I would appreciate any leads. I will post my github by the end of the week.
Thanks
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
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:
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.
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...
...
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.
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
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:
Then when I try to run the same type of command to start litecoin:
I get errors that keeps repeating:
Testing bitcoind RPC connection to 'http://127.0.0.1:9334/' with username 'litecoinrpc'...
Here is my litecoin.conf file:
Here is the p2pool/bitcoin/networks.py file:
Any help would be so greatly appreaciated! Please leave your BTC or LTC wallet address.
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
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 > --- ---
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
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
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 > --- ---
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
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:daemon=1
rpcuser=litecoinrpc
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
rpcallowip=127.0.0.1
rpcallowip=192.168.0.165
rpcport=9334
port=9335
gen=0
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,
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,
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.
Quote
Quick Update
Stopped dogecoin and attempted to start litecoin. - same errorTried 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
Re: [ANN] Official Neocoin thread - Innovative PoS/PoW Coin with instant messages
Can someone please post the ~/p2pool/networks.py and the ~/p2pool/bitcoin/networks.py.
This should be standard documentation for those that run p2pool to run the coin.
mooncoin=math.Object( #565
PARENT=networks.nets['mooncoin'],
SHARE_PERIOD=25, # seconds target spacing
CHAIN_LENGTH=12*60*60//25, # shares
REAL_CHAIN_LENGTH=12*60*60//25, # shares
TARGET_LOOKBEHIND=20, # shares coinbase maturity
SPREAD=10, # blocks
IDENTIFIER='e8e8c0c0f7f7f9f9'.decode('hex'),
PREFIX='c0c0e8e8f7f7f9f9'.decode('hex'),
P2P_PORT=8664,
MIN_TARGET=0,
MAX_TARGET=2**256//2**20 - 1,
PERSIST=False,
WORKER_PORT=9664,
BOOTSTRAP_ADDRS='p2pool-eu.gotgeeks.com p2pool-us.gotgeeks.com rav3n.dtdns.net doge.dtdns.net pool.hostv.pl p2pool.org p2pool.gotgeeks.com p2pool.dtdns.net solidpool.org'.split(' '),
ANNOUNCE_CHANNEL='#p2pool-alt',
VERSION_CHECK=lambda v: True,
mooncoin=math.Object(
P2P_PREFIX='f9f7c0e8'.decode('hex'),
P2P_PORT=44664,
ADDRESS_VERSION=3,
RPC_PORT=44663,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'tomooncoinaddress' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: 2000000*100000000,
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
BLOCK_PERIOD=90, # s
SYMBOL='MOON',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'MoonCoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Mooncoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.mooncoin'), 'mooncoin.conf'),
BLOCK_EXPLORER_URL_PREFIX='http://moonchain.info/block/',
ADDRESS_EXPLORER_URL_PREFIX='http://moonchain.info/address/',
TX_EXPLORER_URL_PREFIX='http://moonchain.info/tx/',
SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
DUMB_SCRYPT_DIFF=2**16,
DUST_THRESHOLD=0.03e8,
Just like for mooncoin above, I am looking for the values for p2pool mining.
This should be standard documentation for those that run p2pool to run the coin.
mooncoin=math.Object( #565
PARENT=networks.nets['mooncoin'],
SHARE_PERIOD=25, # seconds target spacing
CHAIN_LENGTH=12*60*60//25, # shares
REAL_CHAIN_LENGTH=12*60*60//25, # shares
TARGET_LOOKBEHIND=20, # shares coinbase maturity
SPREAD=10, # blocks
IDENTIFIER='e8e8c0c0f7f7f9f9'.decode('hex'),
PREFIX='c0c0e8e8f7f7f9f9'.decode('hex'),
P2P_PORT=8664,
MIN_TARGET=0,
MAX_TARGET=2**256//2**20 - 1,
PERSIST=False,
WORKER_PORT=9664,
BOOTSTRAP_ADDRS='p2pool-eu.gotgeeks.com p2pool-us.gotgeeks.com rav3n.dtdns.net doge.dtdns.net pool.hostv.pl p2pool.org p2pool.gotgeeks.com p2pool.dtdns.net solidpool.org'.split(' '),
ANNOUNCE_CHANNEL='#p2pool-alt',
VERSION_CHECK=lambda v: True,
mooncoin=math.Object(
P2P_PREFIX='f9f7c0e8'.decode('hex'),
P2P_PORT=44664,
ADDRESS_VERSION=3,
RPC_PORT=44663,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'tomooncoinaddress' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: 2000000*100000000,
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
BLOCK_PERIOD=90, # s
SYMBOL='MOON',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'MoonCoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Mooncoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.mooncoin'), 'mooncoin.conf'),
BLOCK_EXPLORER_URL_PREFIX='http://moonchain.info/block/',
ADDRESS_EXPLORER_URL_PREFIX='http://moonchain.info/address/',
TX_EXPLORER_URL_PREFIX='http://moonchain.info/tx/',
SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
DUMB_SCRYPT_DIFF=2**16,
DUST_THRESHOLD=0.03e8,
Just like for mooncoin above, I am looking for the values for p2pool mining.
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
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.
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?
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
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.
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?
Perhaps someone could help clarify/correct my understanding.
There are a total of 6 ports defined for p2pool and a coin.
For example, there is the coin daemon .conf file that you must you configure, it contains 2 ports. These ports are used by P2pool to connect to the coin daemon. One is a standard rpc, the other is a json format rpc.
rpcport=9334
port=9335
There is also ports defined in the networks.py file for each coin in ~/p2pool/p2pool. In this file it defines a p2p_port which is the port that is used to connect to the p2pool peers for that particular coin. The worker port is fairly easy, it is the port through which your cgminers connect. You will also use this port for the web-static http site.
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,
There is also ports defined in the networks.py file located in ~/p2pool/p2pool/bitcoin. This file seems a bit redundant. I am using a networks.py from https://github.com/Rav3nPL/p2pool-rav/ there are several coins defined in his networks.py. I know some of the coins are out of date. So before I actually install the coin, I insure the ports are correct. In some cases the ports defined in this networks.py file are completely new ports than above. In some cases the ports are defined as the same in daemon .conf file, in other cases they match the networks.py from above. I am fairly certain that the ports here have no purpose.
litecoin=math.Object(
P2P_PREFIX='fbc0b6db'.decode('hex'),
P2P_PORT=9333,
ADDRESS_VERSION=48,
RPC_PORT=9332,
There are a total of 6 ports defined for p2pool and a coin.
For example, there is the coin daemon .conf file that you must you configure, it contains 2 ports. These ports are used by P2pool to connect to the coin daemon. One is a standard rpc, the other is a json format rpc.
rpcport=9334
port=9335
There is also ports defined in the networks.py file for each coin in ~/p2pool/p2pool. In this file it defines a p2p_port which is the port that is used to connect to the p2pool peers for that particular coin. The worker port is fairly easy, it is the port through which your cgminers connect. You will also use this port for the web-static http site.
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,
There is also ports defined in the networks.py file located in ~/p2pool/p2pool/bitcoin. This file seems a bit redundant. I am using a networks.py from https://github.com/Rav3nPL/p2pool-rav/ there are several coins defined in his networks.py. I know some of the coins are out of date. So before I actually install the coin, I insure the ports are correct. In some cases the ports defined in this networks.py file are completely new ports than above. In some cases the ports are defined as the same in daemon .conf file, in other cases they match the networks.py from above. I am fairly certain that the ports here have no purpose.
litecoin=math.Object(
P2P_PREFIX='fbc0b6db'.decode('hex'),
P2P_PORT=9333,
ADDRESS_VERSION=48,
RPC_PORT=9332,
Re: P2Pool only sends coins found to default coin daemon - can't pay miners
I'm running dogecoin right now. Testing with 1 coin.
I added 7 miners to it, total of ~14Mhs of mining. Payouts are coming on average every 1 hour.
When I ran the pool with only 1 miner, memory was at 150MB. After adding 7 miners, memory is about 210MB.
http://s2.postimg.org/rnveu3sop/memoryscreen.png
image: http://postimg.org/image/kxexko5it/
Here is some additional information:
Latency ~ 0.01967s
DOA ~ 6.4%
Efficiency ~ 99.31%
Things are looking great!
I will be re-writing all of the charts graphs from https://github.com/hardcpp/P2PoolExtendedFrontEnd
I like what he has done, but I am taking it a step further.
Also, I will be modifying the p2pool source to include additional logging capabilities.
I have virtual machines running now with the same dogecoin pool. I did one, ran it, then did another to make sure I could repeat it. I also hardened some of the security, logins, passwords, and ports. I used Ubuntu Server 12.04. It has no desktop and is wicked fast! It boots up in about 2-3 seconds! Building in some redundancy and fail-over.
I added 7 miners to it, total of ~14Mhs of mining. Payouts are coming on average every 1 hour.
When I ran the pool with only 1 miner, memory was at 150MB. After adding 7 miners, memory is about 210MB.
http://s2.postimg.org/rnveu3sop/memoryscreen.png
image: http://postimg.org/image/kxexko5it/
Here is some additional information:
Latency ~ 0.01967s
DOA ~ 6.4%
Efficiency ~ 99.31%
Things are looking great!
I will be re-writing all of the charts graphs from https://github.com/hardcpp/P2PoolExtendedFrontEnd
I like what he has done, but I am taking it a step further.
Also, I will be modifying the p2pool source to include additional logging capabilities.
I have virtual machines running now with the same dogecoin pool. I did one, ran it, then did another to make sure I could repeat it. I also hardened some of the security, logins, passwords, and ports. I used Ubuntu Server 12.04. It has no desktop and is wicked fast! It boots up in about 2-3 seconds! Building in some redundancy and fail-over.
Re: P2Pool only sends coins found to default coin daemon - can't pay miners
I'm running for altcoins for the moment. Everything is running just fine now. It's been up and stable for 2 days now, payments coming about every 1.5 hours.
Payouts are happening just fine to the individual miners. Logs are well, no errors. Jason web stats are accurate. Good hash rates, and better hashing than other pools. I am quite happy with the setup. Putting load on it now.
Payouts are happening just fine to the individual miners. Logs are well, no errors. Jason web stats are accurate. Good hash rates, and better hashing than other pools. I am quite happy with the setup. Putting load on it now.
Re: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux
Makes sense.
What I want to be able to do is very similar to the proxy.
I like what they say:
There are many advantages for mining on P2Pool, however as the hash rate of P2Pool network grows, so does share difficulty. Many miners have experienced hour long 'dry spells' where no payouts are received. This is a problem inherent to the design of P2Pool.
Proxy pools solve this problem by creating sub-pools that feed into the P2Pool network, each one managing the payouts for miners under them. This will allow the P2Pool network to scale to many times its current size while ensuring fair payout for all patrons.
The idea is really good and that is what I would like to do is create a sub pool and manage the payouts. There must be some sort of calculation that p2pool uses to determine which miner gets paid what. I just need that same information from p2pool.
Regards
What I want to be able to do is very similar to the proxy.
I like what they say:
There are many advantages for mining on P2Pool, however as the hash rate of P2Pool network grows, so does share difficulty. Many miners have experienced hour long 'dry spells' where no payouts are received. This is a problem inherent to the design of P2Pool.
Proxy pools solve this problem by creating sub-pools that feed into the P2Pool network, each one managing the payouts for miners under them. This will allow the P2Pool network to scale to many times its current size while ensuring fair payout for all patrons.
The idea is really good and that is what I would like to do is create a sub pool and manage the payouts. There must be some sort of calculation that p2pool uses to determine which miner gets paid what. I just need that same information from p2pool.
Regards
Re: P2Pool only sends coins found to default coin daemon - can't pay miners
Quick update.
Initially when I started the miners, in the address I put a user name in the worker user. This will cause all the coins mined to be dumped into the server's wallet address for p2pool. It was later that I put in actual wallet addresses. After putting the new wallet address for a couple of hours, payments still went to the server address. However, it then started to work and all the remaining payments have now gone to the individual wallets and it seems to be working as expected now.
The p2pool also has very good DOA + orphan. I'm getting much better payouts than I when connected to another pool. But, time will tell, could just be luck playing a role.
Thanks
Initially when I started the miners, in the address I put a user name in the worker user. This will cause all the coins mined to be dumped into the server's wallet address for p2pool. It was later that I put in actual wallet addresses. After putting the new wallet address for a couple of hours, payments still went to the server address. However, it then started to work and all the remaining payments have now gone to the individual wallets and it seems to be working as expected now.
The p2pool also has very good DOA + orphan. I'm getting much better payouts than I when connected to another pool. But, time will tell, could just be luck playing a role.
Thanks
Re: P2Pool only sends coins found to default coin daemon - can't pay miners
Okay, so something went wrong, I can fully redo all the steps.
However, I just want to confirm the scenario:
I can run a p2pool node and have multiple miners connected to my pool. They would put their wallet address in cgminer's user field. Then, they would receive coins directly.
Please confirm, this is the case.
Thanks
However, I just want to confirm the scenario:
I can run a p2pool node and have multiple miners connected to my pool. They would put their wallet address in cgminer's user field. Then, they would receive coins directly.
Please confirm, this is the case.
Thanks