Those first solo blocks are awesome hahaha
Topic: [ANN] USCoin - Here's the change! [USC] - page 6. (Read 17873 times)
Replied, no worries
Those first solo blocks are awesome hahaha
Those first solo blocks are awesome hahaha
Your coins will arrive in the host wallet.
i found 2 block appearance in my wallet +40 twice
elx i sent pm for you
but im going to back p2pool but i have issue stratum connect
is there another pools?
352.08 MH/s networker
i found just 2 blocks but now i know how to mine solo
thx for everybody
Your coins will arrive in the host wallet.
now working how can i check hashrate?Should show in your miner.
ops nothing hashrate i wrote wrong , my coins
it's normal "new block detected on net"...
Indeed it is normal.
now working how can i check hashrate?Should show in your miner.
ops nothing hashrate i wrote wrong , my coins
it's normal "new block detected on net"...
now working how can i check hashrate?Should show in your miner.
now working how can i check hashrate? Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::f0b7:4832:89fe:201b%10
IPv4 Address. . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Link-local IPv6 Address . . . . . : fe80::f0b7:4832:89fe:201b%10
IPv4 Address. . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Then mine using 192.168.1.100
edit
^
I believe that's basically the only possible issue now. Some routers assign 192.168.15.x and other semi-random numbers to avoid potential conflicts I guess, just double check.
I believe that's basically the only possible issue now. Some routers assign 192.168.15.x and other semi-random numbers to avoid potential conflicts I guess, just double check.
Looks like it's working to me for your host machine. That long polling message isn't a problem.
Are you sure your host is 192.168.1.1?? You can check by typing ipconfig into cmd. Look for address that starts with 192.168.1.?? and enter that one in.
Are you sure your host is 192.168.1.1?? You can check by typing ipconfig into cmd. Look for address that starts with 192.168.1.?? and enter that one in.
Make sure your .conf name looks like 'USCoin.conf' (caps for the first 3 letters) and also make sure it isn't a .txt.bat, notepad will spit that out by default unless you change the file type to 'all' when saving.
Are you able to solo mine on the host machine through localhost/127.0.01?
Are you able to solo mine on the host machine through localhost/127.0.01?
yes host machine i can mine (i think)
[2013-05-25 03:03:46] Started cgminer 3.0.1
[2013-05-25 03:03:46] Probing for an alive pool
[2013-05-25 03:03:47] Network diff set to 8.19K
[2013-05-25 03:03:47] No suitable long-poll found for http://127.0.0.1:9332 <<=== is it a issue?
[2013-05-25 03:03:57] Network diff set to 8.19K
[2013-05-25 03:03:57] New block detected on network
[2013-05-25 03:04:07] Network diff set to 8.19K
[2013-05-25 03:04:07] New block detected on network
Make sure your .conf name looks like 'USCoin.conf' (caps for the first 3 letters) and also make sure it isn't a .txt.bat, notepad will spit that out by default unless you change the file type to 'all' when saving.
Are you able to solo mine on the host machine through localhost/127.0.01?
Are you able to solo mine on the host machine through localhost/127.0.01?
If you want to run separate wallets then yes, you would need to set each one to localhost/127.0.0.1
Ideally, we will avoid the complication/nuisance of multiple wallets.
Let's try simplifying those launch commands, cgminer shouldn't be closing like that but I've found it to be rather particular and sometimes highly illogical.
cgminer --scrypt -o http://192.168.1.1:9332 -u **** -p *****
try removing that secondary rpcport (80) in your uscoin.conf, could be causing a bit of trouble.
Ideally, we will avoid the complication/nuisance of multiple wallets.
Let's try simplifying those launch commands, cgminer shouldn't be closing like that but I've found it to be rather particular and sometimes highly illogical.
cgminer --scrypt -o http://192.168.1.1:9332 -u **** -p *****
try removing that secondary rpcport (80) in your uscoin.conf, could be causing a bit of trouble.
[2013-05-25 02:47:32] Probing for an alive pool
[2013-05-25 02:47:39] Pool 0 slow/down or URL or credentials invalid
but is the same from .conf -u xx - p x
If you want to run separate wallets then yes, you would need to set each one to localhost/127.0.0.1
Ideally, we will avoid the complication/nuisance of multiple wallets.
Let's try simplifying those launch commands, cgminer shouldn't be closing like that but I've found it to be rather particular and sometimes highly illogical.
cgminer --scrypt -o http://192.168.1.1:9332 -u **** -p *****
try removing that secondary rpcport (80) in your uscoin.conf, could be causing a bit of trouble.
Ideally, we will avoid the complication/nuisance of multiple wallets.
Let's try simplifying those launch commands, cgminer shouldn't be closing like that but I've found it to be rather particular and sometimes highly illogical.
cgminer --scrypt -o http://192.168.1.1:9332 -u **** -p *****
try removing that secondary rpcport (80) in your uscoin.conf, could be causing a bit of trouble.
D:
Your .conf looks good, did you try 'cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:9332 -u x -p x' ??
You could run multiple wallets (one per machine with different addresses) but I think your hashes will potentially be less effective.
Your .conf looks good, did you try 'cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:9332 -u x -p x' ??
You could run multiple wallets (one per machine with different addresses) but I think your hashes will potentially be less effective.
yes , cgminer open and closed
Code:
rpcuser=x
rpcpassword=x
maxconnections=100
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1
rpcallowip=192.168.*.*
rpcport=9332
rpcport=80
testnet=0
daemon=1
server=1
gen=0
addnode=24.162.172.119
addnode=67.233.57.113
addnode=65.87.180.248
addnode=54.217.218.132
addnode=54.217.218.219
addnode=54.217.218.231
addnode=54.217.218.234
addnode=54.217.218.238
rig 2 and 3 - i got cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:9332 -u x -p x' ??
rig 2 and 3 - do i need get uscoin.conf? dont i?
D:
Your .conf looks good, did you try 'cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:9332 -u x -p x' ??
You could run multiple wallets (one per machine with different addresses) but I think your hashes will potentially be less effective.
Your .conf looks good, did you try 'cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:9332 -u x -p x' ??
You could run multiple wallets (one per machine with different addresses) but I think your hashes will potentially be less effective.
Nope, a single wallet with an 'rpcallowip:x.x.x.x' per machine in the uscoin.conf will do it
but if i dont have wallet where can i put uscoin.conf?
You only need the single wallet (let's call it the host @ 192.168.1.1) and you just edit that particular .conf file.
So, if you want to connect machine 2 (192.168.1.2) to the host, your host/wallet would have rpcallowip:192.168.1.2. Then, your miner would be instructed to connect to 192.168.1.1:whateverport .
Hopefully I'm not forgetting something/making a stupid mistake in this explanation, heh.
"rpcport=80" < I don't think you need that.
rpcuser=x
rpcpassword=x
maxconnections=100
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1
rpcallowip=192.168.*.*
rpcport=9332
testnet=0
daemon=1
server=1
gen=0
is this good?
Color 0E
cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:8888 -u x -p x FOR RIG2
Color 0E
cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:8888 -u x -p x FOR RIG3
correct?
And gimme your wallet
I think that's good except for 'rpcport=9332' should match the ports on your miner configs...iirc that is...my brain is about to turn off I think lol.
Scooby903 indeed! Very easy to overlook.
i give up =/
Nope, a single wallet with an 'rpcallowip:x.x.x.x' per machine in the uscoin.conf will do it
but if i dont have wallet where can i put uscoin.conf?
You only need the single wallet (let's call it the host @ 192.168.1.1) and you just edit that particular .conf file.
So, if you want to connect machine 2 (192.168.1.2) to the host, your host/wallet would have rpcallowip:192.168.1.2. Then, your miner would be instructed to connect to 192.168.1.1:whateverport .
Hopefully I'm not forgetting something/making a stupid mistake in this explanation, heh.
"rpcport=80" < I don't think you need that.
rpcuser=x
rpcpassword=x
maxconnections=100
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1
rpcallowip=192.168.*.*
rpcport=9332
testnet=0
daemon=1
server=1
gen=0
is this good?
Color 0E
cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:8888 -u x -p x FOR RIG2
Color 0E
cgminer --scrypt -s 5 --queue 0 --expiry 5 -o http://192.168.1.1:8888 -u x -p x FOR RIG3
correct?
And gimme your wallet
I think that's good except for 'rpcport=9332' should match the ports on your miner configs...iirc that is...my brain is about to turn off I think lol.
Scooby903 indeed! Very easy to overlook.
Guys, also make sure you are starting the QT in server mode...
rpcuser=x
rpcpassword=x
maxconnections=100
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1
rpcallowip=192.168.*.*
rpcport=9332
rpcport=80
testnet=0
daemon=1
server=1
gen=0
for qt server?
Jump to: