[ANN] AIRcoin

[luckygenough56]

ultra slow release with a huge premine (considering) to get high prices from beginning and dump. I smell the mega scam.

[splawik21]

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

[LeFiste]

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

Same problem here

[whoiis]

what are dependencies to build from source

[ISAWHIM]

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...

[LeFiste]

Pity the pool is working fine again

[Sprite160]

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.
 

[Shadow_Runner]

{
"blocks" : 9180,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 1.52783606,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 31497504,
"pooledtx" : 0,
"testnet" : false
}

[Mortimer452]

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.

[ISAWHIM]

I am at 9182 diff about 100k in cgminer (1.52587890625)

8 connections, seems like it is appropriate with the rest of the hash-power for the majority. If your diff os lower, you are on the wrong chain with fewer people... delete the block-chain and peer-info and let it download again, finding the new connections.

[Mortimer452]

I am at 9182 diff about 100k in cgminer (1.52587890625)

8 connections, seems like it is appropriate with the rest of the hash-power for the majority. If your diff os lower, you are on the wrong chain with fewer people... delete the block-chain and peer-info and let it download again, finding the new connections.

Yep, tried the above, but now I'm not syncing.  Do we have any stable nodes other than what's listed in the OP?

Also, what is the version reported by getinfo with your client?  I seem to be the only person with 080701

*Edit*
Yeah, I'm guessing the version# is definitely the problem.  Devs posted new version is 080701 but I seem to be the only person whose client actually reports version 080701, current Github source and binaries all still say 080602 even though the code is really 080701.

[splawik21]

I am at 9182 diff about 100k in cgminer (1.52587890625)

8 connections, seems like it is appropriate with the rest of the hash-power for the majority. If your diff os lower, you are on the wrong chain with fewer people... delete the block-chain and peer-info and let it download again, finding the new connections.

Yep, tried the above, but now I'm not syncing.  Do we have any stable nodes other than what's listed in the OP?

Also, what is the version reported by getinfo with your client?  I seem to be the only person with 080701

*Edit*
Yeah, I'm guessing the version# is definitely the problem.  Devs posted new version is 080701 but I seem to be the only person whose client actually reports version 080701, current Github source and binaries all still say 080602 even though the code is really 080701.

so how can we go forward now?

new wallet downloaded few minutes ago, the wallet does not open and get in tilt.

EXTRA

[Mortimer452]

I am at 9182 diff about 100k in cgminer (1.52587890625)

8 connections, seems like it is appropriate with the rest of the hash-power for the majority. If your diff os lower, you are on the wrong chain with fewer people... delete the block-chain and peer-info and let it download again, finding the new connections.

Yep, tried the above, but now I'm not syncing.  Do we have any stable nodes other than what's listed in the OP?

Also, what is the version reported by getinfo with your client?  I seem to be the only person with 080701

*Edit*
Yeah, I'm guessing the version# is definitely the problem.  Devs posted new version is 080701 but I seem to be the only person whose client actually reports version 080701, current Github source and binaries all still say 080602 even though the code is really 080701.

so how can we go forward now?

We need to wait for devs to chime in and figure out WTF is going on.  The QT on mydesktop shows v 080602 as well, and is currently at block 9210 which seems right.

I just recompiled GitHub source (which also still shows 080602 even though all comments say it should be 080701) and now I'm getting an error when trying to run aircoind:

Code:

