First and most important i wish a very Happy New Year to all Casinocoin enthusiasts. I hope all of you and your loved ones have a great 2016! I am pretty sure casinocoin will contribute to that by being the rising star of the 2016 crypto world. I have had a very necessary time of for the past few weeks but things will pickup again from now.
Work is going steadily on the walletserver/mobile clients. Let me explain a bit what i am doing, ... i am extending the current C++ casinocoin core sourcecode to make it possible to use the current blockchain code and be able to plugin to that any wallet file that is needed. I want to have the user to decide if they want to leave the wallet file on the server, the client, or both. That way we move the blockchain away from the actual wallet and a user can potentially use the same wallet on a desktop client, browser or mobile client. To make this work i have to ensure that the wallet code is capable of high load with a high concurrent wallet count and stays threadsave and stable. The communication with the clients will be through message queues (RabbitMQ) and all security and rest services will be build on the WSO2 stack. Using the message queues will also help masquerade the actual walletserver location from the clients. Clients will include user accounts, OAuth and 2FA, probably with an added extra personal security token on top of that. As you can see, a lot of work and i am still targeting Q1 but this is by no means a hard deadline ....
Currently i am the only developer for Casinocoin, ... mabe Felix will help out a bit more on some features for the wallet but still it would be nice if there was some more help from the community on the development side of things, ... my workqueue is kind of big at the moment. If anybody has C++/Qt or mobile development experience with Ionic/Cordova/AngularJS and is willing to spent some time on development please contact me.
I cna help you with the rabbitmq piec
First and most important i wish a very Happy New Year to all Casinocoin enthusiasts. I hope all of you and your loved ones have a great 2016! I am pretty sure casinocoin will contribute to that by being the rising star of the 2016 crypto world. I have had a very necessary time of for the past few weeks but things will pickup again from now.
Work is going steadily on the walletserver/mobile clients. Let me explain a bit what i am doing, ... i am extending the current C++ casinocoin core sourcecode to make it possible to use the current blockchain code and be able to plugin to that any wallet file that is needed. I want to have the user to decide if they want to leave the wallet file on the server, the client, or both. That way we move the blockchain away from the actual wallet and a user can potentially use the same wallet on a desktop client, browser or mobile client. To make this work i have to ensure that the wallet code is capable of high load with a high concurrent wallet count and stays threadsave and stable. The communication with the clients will be through message queues (RabbitMQ) and all security and rest services will be build on the WSO2 stack. Using the message queues will also help masquerade the actual walletserver location from the clients. Clients will include user accounts, OAuth and 2FA, probably with an added extra personal security token on top of that. As you can see, a lot of work and i am still targeting Q1 but this is by no means a hard deadline ....
Currently i am the only developer for Casinocoin, ... mabe Felix will help out a bit more on some features for the wallet but still it would be nice if there was some more help from the community on the development side of things, ... my workqueue is kind of big at the moment. If anybody has C++/Qt or mobile development experience with Ionic/Cordova/AngularJS and is willing to spent some time on development please contact me.
Be careful with rabbit. You have to watch the number of connections and periodically reset the broker. That damn thing leaks open sockets. If you need some help with that I'm here. Also take a look at using ssl and mirrored queues.