Pages:
Author

Topic: Antminer S1 SoloMining Setup/Easy Solo/Own Pool Setup! - page 3. (Read 19343 times)

full member
Activity: 202
Merit: 100
i used this guide and solo mined for a few days. after that i installed the p2pool version 13.4 and was mining bitcoins on p2pool with every one else and not solo mining. however, when i now want to solo mine and run the bat file, it connects to the bitcoin p2pool and is not solo mining any more. can anyone help me with this. i cant figure out why this is happening.
thanks.
newbie
Activity: 48
Merit: 0
I setup the Litecoin P2Pool but there is some mistake


You are using Scrypt miners to mine Litecoin correct?
You also did the extra step for Scrypt coins?


I cannot double check p2pool configs at the moment hardware fault with the box I was using for testing.
That and I have to revise the guide due to some changes in p2pool.
I'll update when I can.
newbie
Activity: 12
Merit: 0
I setup the Litecoin P2Pool but there is some mistake

ock: 6.7 hours
2014-07-04 12:12:10.854000 New work for worker! Difficulty: 0.232827 Share diffi
culty: 27.127695 Total block value: 50.000000 LTC including 0 transactions
2014-07-04 12:12:11.104000 P2Pool: 17317 shares in chain (9029 verified/17321 to
tal) Peers: 6 (0 incoming)
2014-07-04 12:12:11.104000  Local: 0H/s in last 0.0 seconds Local dead on arriva
l: Huh Expected time to share: Huh
2014-07-04 12:12:11.104000  Shares: 0 (0 orphan, 0 dead) Stale rate: Huh Efficie
ncy: Huh Current payout: 0.0000 LTC
2014-07-04 12:12:11.104000  Pool: 2690MH/s Stale rate: 14.3% Expected time to bl
ock: 6.7 hours

My miner status is alive and found 3-15 blooks just for 30mins?Huh

i config it to mine at port 9327

litecoin.conf is

server=1
daemon=1
rpcuser=Kun
rpcpassword=fire
rpcallowip=10.1.211.51
rpcallowip=127.0.0.1
rpcport=10332
port=10333
gen=0


newbie
Activity: 12
Merit: 0
Dear
I've tried to setup litecoin pool but there is mistake like that

