Great news! I agree with the distribution of the bounty. Good to see everyone who has put effort into this will be rewarded.

A can not keep up with you Jojatekok . But very nice to see the progress you are making!

I plan on keeping my wallet as simple and stable as possible. I would like to remind people my wallet runs on linux as well (using mono). For a full featured and slik Windows wallet Jojatekoks wallet is definatly the best choice.

I have made some adjustments to polish my wallet: Download v0.2.3
-About dialog added (shows software versions and block height).
-Changed icon (to the one from the branding kit).
-Non-main windows don't show in taskbar any longer.


(versions numbers in the screenshot are wrong, this has already been fixed in the download)

Don't panic. Your coins are there. The 'unavailable' means the coins have been spent in an earlier transaction (for the most part, I'm still figuring out what it exactly means). It does not mean you should receive them, but haven't yet.

---

On another (crypto)note, I finally found some time again to put some work in my wallet.

New in this version (download):
- Separate windows for wallet and daemon log
- Much smoother output of log lines (no more jittering and jumping around)
- Ability to send custom commands to wallet and daemon
- Name change (CryptoNote Wallet --> Monero Wallet)

You are right. My wallet looks for *.bin or *.wallet files. The extensions are configured in the settings file (CryptoNoteWallet.exe.config). When I create an option screen you will be able to change them yourself.

I agree. Some deadline on the bounty is a good idea. Some statement from the person holding the bounty (tacotime?) about the current work being done would be nice.

I wonder how many people are actually using one of the available wallets. There is a lot of talk about a GUI wallet being a necessity, but surprisingly little feedback about the available options.

I will hold of on adding new functions to my project until the rpc api is complete enough to take over communication with the wallet and daemon (I should have a look at the recently added RPC calls).

I'm sorry to hear you are having problems with my wallet. I have test the sending and receiving of coins with my wallet with and without payment id. They both still seem to work ok. Could it be there is a space somewhere in your destination address or in the payment id textbox?

---

Looking good!

I see you also have a 'spend/received' column. I just noticed in my own wallet this might be wrong. I had test wallets where the amount of spend and received combined dit not add up to the actual balance. When executing the 'incoming_transfers' command at the command line, with the 'available' or 'unavailable' argument you'll see you get the transactions of type 'F' or 'T' respectivly. I don't think the types correspond to received and spend. I changed the type column to 'Availablity'.

Maybe someone else knows the relation between availablity, the 'T' and 'F' type transactions and spending and receiving coins?

A minor update of my wallet:
- Wallet update status is shown in status bar (just like updating the blockchain, updating the wallet can take some time)
- Transaction grid now adds new transaction instead of clearing the whole grid every time it refreshes
- Changed spend/received to unavailable/available

Are you referering to my wallet? You can just leave the payment ID field empty if you don't want to include the payment id.

Thanks for the feedback! The transfer should work now (redownload the files from the link in my previous post).

I have been able to reproduce the crash when selecting log text (very weird, nothing special happens there so it seems this is one of the quircks where mono behaves differently from the .net framework). I will look into this (might be I just have to disable selecting text and add a copy to clipboard button to get around the problem).


This could be a solution, but I prefer it if I could prevent crashes al together. I think that should be the the goal instead of adding another process which monitors other processes.

I have pushed another update (v 0.2): https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip

New in this update:

- The startup screen where the user can pick a wallet now asks for the path to the wallet files. The choosen path will be remembered.
- Progress indicator when shutting down (could take a long time sometimes).
- Transactions are grouped by transaction ID for a better overview.
- The log windows now only show messages which are not handled by the wallet. This way you can spot more easily if something goes wrong.
- Linux support
  - You need Mono 3.2 (sudo apt-get install mono-runtime)
  - As far as I can tell, that's all. You can start the application with 'mono CryptoNoteWallet.exe'
  - At the moment the wallet path is not saved on mono, so it is most convenient to put the
    CryptoNoteWallet files in the same directory as the wallet files, that way you will not have
    to enter the correct path each time you run the application.

I am really curious to hear from Linux users who are willing to try out the application.


Done.

