I will give it a try when I'm home in a few hours. But last time, I chnaged my networks.py to work together with the other Pools, the performance of the pool got really bad. And the other pools had the same Problem....
I had the same thing happen to me! Disconnected from the other pools until tonight so will keep a close eye on it. BTW, what are you using for SPREAD? I don't think hackbanes setting of 72 is correct. |
|
|
|
Have the p2pools looked at using common settings yet?
I would love to see that happen! I think it would be better for the network if the p2pools work together instead of independently. There seems to be a handful of pools using the hakabane fork that are already working together. Please correct these instructions if I'm wrong but this is what P2Pool operators need to do to connect to the pools that are already working together: 1. Modify p2pool/networks.py in the digitalcoin section to include: IDENTIFIER='a5aed03050126d6d'.decode('hex'),
PREFIX='b6c0601991aa19a3'.decode('hex'),
BOOTSTRAP_ADDRS='pool.bounceme.net'.split(' '),I am not sure if this is necessary but you may need to change: Open up that port to and from your p2pool server on the firewall (incoming/outgoing). You will need to delete the digitalcoin folder in the p2pool\Data directory before starting up p2pool. We should consider adding more servers to the BOOTSTRAP_ADDRS in case pool.bounceme.net is down. |
|
|
|
|
Very nice site Kevin! Good job. I look forward to seeing it evolve.
|
|
|
|
We found our first 5 blocks!
Extreme luck? ...or lower diff? Have made more within the first hour here than I have mining WDC anywhere else.
and how many orphans? I'm noticing whenever diff on WDC drops below 1, number of orphans increasing till almost 50% - Which makes it half efficient - means - mining crap... Zero  |
|
|
|
Ok, took a bit of doing but I have a Worldcoin P2Pool running at: stratum+tcp://wdc.xpool.net:8820Please test it out! You should get low latency which is always good for P2Pools. 0% fee up to a pool rate of 20Mh/s. Stats: http://wdc.xpool.net:8820Example Connection String: cgminer -o stratum+tcp://wdc.xpool.net:8820 -u WgHv6cjRbntvPbB5VU7iKxX4Qr9xnRL1g1 -p password --scryptMake sure to replace the example wallet address with your own. More info: https://bitcointalk.org/index.php?topic=217139.msg2281429#msg2281429Thanks! We found our first 5 blocks! Extreme luck? ...or lower diff? Have made more within the first hour here than I have mining WDC anywhere else. |
|
|
|
Ok, took a bit of doing but I have a Worldcoin P2Pool running at: stratum+tcp://wdc.xpool.net:8820Please test it out! You should get low latency which is always good for P2Pools. 0% fee up to a pool rate of 10Mh/s. Stats: http://wdc.xpool.net:8820Example Connection String: cgminer -o stratum+tcp://wdc.xpool.net:8820 -u WgHv6cjRbntvPbB5VU7iKxX4Qr9xnRL1g1 -p password --scryptMake sure to replace the example wallet address with your own. More info: https://bitcointalk.org/index.php?topic=217139Thanks! |
|
|
|
|
DCu3kjPoQmEftAqUN1rY8sYNbVeFRomDvU
|
|
|
|
|
HEpuWAAA7zHfHXvdUjCPi8WjZEX82jihMt
|
|
|
|
|
Well, could not get my miner to remote connect to the wallet (different machines). It's working for others but I imagine most have their wallets loaded onto the same computer as their miners. I like to isolate the wallets.
Noticed the wallet uses the default ports of:
rpcport=7452
port=17453
Maybe the developer messed up a little there. Also noticed that other coins open up two connections for each port. IPv4 and IPv6. This one only does IPv4 on 17453. No big deal..just observations.
|
|
|
|
Cart I'll bring one up with your settings. Can you paste both networks.py fiiles ? Thx
That would be awesome! Lets avoid the DGC P2Pool situation where everyone is on their own. Will work on this after dinner...which is getting cold because I cant get off the forum  |
|
|
|
|
HEpuWAAA7zHfHXvdUjCPi8WjZEX82jihMt
|
|
|
|
This seems like an OK coin:
1. Very small premine (only 128k TOTAL are in circulation right now)
2. Windows client, with correct port opened, made 65 connections
3. Low orphan/reject rates at difficulty of 0.11170942
4. Low block reward (25). No random blocks. No huge early blocks.
5. 40 seconds is a good time between blocks. Long enough to be secure but fast enough to facilitate quick transactions
6. Working windows client and working linux code at launch
7. Cool name and icon
8. Source on github instead of megafileshare
I don't agree. Number 6 on your list is correct, but with one caveat. The instructions for mining the coin which instruct all miners which ports are used were incorrect. Only those of us that noticed the windows client using a different port were able to mine. These kind of mistakes with the pre-mine don't make this a very good launch IMO. I understand after looking at the netstat this the wallet that it is using 17453 and 17452. It was an honest mistake. But I still mined no problem solo. Hey, no problem. We all make mistakes HYC: HEpuWAAA7zHfHXvdUjCPi8WjZEX82jihMt |
|
|
|
Setting up for solo mining:
Create a hypercoin.conf file in %Appdata%/Roaming/hypercoin/
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rcpallowip=192.168.1.*
rpcport=7452
port=7453
daemon=1
server=1
gen=0
addnode=82.211.31.244
Wait a sec... aren't the ports WRONG in the original post?! I see the wallet client using 17453 not 7453. If that's the case wouldn't it make sense to make rpcport=17452? (offline for a couple of hours but I'll be back later) |
|
|
|
p2pool pls  I'll bring one up but lets agree to some of these settings so other p2pools can join and we don't have a bunch of independent P2Pools: hypercoin=math.Object(
PARENT=networks.nets['hypercoin'],
SHARE_PERIOD=15, # seconds target spacing
CHAIN_LENGTH=24*60*60//10, # shares
REAL_CHAIN_LENGTH=24*60*60//10, # shares
TARGET_LOOKBEHIND=200, # shares coinbase maturity
SPREAD=30, # blocks
IDENTIFIER='xxxxxxxxxxxx'.decode('hex'),
PREFIX='xxxxxxxxxxxxxxxx'.decode('hex'),
P2P_PORT=9775,
MIN_TARGET=0,
MAX_TARGET=2**256//2**20 - 1,
PERSIST=False,
WORKER_PORT=8820,
BOOTSTRAP_ADDRS=''.split(' '),
ANNOUNCE_CHANNEL='#p2pool-alt',
VERSION_CHECK=lambda v: True,
), |
|
|
|
|
So the real power of P2Pools is them all connecting together and working as a whole right? This is not happening with DGC P2Pools. I imagine it is because everyone (me included) is using their own code?
|
|
|
|
Hi Akabane, I've tried your update p2pool for digitalcoin, but I'm still getting this error 2013-05-28 07:02:05.676154 Handshake timed out, disconnecting from 88.161.131.83:8119
2013-05-28 07:02:15.034469 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 1 (0 incoming)
2013-05-28 07:02:15.035127 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-05-28 07:02:20.640012 Handshake timed out, disconnecting from 54.227.253.120:9500
2013-05-28 07:02:21.779768 Handshake timed out, disconnecting from 88.161.131.83:8119
2013-05-28 07:02:28.477534 Handshake timed out, disconnecting from 93.186.200.124:8907
2013-05-28 07:02:30.035985 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 1 (0 incoming)
2013-05-28 07:02:30.036211 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-05-28 07:02:31.923578 Handshake timed out, disconnecting from 108.58.12.54:21111
2013-05-28 07:02:40.297147 Handshake timed out, disconnecting from 54.227.253.120:9500
2013-05-28 07:02:42.248439 Handshake timed out, disconnecting from 216.177.81.88:8810
2013-05-28 07:02:45.037360 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 1 (0 incoming)
2013-05-28 07:02:45.037642 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2013-05-28 07:02:46.569491 Handshake timed out, disconnecting from 88.161.131.83:8119
2013-05-28 07:02:47.497390 Handshake timed out, disconnecting from 54.244.198.104:8119
2013-05-28 07:02:54.178693 Handshake timed out, disconnecting from 199.188.206.150:24397
2013-05-28 07:02:55.084187 Handshake timed out, disconnecting from 93.186.200.124:8907
2013-05-28 07:02:56.112175 Handshake timed out, disconnecting from 108.58.12.54:21111
2013-05-28 07:02:56.669826 Handshake timed out, disconnecting from 216.177.81.88:8810
I launch the pool with the following parameters: screen -d -m -S ltcp2pool ./run_p2pool.py --give-author 0 --fee 0 --bitcoind-p2p-port 7999 --bitcoind-rpc-port 7998 --net digital xxx xxx Do you have any suggestion? I think others people with old version are trying to connect to your node. Have you changed your listen ports after upgrading ? 2013-05-28 07:02:45.037360 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 1 (0 incoming) Means you are correctly connected to my node I think. I updated my code to connect to the new port (25396). I seem to be the only other pool connected to pool.bounceme.net at the moment where before there were quite a few others. |
|
|
|
I had crashing problems with cgminer after setting the following environment variables:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
I had to remove the second (use_sync_objects) and remove it from the registry, too (under HKEY_CURRENT_USER\Environment) and it worked!
BTW the first one (max_alloc_percent) is recommended to be able to use high thread-concurrency values.
That's strange. I use the setx GPU_USE_SYNC_OBJECTS 1 setting and it works fine for me. What does this one do? |
|
|
|
xPool.net BTC - LTC - DGC - WDC PPLNS P2Pool - World-class Data Center - Dedicated Enterprise Class Equipment - 1% fee Features- No account registration or passwords to remember
- Instant payout when a block is found
- Block finder bonus (0.5% of the block payout)
- Transaction fees given to miners
- No coins stored on pool server
- Maintain your PPLNS level switching between connected p2pools nodes
- Payout for your shares continue from P2Pool if a node goes down
- 3 hour PPLNS window for Digitalcoin, Worldcoin, and Craftcoin
Bitcoin stratum+tcp://btc.xpool.net:9332Litecoin stratum+tcp://ltc.xpool.net:9327Digitalcoin (beta) stratum+tcp://dgc.xpool.net:8810Worldcoin (beta) stratum+tcp://wdc.xpool.net:8820Craftcoin (beta) stratum+tcp://crc.xpool.net:8830For getwork clients replace stratum+tcp:// with http://Login Username: Your Wallet Address Password: Any password you like Example Connection Strings Bitcoin cgminer -o stratum+tcp://btc.xpool.net:9332 -u YourWalletAddress -p password Litecoin cgminer -o stratum+tcp://ltc.xpool.net:9327 -u YourWalletAddress -p password --scrypt Digitalcoin cgminer -o stratum+tcp://dgc.xpool.net:8810 -u YourWalletAddress -p password --scrypt --queue 0 --scan-time 5 --expiry 10 Worldcoin cgminer -o stratum+tcp://wdc.xpool.net:8820 -u YourWalletAddress -p password --scrypt --queue 0 --scan-time 5 --expiry 10 Craftcoin cgminer -o stratum+tcp://crc.xpool.net:8830 -u YourWalletAddress -p password --scryptMake sure to replace YourWalletAddress Statistics: Bitcoin http://btc.xpool.net:9332 Litecoin http://ltc.xpool.net:9327 Digitalcoin http://dgc.xpool.net:8810 Worldcoin http://wdc.xpool.net:8820 Craftcoin http://crc.xpool.net:8830Internet Explorer may not display current data after a browser refresh. Please try using Chrome instead. Share DifficultyYou can set the level of difficulty sent to your miner by appending a difficulty setting to your wallet address. The following difficulty settings can be used as a guide: Kh/s Difficulty
1 +0.00000116
50 +0.000058
100 +0.000116
250 +0.00029
500 +0.00058
750 +0.00087
1000 +0.00116
1250 +0.00145
1500 +0.00174
1750 +0.00203
2000 +0.00232
To determine the difficulty for your specific hash rate multiply by 0.00000116 For example, if your miner is capable of 1440 Kh/s: 1440 * 0.00000116 = 0.0016704Example Connection String for a miner capable of 1440 Kh/s: cgminer -o stratum+tcp://ltc.xpool.net:9327 -u LQgjHVugooxdrEf86Seaxj1BC7G7HjWPfe+0.0016704 -p password --scryptLive SupportI try to be on IRC as much as possible on these channels: #bitcoin, #digitalcoin, #litecoin, #p2pool, #worldcoin, #xpool New block announcements are made in the #xpool channel except for WDC. Go to the #worldcoin channel for WDC block announcements. Frequently Asked QuestionsQ: Why does my miner report so many longpoll/stratum from pool request work restarts? A: This is normal. It is how often p2pool shares are generated. More info:https://bitcointalk.org/index.php?topic=217139 |
|
|
|
|
Show Posts