f:\BitDig\Python\Lib\site-packages>run_p2pool.py --net "litecoin" --give-author
0.0 --no-bugreport --disable-upnp -a LNWPn9sDAkSoofaZSFQHj8Y6dSeC1ecjqR
Traceback (most recent call last):
  File "F:\BitDig\Python\Lib\site-packages\run_p2pool.py", line 3, in
    from p2pool import main
  File "F:\BitDig\Python\Lib\site-packages\p2pool\main.py", line 25, in

    from . import networks, web, work
  File "F:\BitDig\Python\Lib\site-packages\p2pool\networks.py", line 48
    litecoin=math.Object(
SyntaxError: keyword argument repeated



Whats my problem?
sr. member
Activity: 369
Merit: 250
Just to let you all know that I've been tweaking the p2pool settings using the tutorials that up (such as: http://www.guugll.eu/guide-mining-efficiently-p2pool/) and to get your dead/orphan shares to go down and obtain better overall performance it's a matter of getting your miners to take "smaller bites" instead of the bigger ones they normally do. So far just setting the max connections to the suggested 20 in the .conf file made my dead and orphans shares drop like a rock. I'm using an S1 over WiFi so it was suggested to do something as such but it will be different depending on how your miner is set up. I'll still need to do more fiddling to get better performance but at least it a start.

EDIT: Lowering my block value has also done wonders for my share rate. So I guess we got our answer about the dead/orphans. Now if I can just get my stales to go down. Any ideas?
sr. member
Activity: 369
Merit: 250
Constant, it doesn't seem to be affecting anything but it's annoying.

I do see the hash rash increasing over time and I' just read up on fine tuning the p2pool setting so I'll try that next.
newbie
Activity: 48
Merit: 0
Thanks for this thread, works great but I am getting a lot of dead shares. I have two questions:

If its dead share's as you just start mining this is normal as p2pool adjusts share difficulty against hashrate.
You can try:
Code:
+1 to 1000
After your coin address but it only seems to work for certain coins.

Quote

1. Do you know how to add coins to the networks.py that don't come with the p2pool originally?

It involves going through the coin source code of the one you want to add and adding the correct info manually.
Or just contact the Coin Developer and ask for the p2pool info that has to be added for p2pool mining to work.

Quote
2. I keep getting this error about a 'bad peer" being connected to itself. I thought it was the fact that I am using 127.0.0.1 in the config file but that wasn't it.

This is a new one.
Is this a random error or a constant one?
sr. member
Activity: 369
Merit: 250
Thanks for this thread, works great but I am getting a lot of dead shares. I have two questions:

1. Do you know how to add coins to the networks.py that don't come with the p2pool originally?

2. I keep getting this error about a 'bad peer" being connected to itself. I thought it was the fact that I am using 127.0.0.1 in the config file but that wasn't it.
newbie
Activity: 48
Merit: 0
if i have multiple antminers, would i enter the same local bitcoin address for all the user name's or can i have different bitcoin addresses as well?
You can have a different or the same Bitcoin address for Each Ant if you want as long as its a local wallet (Not an Exchange address) you shouldn't have an issue getting payments.

full member
Activity: 202
Merit: 100
if i have multiple antminers, would i enter the same local bitcoin address for all the user name's or can i have different bitcoin addresses as well? lovely guide. though encountered a few hiccups, managed to get on. was not working, but for some reason the node was taking the .conf file in the roaming directory and not the one in my other hard disk which is where bitcoin data is located. once i copied the .conf to the roaming file, it was smooth sailing after that.
member
Activity: 112
Merit: 10
Good job with this. Been looking for a guide for this for awhile now.
Much thanks.
full member
Activity: 176
Merit: 110
I have no idea what's gone wrong but this is now what I am getting:


http://i.imgur.com/EEZ5fQP.jpg

http://i.imgur.com/G8oRJh7.jpg
full member
Activity: 176
Merit: 110
I found where I was going wrong - I thank you again.

got one ant up and running Cheesy
newbie
Activity: 48
Merit: 0
Don't be sorry we all have to learn some way.

So your info for your Ants would be:
Code:
Your S1 Mining entries would be:
192.168.0.200:9332
"ALocalBitcoinaddress"
x

full member
Activity: 176
Merit: 110
Sorry about this. Guess its meant for people with a decent level of IT knowledge.


This is my networks.py:

Quote
nets = dict(
    bitcoin=math.Object(
        PARENT=networks.nets['bitcoin'],
        SHARE_PERIOD=30, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=3, # blocks
        IDENTIFIER='fc70035c7a81bc6f'.decode('hex'),
        PREFIX='2472ef181efcd37b'.decode('hex'),
        P2P_PORT=9333,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**32 - 1,
        PERSIST=False,
        WORKER_PORT=9332,
        BOOTSTRAP_ADDRS=''.split(' '),
        ANNOUNCE_CHANNEL='#p2pool',
        VERSION_CHECK=lambda v: 50700 <= v < 60000 or 60010 <= v < 60100 or 60400 <= v,
        VERSION_WARNING=lambda v: 'Upgrade Bitcoin to >=0.8.5!' if v < 80500 else None,
    ),
)
for net_name, net in nets.iteritems():
    net.NAME = net_name

newbie
Activity: 48
Merit: 0
I'm following this guide but still keep getting: "Local: 0H/s in last 0.0 seconds Local dead on arrival"

I think I'm getting confused over the IP addresses and ports.

My conf file is as follows:

server=1
rpcuser=ads2003uk
rpcpassword=RANDOMLETTERS
rpcallowip=192.168.0.200
rpcport=17444
port=17334

My S1 pool entries are:
192.168.0.200:17334
ads2003uk
SAMERANDOMLETTERS

and still nothing, where am I going wrong?
In the past 4days between my 5 S1's I've found 2 blocks on Ghash.io (thats what the console tells me) so I'd like to have a crack at solo with them.

Seeing there seems to be some problem getting the right info in the right spot.

Code:
server=1
rpcuser=ads2003uk
rpcpassword=RANDOMLETTERS
rpcallowip=192.168.0.200
rpcport=17444
port=17334
That goes into your "coin.conf" file.

Code:
My S1 pool entries are:
192.168.0.200:17334
ads2003uk
SAMERANDOMLETTERS

This is incorrect.
It's:
Code:
IP address of the p2pool server and its worker port. NOT the port of the wallet Client Server. You can check what port in networks.py in p2pool or it's shown when you first start p2pool.
Coinyourmining address to send payments to MUST be a local wallet
"x" as password or anything it's ignored

full member
Activity: 176
Merit: 110
Strictly speaking, this can not be considered solo mining, another recent p2pool hashrate very low, so it seems worthwhile

ok, but that is not what I've asked, a guide has been written, and I'm asking for clarification.

It's not just BTC im interested in doing but other ALTcoins.

Can you assist?
newbie
Activity: 56
Merit: 0
Strictly speaking, this can not be considered solo mining, another recent p2pool hashrate very low, so it seems worthwhile
full member
Activity: 176
Merit: 110
I'm following this guide but still keep getting: "Local: 0H/s in last 0.0 seconds Local dead on arrival"

I think I'm getting confused over the IP addresses and ports.

My conf file is as follows:

server=1
rpcuser=ads2003uk
rpcpassword=RANDOMLETTERS
rpcallowip=192.168.0.200
rpcport=17444
port=17334

My S1 pool entries are:
192.168.0.200:17334
ads2003uk
SAMERANDOMLETTERS

and still nothing, where am I going wrong?
In the past 4days between my 5 S1's I've found 2 blocks on Ghash.io (thats what the console tells me) so I'd like to have a crack at solo with them.
newbie
Activity: 33
Merit: 0
Thank you for the good guide!
Pages:
Jump to: