Hi alpho2k,

in a short answer yes and no.

initial rls will depend on several components of the overall project working together as-one. (as per that article URL posted previously) which highlights some of the complexities involved in a project of this kind. to incrementally release part of a project would be the equivalent of building a house without the cement as an example, and then once the cement truck arrives we remove all the bricks and start again.. type-of-thing.. Systems are reliant on other subsystems. HTTPS stuff, the RPC stuff and the Nodejs/NWJS stuff which in turn relies on the mongo/Relic realtime & DB stuff.. so its like the middleware needs somewhere to get routed to and is kind of a way to do it incrementally after initial release has shipped...  With P2P apps I cannot rely on LocalStorage as an example, I cannot rely on cache and write backs as another example these can all be leveraged in their own rights in certain sections of this project where applicable but the front/backend and client NWJS apps all need a place to pull/push their data to/from without the backend for example where will the rest of the apps pull or push to??

Without the endpoints to direct data to or gather data from; if released without the complete picture would be like plugging in a power socket into a generator without any fuel. The lights are on but nobody's home kind of deal.

Its like having a altcoin with only the nodes working on testnet and no wallet.. that's probably the closest analogy I can come up with if I release it now. 

They all rely on each other in some shape or form. The client and AM-X backend needs to know what block it's on to interact correctly with the network. And the client needs to also know which blocks to act upon/trigger as per events. if the BC is not talking to lets say the client then the client will have nothing to do but just to look pretty and wait for instructions. See where I am going with this.. All are crucial, all are interdependent but yet self contained in their own-rights as to be counted as separate applications, which all sounds contradictory but still true.

There are methods which could be exposed internally, re-adjusted based from the custom aerome daemon build i done to allow for a very very basic example but its a waste of time and would look completely shit. not worth the time to do imho. The parts which are causing delays at the present moment are in the actual headers packets transmitted from the network to the client. To handle the SContracts data packets I needed to adjust how the client consumes normal blocks sent from the network and insert some extra frames which allows for the BC to manage the Smart-contract data-flows. its a pain in the ass as I do not have any reference to go by/from as a working example. The offerings which are out there presently only explain to me a limited portion of the problem and not the complete picture which I am having to work through. NXT have used a similar mechanism to accomplish what I am in the process of achieving so that helps a great deal. I am relying on my memory from the JEE stuff I used to do to work out / reverse a section from their work and port it over to AM-X specifically the SC portion which is only a few lines of code.

In answer to your query alpho2k yes it can be released incrementally which is what I am going to do but the whole picture needs to be clear AND functional prior to public  release. Everything is fully modular as is the way in modern coding practices separation of concerns but there are unfortunately exceptions to this rule as in this case.

The process will definitely require input from the community as its for you guys which its being built for AND this process WILL undoubtedly require changes to me made. I suspect this process will continue indefinitely until we reach a milestone which clears the backlog of requests and features work in a manner which all we like..

X_____ stop your stupid comments it's pathetic..