Not a lot of people know but Bitcoin for most nodes is not the graphical Qt version showing your wallet balances and transactions. Instead most nodes run the daemon or server version. This version runs in the background and is communicated by using RPC commands on the commandline or through an application.
With MicroCash I want to have the server actually be connectable through a graphical web client. This way I can drop support for the MicroCash C# client which I think just added a lot of time to Realsolids development schedule. He told me the reason for that client was that others could make it while he made the MicroCash server but instead he was left with both projects.
To allow web browsers to connect to a MicroCash server requires a bit more code but not too much. After all, the RPC code already is pretty much like a webserver. I think it will actually be fairly efficient to convert Realsolid’s server code to support this because he already had a wallet system in Microcash server that was accessible over the command line or RPC. All I need to do is hook that up to a graphical web UI and call the same functions. However since I haven’t yet migrated his wallet code into my server this is still something I have to do.
With this web browser support it means MicroCash will nearly be platform independant even if the server is bound to a few platforms (Windowns or Linux servers). I still need to have a talk with Realsolid about this but I believe I may be able to do a brain wallet that would allow a web browser to use an untrusted node as a buffer to the MicroCash network securely. This would mean all clients would be so called “light clients” only requiring a user to remember a password to access his funds from anywhere in the world. There are a lot of ideas about this that I still have to put together into an actual framework but it is exciting when it comes to actual use cases for MicroCash.