aircoind: main.cpp:2923: bool InitBlockIndex(): Assertion `block.GetHash() == hashGenesisBlock' failed.

[Mortimer452]

OK - I'm sync'd and on what I think is the correct chain now (of course we cannot know this without an official block explorer)

Error above was due to a goof in the .conf file on my part

http://air.pitythepool.com up and running again

On a side note, this update release was a train wreck - client still reports version 080602

[Shadow_Runner]

9216 block in my wallet.

[AIRCOINDEV O]

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.

Mortimer, if you have changes outlined here and your wallet syncs, it shouldn't matter whether your version is 0.8.6.2-KGW or 0.8.7.1-KGW.  Everyone else should still be on 0.8.6.2 still if they downloaded the wallet AFTER AIRcoin Aether's post about the features of the new wallet.  If you downloaded source before that from Github, you will have a different version number.  This is why "UPDATE NOW" posts will be clearer in the future (sorry about that), so everyone knows when we are telling them to update from when we are talking about a wallet update in progress.  

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.

A block explorer is in the works, but is not ready for release yet.  We are working on it though!

[AIRCOINDEV O]

I am at 9182 diff about 100k in cgminer (1.52587890625)

8 connections, seems like it is appropriate with the rest of the hash-power for the majority. If your diff os lower, you are on the wrong chain with fewer people... delete the block-chain and peer-info and let it download again, finding the new connections.

Yep, tried the above, but now I'm not syncing.  Do we have any stable nodes other than what's listed in the OP?

Also, what is the version reported by getinfo with your client?  I seem to be the only person with 080701

*Edit*
Yeah, I'm guessing the version# is definitely the problem.  Devs posted new version is 080701 but I seem to be the only person whose client actually reports version 080701, current Github source and binaries all still say 080602 even though the code is really 080701.

so how can we go forward now?

new wallet downloaded few minutes ago, the wallet does not open and get in tilt.

EXTRA

If your wallet is still not syncing, as ISAWHIM suggested, please close the daemon or AIRcoin-qt.exe, delete the "blocks" and "chainstate" folders, and the "db.log" in your AppData/Roaming/AIRcoin folder, then restart the daemon or AIRcoin-qt.exe and wait for the wallet to sync.  If it still refuses to sync after that (it should be syncing) then close down the daemon or qt.exe and check to make sure your AIRcoin.conf matches the example on the topic page.  If it doesn't, please edit it, save it, and restart the daemon or qt.exe version of the client.  If it does, please redownload the wallet and try the above steps again.  For further assistance, please PM me or any other developer.    

[Mortimer452]

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.

Mortimer, if you have changes outlined here and your wallet syncs, it doesn't matter whether your version is 0.8.6.2-KGW or 0.8.7.1-KGW.  Everyone else should still be on 0.8.6.2 still if they downloaded the wallet AFTER AIRcoin Aether's post about the features of the new wallet.  If you downloaded source before that from Github, you will have a different version number.  This is why "UPDATE NOW" posts will be clearer in the future (sorry about that), so everyone knows when we are telling them to update from when we are talking about a wallet update in progress.  

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.

A block explorer is in the works, but is not ready for release yet.  We are working on it though!

I beg to differ, I believe the version number absolutely DOES matter.  If you make an announcement about new wallet version 8.7.1, the new wallet should report that version# when checked with getinfo.  That is how we know we are running on the correct version.

Version number is VERY important to proper synchronization of the blockchain.  If my client is reporting 8.7.1 and the majority of the network is on 8.6.2 my wallet will not synchronize.  This is how forks occur, when too many people are running the wrong version client.  It doesn't matter whether my main.cpp has the right code in it or not.  Version, as in version reported by the client regardless of what source code was compiled.  

Telling people that their 8.6.2 wallet is "really 8.7.1 even though that's not what it says" is plain messed up.

[AIRcoin]

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.

Mortimer, if you have changes outlined here and your wallet syncs, it doesn't matter whether your version is 0.8.6.2-KGW or 0.8.7.1-KGW.  Everyone else should still be on 0.8.6.2 still if they downloaded the wallet AFTER AIRcoin Aether's post about the features of the new wallet.  If you downloaded source before that from Github, you will have a different version number.  This is why "UPDATE NOW" posts will be clearer in the future (sorry about that), so everyone knows when we are telling them to update from when we are talking about a wallet update in progress.  

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.

A block explorer is in the works, but is not ready for release yet.  We are working on it though!

I beg to differ, I believe the version number absolutely DOES matter.  If you make an announcement about new wallet version 8.7.1, the new wallet should report that version# when checked with getinfo.  That is how we know we are running on the correct version.

Version number is VERY important to proper synchronization of the blockchain.  If my client is reporting 8.7.1 and the majority of the network is on 8.6.2 my wallet will not synchronize.  This is how forks occur, when too many people are running the wrong version client.  It doesn't matter whether my main.cpp has the right code in it or not.  Version, as in version reported by the client regardless of what source code was compiled.  

Telling people that their 8.6.2 wallet is "really 8.7.1 even though that's not what it says" is plain messed up.

Mortimer is completely correct and this is a sentiment I have expressed repeatedly to AIRcoin Dev O. Our programmers were given free reign to release a new wallet on their own, but did not meet yours and (infinitely higher) my standards. From here on out, I will be overseeing the releases personally and you can trust that the developer(s) in question who allowed this release to become this confusing will dealt with accordingly.

Whether it works or not isn't the goal, that's the requirement. Our goal is to make things smooth, professional, and clean, something this wallet release was not. You can leave it to me to sit down with the developers and identify how we need to alter our team in order to proceed according to our plan. After I debrief the team to identify the exact sequence of events, I will release a statement to all of you that explains exactly what happened. For now, there is adequate information to make sure your wallets are up to date, but it is likely we will release a refresh version that displays the complete version on equal terms for all users.

For now, I recommend that users recompile from the github or re-download from our site and delete the blocks, chainstate, and db.log folder to re-sync your wallets if you have any further concerns about the version number. They should ALL say 8.6.2 now. If you have zip files or folders named 8.7.1, use getinfo, and you should see 8.6.2 on all versions currently available for download. Let me know if this is not the case, as I am still digging through what our team exactly did wrong.

AIRcoin Dev O is our general development account, but it is primarily used by one of our programmers. As the manager behind this update, has been removed from his position.

I will make sure not only that this doesn't happen again, but that there is just response to those who let it happen.

- Alexander

[ISAWHIM]

Website still says version 0.8.1 (above the wallet selection links) {consumer downloads}

Windows link is for "AIRcoin-v0.8.7.1_KGW.zip" <-- Correct file
Linux link is for "AIRcoin-v0.8.7.1_KGW_Linux.zip" <-- Correct file

Actual Internal windows version# v0.8.6.2-gda10b75-beta
Actual Internal linux version# v? <-- Anyone have this number from the latest download?

Wallet reporting block 9278 at the moment. Diff 96.1K (1.46636962890625 Diff) 14 connections.

P.S. Nice smooth Gravity-well results... Easy to see hash-rate of network with the diff-change now. Value will be easy to gauge once this hits an exchange. (No having to guess and calculate for 24-hours.)

P.P.S. Don't be too hard on the devs... that was a MAJOR change to the code. Which they rolled-out rather fast, and smoothly... regardless.