In this section, we will explain how the whole software is being basically built, so we encourage everyone to read it! (The vocabulary might change in the future, we will introduce SDK, API, and OTA terms).

Why do we need an API ?

The blockchain is only a tool that references all transactions as blocks, to illustrate you can look at it as ingredients to make a dish. We indeed need to cut them, prepare them etc., in other words interact with them, because otherwise we cannot make a meal. It is the same for us, and that is why we need an API to use the blockchain.

What the API is going to do ?

The API will serve as a set of classes and functions to use and operate on the blockchain. It will also contains functions that can be directly used in the front-end and therefore allow the user to interact with other peers and the blockchain.

It will create a decentralized network which connect all devices where each one of them is a web server and a web client. We call them websockets. Request will be handled with a REST protocol.

Since we are in a decentralized network, everyone will have a copy of the block chain and our mission is to keep it updated on most of devices.

To illustrate a transaction we will take the a user A and user B, let us say that user A wants to send 1 XCoin to user B, what is happening concretely ?

List of features

To be determined after brainstoming.