Sorry to see you go. How is that possible? Did you overwrote your wallet file? It is wise to have a backup of wallet file and keys, we even have paperwalett. I can do nothing more to prevent such things.

We indeed have child pains, and problems which need to be fixed and we're working on it.

For miners, please switch to http://democats.org/pool/?name=karbowanec while we're investigating issues with pool.karbowanec.com

It happened because  your wallet doesn't create a default wallet.
I was using the Windows x64 version.

your wallet by default does create a recieve hash and private key hash; however, it doesn't create a .wallet or . keys file.
Not really sure what you're telling me to have backed up since I had nothing to start with.

Also as I posted before the wallet needs a lot of work with transaction fee calculation, coin control, and declining invalid transactions i.e. sending to many coins at once.

by the way they never came back as you had stated that they should after 24 hrs and that was an additional 900 coins as well.

It does, if you didn't change default path to something containing non-latin letters. But you are right, all you mentioned has to be fixed.

I don't know about non-latin letters but I thought it would be in the usual default location on windows %driveletter%\users\%username%\appdata\roaming\%coinname%\
between percent signs are wild card not actually used.

It looks like the default for your coin is:  C:\ProgramData\karbowanec

So, I have my coins back now.   

I try that reset after backup .

I am glad you found your wallet. Make sure you have backup. It should concern any cryptocurrency. We store blockchain by default in C:\ProgramData, the same location Monero does. This is to prevent issues with non-latin folders and filenames in GUI while we didn't mitigate incorrect work with such folders in GUI. But storing blockchain in common place does make sense. We just need to move user specific wallet to his folder later.  


Upd.

Yes. We need to do something to stuck transactions. Possible way is to enlarge initial max blocksize so our transactions would fit and only insane ones would stuck. And for those we have to make check and error message, or split transaction in few smaller.
To enlarge allowed blocksize we gonna need hardfork.

This is still work-in-progress stage of the coin. I have limited time and resources to quickly make improvements.
In case I will find programmer to do stuff, will anyone donate to fund work?

Btw, dev donation address is in first post.

I'm aware of fusion transactions. Got quick feedback, and agree that average users just want to send coins - any amounts,  not to dig into settings to enable some fusion transactions or split transactions. It looks strange, kind of crutches. But as a side option background optimization is nice and needs to be included of course.

You will find all info about Karbovanets name, it's history and the meaning of the word in first post and Wikipedia.

In first place we're going to do something to transactions limitations. We can wait as blocksize limit is slowly growing with current code but this is too long, or we can tweak coin's settings but this will be essentially a hardfork, and those who will not update will have errors and will stuck at height prior to too big block. If this change won't kill Karbo it will make it better. It is better to do it now while the network is small, and is basically one pool and one exchange.