Betacoin on the way...
lol, gamma coin is in the planning 
yes but to mine the gamma coin you must live in the gamma quadrant!
I agree
Topic: Alphacoin - the new innovative alt coin! | Version 1.1 released, please update! - page 21. (Read 117005 times)
June 21, 2013, 10:22:59 PM
yes but to mine the gamma coin you must live in the gamma quadrant!
I agree
June 21, 2013, 07:53:13 PM
Betacoin on the way...
lol, gamma coin is in the planning yes but to mine the gamma coin you must live in the gamma quadrant!
June 21, 2013, 06:33:41 PM
Betacoin on the way...
lol, gamma coin is in the planning June 21, 2013, 03:36:27 PM
Betacoin on the way...
lol, gamma coin is in the planning legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
June 21, 2013, 03:22:57 PM
Betacoin on the way...
June 21, 2013, 03:13:22 PM
Nice I have no problem of syncing. But sometimes I also see this Litecoin chain, it's annoying though it does not really matter, as the sync can not be completed due to checkpoints. But many alt coins have this issue. Someone pointed out the reason could be that these coins did not change the script pub key in the code.
June 21, 2013, 03:12:15 PM
Any selling/buying action ongoing? Links?
June 21, 2013, 01:09:47 PM
yup
June 21, 2013, 11:58:04 AM
I am having no problem to sync.
I have no problem to sync too. Not seem to have another fork there (though sometimes I see it try to sync with Litecoin chain, but several coins have that problem). 
June 21, 2013, 01:02:32 AM
I am having no problem to sync.
June 20, 2013, 10:19:43 PM
June 20, 2013, 06:17:28 PM
Thanks guys
June 20, 2013, 06:10:27 PM
err..we got a fork happening here guys? Ive got 2 rigs mining this atm:
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
The rig 2 is in the process of sync'ing, once all sync'ed up, you should see the same thing. Clearly it is not sync'd up. You see the status of those blocks that sync'ed only.
June 20, 2013, 05:56:54 PM
Check your rig 2 settings, that is the wrong one. You probably need to restart rig 2. Is it actually solving blocks?
June 20, 2013, 04:11:14 PM
err..we got a fork happening here guys? Ive got 2 rigs mining this atm:
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
Yah somthings up
June 20, 2013, 02:19:09 PM
err..we got a fork happening here guys? Ive got 2 rigs mining this atm:
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
Rig 1:
04:47:55

getmininginfo
04:47:55

{
"blocks" : 26961,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02508189,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 3384060,
"pooledtx" : 0,
"testnet" : false
}
Rig 2:
04:47:46

getmininginfo
04:47:46

{
"blocks" : 20531,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03528376,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 90507,
"pooledtx" : 0,
"testnet" : false
}
June 20, 2013, 02:04:46 PM
My client isn't progressing on synchronizing :/
I have no sync problem June 20, 2013, 11:32:02 AM
My client isn't progressing on synchronizing :/
June 20, 2013, 12:13:26 AM
Just though i would post this... i don't know why... proof its working?
June 19, 2013, 11:53:31 PM
ALF coin? 
sorry couldnt resist
sorry couldnt resistYes, this has been punned numerous times xD
Jump to: