Thanks Piotr_n. That's very helpful!

BTW, the latest version of wallet also supports Litecoin (add -ltc switch)
The client node does not, but you can fetch balance of your Litecoin addresses from http://ltc.blockr.io using tool/balio
Then broadcast a signed transaction to Litecoin network using this page: http://ltc.blockr.io/tx/push (or the official litecoin's client sendrawtransaction RPC).

---

From other useful changes in the wallet, now you can just do:
.. to sign all the multisig inputs that the current wallet knows keys for. (previously you had to specify a specific signing address with "-msign")

Update on the development.

I had said to myself that after I would have the current code running without any changes for like 2 weeks, then I would tag it as 1.0
And the problem is that I apparently don't have a patience for it - 2 weeks is just too long for me to not touch a code
So now I am already on 1.0.0-RC8, and again the code was hugely remade.

In rc8 I changed the format of UTXO database. Now it is kept in "gocoin/btcnet/unspent4/", while the old one was in unspent3.
The new format allowed me to further simplify the architecture, but also performs significantly better (e.g. the node starts faster).
But the most important thing is that it decreased memory consumption, from far over 2GB to slightly over 1GB. But it still does not work on 32-bit arch (too little memory space for Go framework, I guess).
Additionally the size of unspent4 folder is significantly lower, comparing to its predecessor.

I developed this version on a branch, because the new database format means that the node needs to rebuild the UTXO at the first launch.
It may take up to an hour, so I did not want to annoy anyone, especially when it wasn't all complete and stable yet.

But the current version seems to have all the old full functionality already.
If anyone would like to try it before I get to merge it with the master, to checkout the branch:
...and then rebuild your binaries.

Any feedback welcome.

Oh, and there were plenty of changes since my last announcement on 0.9.13, though mostly of architecture performance matter.
Not much visible on a user interface level, but really plenty of good stuff. As usually you can find a more detailed list in changelog.txt

Also, if you run it for the first time and have no fresh bitcoind to import your blocks from, make sure to try the downloader.
On my few yrs old i5 desktop PC, with 50Mb downlink, it fetches the current block chain (while building UTXO database) in about 90 minutes.
For comparison: on the same PC, bitcoin-qt needs like 6 hours to just re-index the chainstate (having the blocks on disk already).

sure - it's always worth trying.
let me know if you needed any help.
and also how it went.

all I can say about 32-bit "incompatibility" is that when I build the node with 32-bit compiler and run it on my 64 bit windows, it crashes after awhile complaining something about memory allocation error.
but it does not seem to take more than 2GB of the system memory at any time, so that's kind of weird.
it may be only happening on windows - worth trying at a different OS.

also, in the testnet mode, it should work just fine on 32 bit OS.
the database isn't so big yet.
but who needs testnet mode for anything except testing.

FYI, few days ago, after a longer period of testing, I released Gocoin version 1.0.0.

I have built binaries of this release for Windows and Linux. You can download them from here: https://sourceforge.net/projects/gocoin/files/?source=directory
Inside each archive there is a file with SHA-256 sums, signed with my bitcoin-otc PGP key.

The Linux execs require 64 bit OS.
Windows binaries require 64-bit platform for downloader in client, but the wallet and balio apps will also work on 32 bit systems.
If you need a binary for any other platform (OSX, FreeBSD, Linux i386, Linux ARM), let me know - I can build it for you.

When launching the client make sure to have the www/ folder in the place (it contains the WebUI app).

For the wallet there is an example config file (with all the config parameters are commented out).

Don't hesitate to give me a shout, if you'd experience any issues: tonikt@assets-otc.com

sure I can.
the problem is that testing this would be very time consuming, so I am not very keen to start working on it, considering that it'd take lot of my time giving me back nothing I need myself.

but I will keep your request in mind and see what I can do.
cheers

I need the bootstrap.dat function for creating my personal blockchian backups i'll really appreciate if you add this function.
Anyway i think the downloader needs a tweak because it uses way to much ram in my machine windows 7 64bits 4gb ram it makes the pc slow when the ram usage comes to 90%/95% . anyway the cpu usage is fine it's just 10%. (And yes i've compiled using the gcc in go)
Thanks in Advance

Ok thanks for helping me !
I'll checkout the tool and i let you know if there are problems.
i'll also check the ram settings. 

The default type 3 is my own schema. It goes like this:


Type 1 and 2 are also my own schemas, though they use different algos.