A new ShadowCash client has been released earlier today, which redefines the way we use QT clients. As most of you will know, privacy and anonymity are the cornerstones of SDC, but the user-friendliness left a bit to be desired. Let’s take a look at the update!
Several changes have been made on both the frontend and backend of Shadow, making it resemble a more modern and professional app framework. Where other developers would build a wallet into a browser framework, the Shadow team has done things the other way around by developing a browser framework into a wallet.
For the techy geeks amongst us, the entire front end of the new client is written in HTML5/CS3/JS using QtWebKit widgets and C++. All the terminology makes sense to me but I’d have no clue how to put it together. Good thing that isn’t my job then!
Developers who would like to tinker around with the new ShadowCash client will be pleased to hear a ShadowSDK will be released in the near future. No official release date has been announced at this point in time, but we will keep an eye out for further information.
All of ShadowCash’s previous feature are fully functional in the new client : dual key stealth addresses (ShadowSend) , encrypted messaging (ShadowChat) , and the simplified payment verification system (ShadowLite). The next step will be to integrate the new interface into the mobile application (ShadowGo).
As ShadowCash has evolved from wallet development into framework development, developers will be able to create apps and games for the Shadow platform. I’m excited to see what the community members will come up with once ShadowSDK has been released.
ShadowSend will also receive an update in the future, as research and development has already started to bring us ShadowSend V2. Implementation of the latest advancements in zero knowledge cryptographic primitives has been achieved.
ShadowChat will also receive an update, with voice, video and file attachment support coming in the future. Even though these features were scheduled for release earlier, the team pushed the features back in order to focus on core framework development.
Official announcement :