It seems that there is a level of opposition just because of a small misinformation about the version of ProximaX product. Let me try giving some clarity on this.
When we develop the MVP, we were using NEM NIS1 and IPFS. For the purposes of clarity, lets say this is the 1st version of ProximaX. The core storage concept of the first version was to extend the data that can be stored as part of the NEM Transaction. Basically its linking a IPFS data hash to a NEM Transaction. We then built a bunch of features that surrounds this idea including privacy controls, easy integration using REST API endpoints and a fully built SDK to ease the integration.
This is all available on NIS1 testnet, privatenet using either a public IPFS or a privatize IPFS (either hosted in our ProximaX environment boxes or if requested by the client, on their own premise).
The WP version is the second version which will be purest form of ProximaX with all the technology stack mentioned including the first version (storagee. This includes the storage (DFMS), consensus, catapult integration and the streaming/routing layer. If you are basing it only on the whitepaper then yes, the whitepaper version is not yet complete and is still under development but we do have first version that’s already working and can be used by interested companies like rocketshoes.
@gimer , we provide private hosting (either we host it in our servers or we provide the storage contributor node artifact to the companies and they host it locally) and its either connected to NIS1 testnet or privatenet. The data on the blockchain is just a reference hash with some metadata we built to give enhancement features such as simple searching and content validation.