I wanted to add some informations and clarify certain things because the site is not that much informational.
Already the reason why there is no download link or source on the site, is due to the nature of the project which is more conceived as a blockchain engine rather than a monolithic core linked exclusively to a coin, and we have been testing various kind of projects with different kind of blockchains, not all of them are focused mainly on holding coin, or hold any coin of value, so to avoid confusion on the website we prefer to focus on the ico and have simple interface rather than having different kind of wallet and test and middleware which would be confusing on what is exactly related to the ico coin.
The way i view it, it's more to be seen on the over all as an application framework to work with blockchain for different purpose, rather than being focused on handling à single coin, the property of blockchain that is very interesting to me is the principle of publicly verifiable digital ownership, and ultimatly im more interested in developping distributed application that exploit this property, rather than developping a single coin.
Now also having a well maintained coin of our own is still a must to exist in the blockchain world, im not sure which future update are to be integrated into this coin vs other blockchain, but changes should be easy to integrate into it, either it will require some kind of fork to integrate future progress on non transaction blocks and hierarchised data, or integrated on the basis of external modules if they dont change the way blocks are validated.
One of the problem I see with most core ive seen is that it's complex c++ code, very monolithic, and not developped as a library or framework that can easily be integrated in other applications, the rpc interface mitigiate this, but it still limit the possibilities to make advanced low latency application, cryptonote used an approach more in tune with having a core library that implement the base functionalities, and different blockchain based on the same core, with the node separated from the wallets, but for most coin need to deal with the whole thing with the forks and tweaks specific to a coin, and it's not that trivial to update the code due to high coupling and complex code, long compilation time, need for lot of framework to compile and modify the code etc
The system of standalone binary module is also a key feature, for example it allow to add and deploy new rpc functions very easily, just need to declare the function in the C file, recompile the rpc module (which is standalone , do not depend on anything on the system, not even base stdc header and runtime), and then the module can be copied from windows to linux and vice versa, which allow for very fast deployment of updates, and easy check of code integrity as it's the exact same binary module that will run on all systems.
Another point that is also key is related to graphic interface, most coin opted for QT , but it's still rather heavy, and not trivial to modify, and need to recompile the wallet for each platform each time a change is to be made on the interface. With the html5 approach, the wallet application is made in html5/js, so it works on all platform, can connect remote node with the graphic interface from a browser, and can be changed and customized easily, without recompiling.
The last aspect I want to speak of is related to separation of public and private data which i find rather loose with the monolithic core approach, the public data is the blockchain itself, and private data are private keys and wallet based infos, and both are stored in the node without a true system of inner accounting, and data signature also has to be done with the node itself, whereas with the html5 approach, it works more like a credit card where the browser can sign transaction on it's own, without a node being locally installed,or the node having to know about the private key at all, and private data remain out the node and remain private on a per user basis rather than a per node basis where all the keys stored in a node are accessible and useable by anyone having access to the node.
The modifications will mostly affect purenode engine and the qt wallet will disapear latter on, it's used to kick start the coin with a well tested and recognized mature core, purenode can already synchronise and check the block and tx, and can support either pow or pos or hybrid coins, with properties being customisable via a conf file.