Do we have a block explorer up and running yet ?
Three pools are reporting are reporting three different current block heights - obviously two of them are wrong.
Topic: [ANN] AIRcoin - page 96. (Read 137265 times)
{
"blocks" : 9180,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 1.52783606,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 31497504,
"pooledtx" : 0,
"testnet" : false
}
"blocks" : 9180,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 1.52783606,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 31497504,
"pooledtx" : 0,
"testnet" : false
}
OK,
I got my pool back up on the new wallet. Waiting to see if I get the confirms after KGW. Looks like my pool is at about 10% of network.
I got my pool back up on the new wallet. Waiting to see if I get the confirms after KGW. Looks like my pool is at about 10% of network.
Pity the pool is working fine again
We are only at 9046... not at the point of Gravity-well yet... You guys must-of forked...
Stop mining for about 30 minutes... it should reconnect at that point... once we get past your block...
Too much hashing power on your pool, I assume...
Stop mining for about 30 minutes... it should reconnect at that point... once we get past your block...
Too much hashing power on your pool, I assume...
what are dependencies to build from source
GUYS!!!! PROBLEM WITH THE PITY POOL
http://scr.hu/1ame/swo9d
rejected all shares after KGW
do you have the same or I`m special?
or there is a fork on the pity?
http://scr.hu/1ame/uyx56
http://scr.hu/1ame/swo9d
rejected all shares after KGW
do you have the same or I`m special?
or there is a fork on the pity?
http://scr.hu/1ame/uyx56
Same problem here
GUYS!!!! PROBLEM WITH THE PITY POOL
http://scr.hu/1ame/swo9d
rejected all shares after KGW
do you have the same or I`m special?
or there is a fork on the pity?
http://scr.hu/1ame/uyx56
btw. can`t even mine solo
http://scr.hu/1ame/swo9d
rejected all shares after KGW
do you have the same or I`m special?
or there is a fork on the pity?
http://scr.hu/1ame/uyx56
btw. can`t even mine solo
ultra slow release with a huge premine (considering) to get high prices from beginning and dump. I smell the mega scam.
Wallet update thread created: https://bitcointalksearch.org/topic/m.5422246
Put a link-back to this thread, for the wandering souls with millions of coin questions... With the title listed too, so they know where they are going.
Could also put a link on the wallet page, of the website, for people there to come to this forum for wallet help. (As well as a link to your own forums duplicate posting.)
Shouldn't need more than that, for alternate links.
3 blocks to KGW 
103 blocks, actually (102 now). It kicks in on block 9108.
Hashrates are back to over 100 MH/s as a result.
Ahhh iI was sure
@ 9008 ) 3 blocks to KGW
103 blocks, actually (102 now). It kicks in on block 9108.
Hashrates are back to over 100 MH/s as a result.
3 blocks to KGW
One is linux-compile, one is windows-compile?
There are two separate compiles, they both came from the same code though. When did you compile Mortimer?
EDIT: I see you may have downloaded the Source almost as soon it came out to about 2 hours after. As long as your checkpoints.cpp file has checkpoints every 1000 blocks till 8000 blocks, and you have the Kimoto gravity well enabled (in main.cpp, do a quick search for Kimoto and/or gravity should be starting at line 1174), and your main.cpp has the following starting at line 921:
Code:
int CMerkleTx::GetBlocksToMaturity() const
{
if (!IsCoinBase())
return 0;
return max(0, (COINBASE_MATURITY+17) - GetDepthInMainChain());
You should be fine, regardless of what the wallet version says.
I downloaded the source shortly after the post from you.
In the future - I think a better idea would be to simply make sure the master branch is updated with the proper code and incremented version number. Incrementing the version number on *every* new release should be standard practice, no matter how small or large the changes are, so pool operators, exchanges and others can easily confirm they are running on the new code base before a fork. The last thing I want is to find out my pool has been stuck on the wrong chain for 10 hours.
Wallet update thread created: https://bitcointalksearch.org/topic/m.5422246
New Pool added to the main page (The NEW Pool) http://air.okaypool.com/
New Pool added to the main page (The NEW Pool) http://air.okaypool.com/
That video is amazing.
Solowheel wow!
Yes it`s cool, to move in the city its ok 10km on one battery cahrging.... prefer to walk for a while
That video is amazing.
Solowheel wow!
One is linux-compile, one is windows-compile?
There are two separate compiles, they both came from the same code though. When did you compile Mortimer?
It was yesterday, 14:58 CST Feb 27 (about 12 hours ago)
Ah, that was before AIRcoin Aether announced the official wallet update. According to Aether's post, the earliest the newest wallet was available was about 7/8 hours ago. I think you may have grabbed the version I was pushing onto Github before dealing with the syncing issues. We will work on making the "OFFICIAL Mandatory Update!" posts clearer. As long as you have the changes outlined in my last reply before yours, you are still ok.
EDIT: As long as you have those features and the wallet FULLY SYNCS.
One is linux-compile, one is windows-compile?
There are two separate compiles, they both came from the same code though. When did you compile Mortimer?
It was yesterday, 14:58 CST Feb 27 (about 12 hours ago)
One is linux-compile, one is windows-compile?
There are two separate compiles, they both came from the same code though. When did you compile Mortimer?
EDIT: I see you may have downloaded the Source almost as soon it came out to about 2 hours after. As long as your checkpoints.cpp file has checkpoints every 1000 blocks till 8000 blocks, and you have the Kimoto gravity well enabled (in main.cpp, do a quick search for Kimoto and/or gravity should be starting at line 1174), and your main.cpp has the following starting at line 921:
Code:
int CMerkleTx::GetBlocksToMaturity() const
{
if (!IsCoinBase())
return 0;
return max(0, (COINBASE_MATURITY+17) - GetDepthInMainChain());
You should be fine, regardless of what the wallet version says.
Jump to: