yes. its not gen=0 gave problem. But guiminer port not storing.
Always port changes to 8332 after restart of guiminer.
Topic: [ANNOUNCE] New alternate cryptocurrency - Geist Geld - page 14. (Read 74212 times)
The reason for not mining is very simple.
Its not due to not correctly pointing to bitcoin client.
Its for this reason config in bitcoin.conf
On next release update gen=1.
Also i see a strange problem in guiminer. Even after configuring & SAVING & mining, restarting guiminer with quit changes the port back to 8332 in stead of 8777.
Seems guiminer not saving the port number, so in every restart of guiminer port number have to be given again.
I mined only 30 minutes & got 2 blocks & my balance increased from 9 to 23. Since each block has 7 coins. So i hope i am mining correctly.
@Lolcust: Also please add in your signature in BOLD letters to update the config file with ntp=1 instead of ntp=0.
Many are still using old version & it takes me sometimes 1 or 2 attempts to restart GG to get no error/no ntp error in getinfo.
Its not due to not correctly pointing to bitcoin client.
Its for this reason config in bitcoin.conf
Code:
# rpcport will also be changed for namecoin here
rpcport=8777
noirc=0
dns=0
gen=0 I changed it to gen=1
On next release update gen=1.
Also i see a strange problem in guiminer. Even after configuring & SAVING & mining, restarting guiminer with quit changes the port back to 8332 in stead of 8777.
Seems guiminer not saving the port number, so in every restart of guiminer port number have to be given again.
I mined only 30 minutes & got 2 blocks & my balance increased from 9 to 23. Since each block has 7 coins. So i hope i am mining correctly.
@Lolcust: Also please add in your signature in BOLD letters to update the config file with ntp=1 instead of ntp=0.
Many are still using old version & it takes me sometimes 1 or 2 attempts to restart GG to get no error/no ntp error in getinfo.
Are you sure about the gen=1 ? It should run fine with "gen=0".
I thought "gen" is for CPU mining on the local machine, by the client itself.
But that doesn't give you much coins, CPU's are slow for mining...
Mine is running great now, after tons of trials and one change of computer 
. I think most of the problems should be due to firewall setting as for this computer, I just unpack and run and it is running perfectly.
. I think most of the problems should be due to firewall setting as for this computer, I just unpack and run and it is running perfectly.
I see a strange problem in guiminer. Even after configuring & SAVING & mining, restarting guiminer with quit changes the port back to 8332 in stead of 8777.
Seems guiminer not saving the port number, so in every restart of guiminer port number have to be given again.
I mined only 30 minutes & got 2 blocks & my balance increased from 9 to 23. Since each block has 7 coins. So i hope i am mining correctly.
@Lolcust: Also please add in your signature in BOLD letters to update the config file with ntp=1 instead of ntp=0.
Many are still using old version & it takes me sometimes 1 or 2 attempts to restart GG to get no error/no ntp error in getinfo.
Post edited.
Seems guiminer not saving the port number, so in every restart of guiminer port number have to be given again.
I mined only 30 minutes & got 2 blocks & my balance increased from 9 to 23. Since each block has 7 coins. So i hope i am mining correctly.
@Lolcust: Also please add in your signature in BOLD letters to update the config file with ntp=1 instead of ntp=0.
Many are still using old version & it takes me sometimes 1 or 2 attempts to restart GG to get no error/no ntp error in getinfo.
Post edited.
looks perfectly fine to me
Guiminer giving error.
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
Code:
2011-09-18 23:42:40: Running command: poclbm.exe --user=aa --pass=aa -o localhost -p 8777 --device=0 --platform=0 --verbose
2011-09-18 23:42:40: Listener for "Default" started
2011-09-18 23:42:42: Listener for "Default": 18/09/2011 23:42:42, Setting pool aa @ localhost:8777
2011-09-18 23:42:45: Listener for "Default": Wrong username or password
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
What's your hashing rate?
I hope this explains more
Guiminer giving error.
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
Code:
2011-09-18 23:42:40: Running command: poclbm.exe --user=aa --pass=aa -o localhost -p 8777 --device=0 --platform=0 --verbose
2011-09-18 23:42:40: Listener for "Default" started
2011-09-18 23:42:42: Listener for "Default": 18/09/2011 23:42:42, Setting pool aa @ localhost:8777
2011-09-18 23:42:45: Listener for "Default": Wrong username or password
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
What's your hashing rate?
Guiminer giving error.
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
Code:
2011-09-18 23:42:40: Running command: poclbm.exe --user=aa --pass=aa -o localhost -p 8777 --device=0 --platform=0 --verbose
2011-09-18 23:42:40: Listener for "Default" started
2011-09-18 23:42:42: Listener for "Default": 18/09/2011 23:42:42, Setting pool aa @ localhost:8777
2011-09-18 23:42:45: Listener for "Default": Wrong username or password
This is in bitcoin.cnf file in virtual_data folder
testnet_config=1
testnet=1
rpcpassword=aa
rpcuser=aa
printtoconsole=1
EDIT:
It mines now.
No need for server. Just solo, localhost, user, pass and port (8777), and GG application opened, of course.
Hm, the RPC error is quite bizzare - I successfully connect GUIminer "out of the zip" (though its option saving is apparently weird and I have to re-input port every time it restarts). Sent ya some geists
P.S.:
dishwara, seriously, open up them ports for them incoming connections
. That will make you and Geist Geld as a whole happier
dishwara, seriously, open up them ports for them incoming connections
. That will make you and Geist Geld as a whole happier Ports are open only. I think the problem is guiminer searching for bitcoin.exe.
For GG which is the client & server file to run to mine solo?
is it geistd.exe?
I think if it is then giving it in the guiminer "location of bitcoin client" solve RPC problem.
Yes, I tend to agree with your gut feel, will have to tweak that bit later on.
hmm, the "peers disagree with NTP" looks more and more like it can pretty much only be a bad ntp response:
Added time data, samples 17, offset -2 (+0 minutes)
-2 -2 -2 -1 -1 -1 -1 -1 -1 -1 -1 -1 +0 +0 +0 +0 +0 | nTimeOffset = -1 (+0 minutes)
This is on a box with ntpd synced to a local stratum1 where the current SNTP code consistently gets < 10ms offset to local time from all pool.ntp.org servers I tried.
The basic problem is... we can't trust the local clock to be accurate, and if median-of-peers and SNTP disagree by more than a few sec... which one is right?
Gut feeling says if peers and NTP disagree by too much preferring median-of-peers time and issuing a warning might be better, current code uses NTP time and issues a warning under those conditions.
Added time data, samples 17, offset -2 (+0 minutes)
-2 -2 -2 -1 -1 -1 -1 -1 -1 -1 -1 -1 +0 +0 +0 +0 +0 | nTimeOffset = -1 (+0 minutes)
This is on a box with ntpd synced to a local stratum1 where the current SNTP code consistently gets < 10ms offset to local time from all pool.ntp.org servers I tried.
The basic problem is... we can't trust the local clock to be accurate, and if median-of-peers and SNTP disagree by more than a few sec... which one is right?
Gut feeling says if peers and NTP disagree by too much preferring median-of-peers time and issuing a warning might be better, current code uses NTP time and issues a warning under those conditions.
Lolcust,
Can you tell me how to mine GG?
I have GUIMiner. What should I do? I am kinda of a newb! lol
Can you tell me how to mine GG?
I have GUIMiner. What should I do? I am kinda of a newb! lol
1) Please pretty please open incoming ports, seriously, moar listerners are needed
2) input the thing you have in your config after "username=" into username field (default is username)
3) input the thing you have in your config after "password=" into password field (default is password)
4) input 8777 into guiminer's port field
5) Start mining !
I collected some data on the difficulty that adjust ever few minutes. There are some duplicate values you can disregard them.
This is about 4 ro 6 hours of data:
41.32592058
53.03877464
73.57993070
73.57993070
73.57993070
49.74429527
51.01985208
57.21862978
57.21862978
56.05099627
48.21602856
75.14202535
75.14202535
71.00036395
61.73946964
61.73946964
58.56711479
58.56711479
49.14726638
72.36407710
64.32365492
64.32365492
50.78187382
50.78187382
44.64343971
57.91589282
52.65094384
52.65094384
45.29123383
79.92606214
80.26063120
80.26063120
56.48846120
72.49885485
72.49885485
49.57188487
49.57188487
44.55901687
58.75931634
64.98743013
64.98743013
72.89196305
72.89196305
72.89196305
49.69920313
55.47826432
61.35854439
61.35854439
57.52370111
61.35876880
61.35876880
37.95391768
60.72646061
60.72646061
49.91226583
54.44978872
56.08566147
56.08566147
83.60597408
82.91510781
82.91510781
59.57981164
58.36398172
58.36398172
64.55010658
70.41834735
70.41834735
48.70439667
46.02000230
70.80021269
70.80021269
78.66719809
78.66719809
44.52862239
44.52862239
54.24819652
71.53621804
79.85454130
79.85454130
59.70448399
54.90076476
54.90076476
59.62088744
48.17850528
48.17850528
55.32477040
49.17766378
49.17766378
87.79290099
87.79290099
71.66792685
71.66792685
55.12933754
82.69400631
82.69400631
75.46243737
54.71598303
54.71598303
This is about 4 ro 6 hours of data:
41.32592058
53.03877464
73.57993070
73.57993070
73.57993070
49.74429527
51.01985208
57.21862978
57.21862978
56.05099627
48.21602856
75.14202535
75.14202535
71.00036395
61.73946964
61.73946964
58.56711479
58.56711479
49.14726638
72.36407710
64.32365492
64.32365492
50.78187382
50.78187382
44.64343971
57.91589282
52.65094384
52.65094384
45.29123383
79.92606214
80.26063120
80.26063120
56.48846120
72.49885485
72.49885485
49.57188487
49.57188487
44.55901687
58.75931634
64.98743013
64.98743013
72.89196305
72.89196305
72.89196305
49.69920313
55.47826432
61.35854439
61.35854439
57.52370111
61.35876880
61.35876880
37.95391768
60.72646061
60.72646061
49.91226583
54.44978872
56.08566147
56.08566147
83.60597408
82.91510781
82.91510781
59.57981164
58.36398172
58.36398172
64.55010658
70.41834735
70.41834735
48.70439667
46.02000230
70.80021269
70.80021269
78.66719809
78.66719809
44.52862239
44.52862239
54.24819652
71.53621804
79.85454130
79.85454130
59.70448399
54.90076476
54.90076476
59.62088744
48.17850528
48.17850528
55.32477040
49.17766378
49.17766378
87.79290099
87.79290099
71.66792685
71.66792685
55.12933754
82.69400631
82.69400631
75.46243737
54.71598303
54.71598303
Lolcust,
Can you tell me how to mine GG?
I have GUIMiner. What should I do? I am kinda of a newb! lol
Can you tell me how to mine GG?
I have GUIMiner. What should I do? I am kinda of a newb! lol
I'm thinking based on how blocks are generated with large sums of GH that when a pool opens with enough firepower any solo mining with a few GH will likely be in vain.
Small solo miners will be forced to use a pool to get a small cut of the already small GG pie.
Interesting I think.
Small solo miners will be forced to use a pool to get a small cut of the already small GG pie.
Interesting I think.
Well, part of this effort is to establish how big can this pie grow (though, given how most of Bitcoin pie is run by, from Bitcoin Net's perspective, hundreds of nodes at most, it doesn't have to be able to grow very big to "live)
What is more concerning is that fast blocks radically affect some aspects of pool operations, which is where the curious stuff starts.
P.S.:
dishwara, seriously, open up them ports for them incoming connections
. That will make you and Geist Geld as a whole happier
I'm thinking based on how blocks are generated with large sums of GH that when a pool opens with enough firepower any solo mining with a few GH will likely be in vain.
Small solo miners will be forced to use a pool to get a small cut of the already small GG pie.
Interesting I think.
Small solo miners will be forced to use a pool to get a small cut of the already small GG pie.
Interesting I think.
Well, people get that occasionally. Still looking for a cause, but it usually goes away after client restart. Basically, either your NTP server is weird or we have a lot of people who never bothered with ntp=1 which could say scary things about the amount of attention people pay to this thing
Could also indicate you have connection issues, but so far no orphans were reported to be associated with this.
But, better safe than sorry, pls restart.
P.S.:
We will have a "pool friendly" version and a stable bootstrap node on tuesday. Also site.
Could also indicate you have connection issues, but so far no orphans were reported to be associated with this.
But, better safe than sorry, pls restart.
P.S.:
We will have a "pool friendly" version and a stable bootstrap node on tuesday. Also site.
Thanks, now i too have some GG.
9 GG.
Thanks.
Got new error. Marked in RED line
9 GG.
Thanks.
Got new error. Marked in RED line
Interesting fact - when connecting to any-coin through a kinky and weird router (D-Link DIR-615 Wireless N Router), I get no more than 12 connections if "Wan ping" is not allowed, much more if ping is allowed (in both cases, port is forwarded).
Curiously enough, uTorrent seems to give exactly zero rat asses and establishes a lot of incoming connections in both cases.
Curiously enough, uTorrent seems to give exactly zero rat asses and establishes a lot of incoming connections in both cases.
Jump to: