ProximaX and NEM have different goals and can coexist. Proximax is more designed as an application platform and is more centrally managed.
ProximaX is based on a private chain of NEM with some modifications. How they deploy it is up to them, but they’re no different than any other company using a private catapult chain (e.g. LuxTag, Blockstart, He3, etc). The difference is that the ProximaX team is the only team currently contributing back to the ecosystem. They have written a Go-SDK for catapult .
Additionally, the have made changes to a fork of catapult-server
, which I have reviewed. Some of their changes are not applicable to the main trunk, but some could be valuable and find their way into the main catapult-server
trunk eventually.
Even if one views ProximaX as a “competitor”, it’s not uncommon for competitors to work together on open source projects. For example, two of the largest contributors to Hadoop are Hortonworks and Cloudera who are in direct competition.
Due to the shared codebase, atomic swaps should be possible between ProximaX and catapult chains.