In theory it does not belong to an exchange unless the exchange purchased the coins. It might however be an account created in the exchange wallet by a user of the exchange. The answer to your question is in the taint analysis. Chainz is one of the best block explorers out there and provides lots of rich information for chain analysis. When coins move it leaves traces of information that can be analyzed. When coins are withdrawn from an exchange they do not necessarily come from the public key that the particular user created on the exchange. Coins during exchange withdrawals come from random public keys in the exchange wallet. This means that one withdrawal could come from multiple exchange accounts debited simultaneously. Interpretation of this means that the only way that accounts can be withdrawn from multiple accounts simultaneously is when all those accounts' private keys are controlled by the same entity. Over time all these traces can be put together and a picture starts to emerge of entities that control certain groups of accounts.

In this case if you go to the largest wallets tab you will see that the largest wallet according to taint analysis consist of 12 addresses with coins in them and 466 with zero balances. One entity therefore controls the private keys of 12 stocked accounts. This can be due to 2 reasons: Option 1) More often than not it is safe to say that a very lob-sided number of accounts in contrast to the others are addresses on an exchange. The address you mention forms part of the taint analysis of the 12 and my guess would be with this option that someone has stored 17.7m on an exchange to reduce admin later or to be able to move fast on a rainy day. Option 2) There might have been a skew initial coin distribution coupled with some creative accounting and sloppy coin movements by an individual. What does bother me in this case is that exchange account movements are normally more random but these accounts seem to have been moving through many accounts with more round numbers and blocks of thousands, which is not typical of an exchange. It could therefore be under this option that the top wallet is owned by one individual.

The way to find out which option it is, is easy. Each person that has an exchange account must look through the list of accounts linked to the large wallet and if you find it there, then the large wallet is an exchange account. If no-one can find his/her exchange account in the list, then it is an individual's account.

Nice, you figured out getinfo. Maybe say what your views or interpretation are as we can all do getinfo?

More important than the emission curve is that staking gets fixed so that staking can take over at the appropriate time. Since the dev said making a windows wallet is trivial, maybe fixing staking will be a more challenging task?

Difficulty took a loooong time to go up and still does. The high block count is from the ASICs that joined the mining when difficulty was low. The rate blocks are found should stabilize over time as mining power and difficulty get into equilibrium.

I would recommend that the dev fix the staking first before making a windows wallet.

With the console wallet you go to the directory where the executable file is and 1) if your wallet is encrypted type "./bitgrowd walletpassphrase yourwalletpassword 99999999 true" and press enter or 2) if your wallet is not encrypted just run the executable with ./bitgrowd and press enter.

In your ~/.bitgrow folder put the bitgrow.conf file and in it put the items below replacing the italics descriptions with actual data:
rpcuser = choose_a_username
rpcpassword = choose_a_password
rpcallowip = 127.0.0.1
server=1
listen=1
daemon=1
addnode=add_some_nodes_here

Staking still seems to be down. Several wallets are still on 0.1.1.2/3.

While it is really entertaining to watch you two fight like school children I do have a question to SockP.

It is a well known fact that in crypto launches that the early bird catches the worm. Why do you not like others watch the boards and spend the extra time to see a launch and then quickly compile and jump in? (Perhaps you do and something just went wrong here which sometimes do happen e.g. you cannot get a miner hooked up quickly enough) The hard workers and the lucky ones that spend the time and spam F5 are rewarded in the end. Sometimes one goes to sleep and wakes up to a launch that is already well down the line and you lose out. Other times you see a fresh launch just as you refresh your browser. Sometimes you win and sometimes you lose.

People know what they get into with alt-coins and 99.99999% of coins get into a dumping situation and 99.99999% of devs disappear. Whether it is ethically right or wrong, that is the reality. There will never ever be something like a fair launch as there are always someone that needs to mine the early coins and whether it is the dev or someone else, do you expect anything else than a dump? Have that as your going in position in alt-coins and if it does not happen it is a bonus.

I like to watch the emission curves and play the dynamics of some coins' mining for entertainment and/or educational value except in one or two cases where I strongly believe in the cause.

Getblockhash 33426 0000000000121a1b7a82dfdb64882677a19c0642f42a6e99e8bcae09a16250a4

 "moneysupply" : 486586.62

EDIT: The source on Github is the latest version. Just clone the link as per OP.

Not a bad idea.

435558 so far but their might be more than one fork. Although I think latest update fixed that.

But honestly, on a more serious note, why should one do things like maintaining a chain, posting a chain, keeping it ticking over getting coins out of maintenance etc. if no-one cares and the only post is when someone complains that the chain is stuck or the wallet is in maintenance?

I have to point out that you have a valid point there that things are pointless and that is exactly my point.

It is getting really annoying. It is one thing to give support to an active dev but it is a different matter to give support to a dev that is missing in action. Getting to the point of what is the point?

Maybe the pack forked away from Yobit. It looks like when there is not movement on the chain for a while on Yobit wallets it first says "delayed" and then after a while "in maintenance". When the chain moves again then the wallet goes out of maintenance again. it can also happen that they manually put a chain in maintenance to free up resources then a chain move will make no difference. Only way to check which one it is is to do a re-sync to Yobit and let that chain move again to see if it goes out of maintenance.

Ill make a Pi Pi wallet.

To make money they have to do good investments first that generate profits and dividends. Only after that has realised can the underlying value increase. Before actual realization of investment profits and dividends the investment scheme is still a house of cards. One could take a chance on potential but the proof is in the eating.

Show me the money first.

Which coin will you use as base? Quark would be nice for an algo.

Here is a link to the Yobit chain. These files will sync you up (almost) instantly.

Procedure:
1. Make backup of your current .loco or roaming\Loco folders including your old wallet.dat file
2. Cleanout the folder so that you have an empty .loco or roaming\Loco folder
3. Put back the loco.conf file making sure that you have the right nodes in it as per below
4. Unzip the loco.zip file to the root of the .loco or roaming\Loco folder
5. Run the wallet and it will take you to the point when the chain was copied and sync the rest quickly

You will notice that you have an empty wallet. You can now do one of 2 things to recover your coins you might still have on the Yobit fork of the chain:
1. Copy your old wallet.dat to the folder where your loco.conf file is and run the wallet. The results are however unpredictable as you might have transactions from your other fork in the wallet.dat and it could cause conflicts or orphans etc.
2. Dump the private keys of your old wallet.dat before you cleanout the folder and import them into your new synced up empty wallet. You can do this either with the command "dumpwallet keys.txt" and then "importwallet keys.txt" or "dumpprivkey <public key>" and "importprivkey <private key>". If you dump the whole wallet the file will be in the folder where your wallet executable was executed from. In all cases it will tkae a while to trawl through the chain to update your balances.

NB:
Take note that with Loco on Windows/Linux you might have to kill the Loco process after exiting the wallet or rebooting afterwards to re-launch the wallet.

The nodes you have to use in your loco.conf are the following:
addnode = 5.189.189.51
addnode = 45.32.41.132

I will be posting the Yobit chain shortly that will bring you up to date instantly. It makes sense to align with the chain the exchange is on.

Ill post the Yobit chain later today with instructions of how to get aligned.