You caught me redhanded . I haven't used WPF before this project. I said before I wouldn't port to WinForms any time soon, but I changed my mind. I have it running on Ubuntu 14.04.



It generally works, but needs some more testing before I'm confident enough to release it. It will be ready in a few days.

If anybody is feeling adventurous, you can get the source from the github page and compile it yourself. The output of the CryptoNoteWallet.Gui project is the one you'll need. You will need to change the wallet and daemon executable names in the CryptoNoteWallet.Gui.exe.config (they don't have extensions on linux).

Thanks for pointing this out!

I have released a fix for this problem: https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip


It uses WPF, unfortunatly that is not supported on Mono. Should have gone with WinForms, that would have made it possible to run it on Mono without modifications.

Good to hear the RPC API is getting more functionality, if it has enough features I can switch to using the RPC API.

Hmm, then it means the daemon is working fine (reporting it has finished downloading the blockchain), but the wallet has a problem.

Could you send me your simplewallet.log?

From tomorrow I'll be offline for a few days, so expect radiosilence.

I have published a new version of the wallet which will hopefully fix the problem (couldn't reproduce it on my machine, but I have a hunch where the problem was). Download: https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip

And please, post feedback about the GUI in the GUI bounty thread. I probably miss posts about the GUI in this thread because it grows to fast

This seems to be the ouput of the wallet client, not the daemon. Could you post the output of the daemon (or at least the beginning)? I think the daemon fails to start for some reason.

Your wish...

Update (download):
- Payment ID can be entered in transfer tab.
- 'Send' button in transfer tab is not enabled while the GUI waits for confirmation or error from the wallet client.
- Solo mining support added.

---

I must sadly say the linux/mac implementation will not come from me in the near future. I have put considarable effort in porting my .NET wallet to use GTK#. I got the program running on Ubuntu, but developping the GUI for GTK# (using monodevelop) was so clunky (crashes of the IDE, combined with corruption of the designer files) I decided to put my plans to port the program to mono/gtk# on hold for now.

The core of my implementation can run on mono without any modification. If someone would like to implement a different GUI which runs on linux and/or mac, I will be happy to assist.

Could you send me the text in the 'Deamon Log' tab? Or even better, the complete bitmonerod.log file?

From your description alone I can not determine what went wrong.



I'll look into adding the possibility to include a payment id. Thanks for the heads up.

I have added simpleminer support.

You can now launch simpleminer instances from the 'Mining' tab:


Features:
- A list of currently available pools (you can enter a custom address if the pool of your choice is not listed).
- Enters your address as default pool login
- Default password (does not seem to be used in any of the pools)
- By default automaticly sets the number of mining thread to the number of logical cores
- You can choose to show or hide the miner windows

Download: https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip

Please don't loose your enthusiasm over this. As others have pointed out it is not a race. On top of that it is best to have multiple wallets with different implementations. There should not be a single wallet/implementation (single point of failure).

I totaly agree with you that the current solution is not something you want to keep in the long run. I tried and would have prefered to use the RPC API, but it is not complete enough to build a usable wallet at this moment. As there are a lot of people asking for a GUI I started creating the wallet with the idea to get it functional quickly, with the option to make use of the RPC API later on when it is available.

Hmm, was afraid so. Will have to look into other UI's. As far as I can tell other parts of the .NET framework I used are all available in mono. Maybe I'll make an alternate UI which is compatible with mono (WinForms is supported, could be an option).

Meanwhile I did another update (https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip):
- Transactions tab implemented.
- Statusbar shows number of connected peers.
- Status bar show progress (text) while downloading blockchain.
- Log windows properly scroll to bottom on new text.

The transaction tab is very rudimentary at the moment. I plan on grouping transaction by transaction id, and offering the ability to expand them to see the individual coins send.

Next stop: mining.

That would be great. We first need to find out if the .NET features I used are even available in Mono (I'm most worried about WPF, Processes and async/await).

Another minor update: I think I managed to fix the problem where the daemon log window would sometimes stop updating. The wallet now 'pings' the daemon every second by sending an enter. This forces an update of the output from the daemon and will thereby update the log window.

https://dl.dropboxusercontent.com/u/6522303/CryptoNoteWallet_latest.zip