Merge remote branch 'yacoin/testing' into testing
Deleted yacoin-qt executable
Merge remote branch 'yacoin/testing' into testing
Merge pull request #48 from grokouser/updateOpenSSL

Update open ssl md5sum
Merge pull request #50 from yacoin/master

Sync testing.
Testing 0.4.4
Testing 0.4.4
So we know we're on testing...
Update version.h
Testing 0.4.4
Merge remote-tracking branch 'yacoin/testing' into testing
Merge branch 'testing' of https://github.com/grokouser/yacoin into testing
POS checkbox signal handler compatibility; closes yacoin/yacoin#53
Merge pull request #55 from grokouser/testing

Balance Column and rescan revamp
Merge pull request #54 from saironiq/master

POS checkbox signal handler compatibility
Merge pull request #56 from yacoin/master

Bring in saironiq changes to testing.
Per user request, make stake minting a little clearer.
show library versions, moving wallets, live splash screen

All of these 044 changes can be see in this video:
http://youtu.be/C8GvHpjbAnM
which was done to the 043 code. In addition:
In YACoin.conf (or on the command line) for Windows (#ifdef WIN32)
versions of YACoind (MS), YACoind (gcc) & YACoin-qt (gcc) there is a new
walletpath argument.

walletpath can take a full or partial path (or just a filename) to an
existing 'wallet.dat' file or a non-existing name to create a new wallet
with that new name.  If it's a partial path or just a name, the code
'falls back' to using datadir to compose the full path, which is what
the normal code does anyway.

The 'wallet.dat' name can be any legal filename!

The kinds of things one can do with this capability are: Run the wallet
off of a USB memory drive and never have it on the hard drive of the
computer!

Change wallets by editing a line in YACoin.conf, without losing the
other wallet, which is the same as running the same blockchain with
different wallets.

Perhaps an odd use of running the same wallet on different blockchains?

All one needs to know is how the BerkeleyDB code is written in
Bitcoin/YACoin, etc.

In YACoin, the wallet code expects a blkindex.dat and (possibly) a
database/log.0000000nnn file in the directory with the wallet file,
'wallet.dat' or whatever you want to rename it!

The blockchain, I think, is in the datadir directory, wherever that is
on your computer, and it expects to find a blk0001.dat and perhaps a
peers.dat and the ability to have a .lock file.

There is some connection, I believe, but again there is no
documentation, on the relationship between the 'datadir'/blk001.dat file
and the blkindex.dat and (possibly) a database/log.0000000nnn files in
the walletpath which now can be a separate directory!

Ron
POS Minting and Combine update. Split is no more.

POS minting is in need of an update. In order for YACoin
to maintain confidence of it's users, we must adapt to the
higher N values (now 15). The problem is that our core
holders of YACoin have difficulty managing their coin inputs
as their numbers grow. Chunks of coin get split up into
tiny insignificant pieces, and the client doesn't have time
to check each input for POS block creation. Coins pile up
longer then 90 days before they get interest awarded. This
is a huge problem, as it makes YACoin fail to deliver on the
promise of 5% interest on coins kept between 30 and 90 days.

The old rules were designed for a paradigm that no longer
exists for YACoin. POS blocks are no longer expected to
completely replace POW blocks in some utopia of energy
efficiency. There is no longer any need to split coins into
tiny pieces in order to generate large numbers of POS blocks
in order to "secure the network".

To address this issue, new rules are presented that change
how coins are managed when POS blocks are minted. First of
all, splitting is out. Nobody really needs or wants their
coins to be split up. If they do, they can split them up
themselves any way they wish using Coin Control. Second, the
combine feature will be boosted greatly. Instead of waiting
90 days for a coin input to be eligible for combining, only
31 days will do. And instead of the combine limit being POW
reward divided by 3, (which is about 16 now), the combine
limit is set to POW reward times 10 (around 550 at the
moment). These new rules should lighten the load for clients
performing POS minting by about 100X. And small chunks of
coin (including new POW minted coins) will be awarded their
5% much sooner after the 30 day waiting period as they get
sucked up by other POS blocks.

It should be noted that these new "rules" are completely
arbitrary and have no effect on block validity. Anybody who
can build their own client can change these numbers at will
without loosing their coins or getting their POS blocks
rejected. And the "secure the network" thing is ancient
history.
Merge pull request #60 from ya1-old-c-coder/testing

show library versions, moving wallets, live splash screen