Backup your wallet.dat then in the client go to Debug -> Console -> Type in


Hit enter.

I fully understand your frustration there, Press.

To Saros: Not sure where you have been, but the HyperStake community has been very responsive since the day the coin launched. Presstab and I met when he was on the TEK development team, and he was always quick to answer then, too. Generally tried to lead me to the solution by logic to make me learn, which some days was irritating, but in the long term I am grateful for this. From him, and a few others, I have learned enough that I COULD create a clone coin. I have no real inclination to do so, but considering where I started, that's something.

Yes, a LOT of alts have been hyped up for a little while and abandoned. This one is NOT one of those. We're a very active community.

As far as I can recollect, there were no issues with the wallet code from the very first weeks of deployment. All concerns that were aroused laid in the field of the API usage, not the code itself.

Today is a good day as I am now a HYPillionaire! I have made it to the big show. Woot woot to me! Thanks Press.

Awesome accomplishment! I extend my welcome as well.

Lol @presstab

I have decided to make my new in wallet block explorer open source

I am working on the final polish still. I am thinking about releasing a closed source compiled beta for those willing to test. After that I plan on making it as clean of a commit as possible, because I would like it to be easily used by the crypto community if they want it.

So look for a test wallet in the next few days.. hopefully

I have never been able to get static linux binaries to work. So yes.

Yes sir. A real explorer, not a crawler like most other coins have. It is all rpc based at the moment of course, but its more about the code behind it and the DB, not about making it flashy.

Basically how my explorer code functions:
- scan block for all tx's held by the block
- scan each transaction id and create a "transaction summary" for each address in that txid. each txsum has a blockfrom, deposit, withdraw, minted, and mined variables that are filled in.
- insert each txsum object into an array that is tracked per address
- keep a record of every address seen and update its balance, minted total, mined total each time it is seen, store this in Richlist db

These basic things allow for us to query any address, which will bring up the vector of txsums for that address. With this vector you can quickly find a balance by adding all the withdraw and deposits in each txsum, or you can print out a list of transaction id's for that address.

We can also bring up our richlist that is a simple group of every address with its current balance, amount mined, and amount minted.

So my code is built from the ground up, it doesn't even use the txindex=1 functionality. And it provides full address querying without having to dig through the chain each time you query that address. Of course I would love to add even more functionality over time too.

This is made for HYP, but I would like to make it neat on github so other coins can easily cherry pick it if they want. Can you imagine a crypto world where you can get all the info you need from your wallet? No checking websites. If you think your richlist/balances are wrong just hit reindex, or ask a friend what their wallet says. It seems like this is how wallet clients should have been all along.

crawlers just give you information on a transaction hash or a block hash. They don't keep track of addresses at all. So there is really no way of getting an address balance from a crawler, let alone a rich list. If crawlers and default wallets had this capability, then there wouldn't be much reason for a website with a block explorer, other than for public reference to check you are on the correct chain.

Sipa answers this in depth here if you are interested: http://bitcoin.stackexchange.com/questions/10090/how-to-get-an-addresss-balance-with-the-bitcoin-client/10101#10101

You can grab it cheap on POLO right now. I'm scooping it up.