FAQ AND FACTS

It means Input Output (IO) double exchange (two-side marketplace). The X is the symbol of crossing. In the iXXo logo we find the orange diamond, which represents private data (valuable, hot data) preserved and protected by the exchange mechanisms.
iXXo is a public Blockchain operated by trusted nodes (with some strong state-level legal enforcement). The nodes risk severe penalties (economical, penal, reputation) for wrong doing. The iXXo blockchain is a fored Ethereum with an altered and simplified consensus (for businesses, we apply the KISS: Keep It Simple ... principle).
iXXo is integrated with the dAppBox to prevent features such as smart contract functions on private data and data unlocking based on smart contract conditions.
We reached an agreement with ROCKCHAIN.COM, a crypto advisory firm in Gibraltar, who partners with us on advising our business on several strategic topics. Rockchain.io, Rockchain.org and Rockchain.blog will be redirected shortly on the rockchain.com content.
iXXo technical infrastructure contains:
-The dAppBox, a P2P client protocol connected to iXXo blockchian: The front end will be open source. There will also be an API available. (target date 2018, when stability will be reached).
The data access rules management system (which contains read access right, write access rights, delegation accesses, time-restricted accesses, ownership transfers) will be open source.
The dAppBox Service, a set of web based functions to access all dappbox features in a programmatic way, can be deployed on a custom on-demand environment for each user alongside dAppBox registration system.
-The RockEngine, a P2P privacy preserving computation framework (allow to do computation on private data on 2 nodes for a global public result).
An API will be available as a test mode only. RockEngine will not be integrated into the early versions of IXXO blockchain, and targets advanced scalable privacy-preserving features.
-The blockchain: It is a fork of Ethereum with extra features. We changed the consensus (based on POA protocol) along with the blockchain account (several "currencies" are allowed on each user account).
The protocol will be open sourced early 2019.
-The blockchain management toolkit. We deploy and scale our blockchain using Kubernetes, and autoscale the dAppBox networks using Helm.
All our infrastructure code (the links between our cloud management platform, currently Azure, and our public network) is to remain private.
The blockchain consensus and modified solidity engine will be open source allowing any business our developer to verify the legitimacy of transactions on iXXo. Anyone can run an iXXo node and check the blockchain transactions. All access rights between dAppBoxes are coded in open source smart contracts (by definition, a smart contract is open source) and access rights management and audited changes will all remain public.
iXXo is not a decentralized cloud. It integrated cloud technologies (Kubernetes) to operate its public blockchain and that is all. We believe in the community power of Kubernetes for cloud management (the most active software community by far, more then next following 4 cumulated, see below ranking). Integrating Kubernetes with a distributed Ethereum-based blockchain is challenging but fun.
iXXo is keeping data on private nodes (the dAppBoxes) and orchestrate data links inside the public blockchain. The blockchain is the orchestrator, the data are preserved and their "openness" gradually managed through the blockchain logic. Specifically, smart contracts can "unlock" some data content to some specific users based on blockchain logic, thanks to our trusted blockchain validation nodes who maintain a proxy data content zone.
We are radical on data privacy: it's not encrypted, access rights are not managed by any central part: it's private by design, and you are the whole owner of the strategy of your data distribution, with possible time-based restriction and revocation. Every data transfer is notarized and eternally kept in the blockchain ledger, so no one could ever pretend not having used the data sent by the user. Automatically, any file on the dAppBox network is notarized (we keep its proof of existence) so no one could ever pretend to be the author of a document you first put on the dAppBox network.
Because our network is operated by some legal representatives, you could also if you want quick legal proofs to be hand ready share the content only with them so that not only are you the registered and certified author, but a legal proof can also be easily redeemed instantaneously.
As some other blockchain projects working on secret smart contract puts it, blockchain without privacy is useless for businesses. While this views stands for critical data, any user data should yet be preserved and checkable in an ideal world, that's one of the motto of the decentralized IT world. We also chose to apply the KISS (Keep it Simple ...) principle, by making our trusted validator nodes run the computation on the private data for you, the dApp one side and the user the other side. This way, we have certified results on certified data with no dApp making money out of data which transfer has not been approved. Simple, but working, and cheap also.
We are using GOLANG and AngularJS for the front end. Our cloud stack is based on Kubernetes.
We are heavy users of docker and are working on fixing security issues (removing ourselves as "central guru admin") on our public network.