How to USE EOS ?

To build a global Industrial Internet of Things platform that will be public and accessible for easy connection from any device, it is necessary to use hundreds of thousands of computing resources scattered around the world, to which the IIoT Platform can be provided without direct interaction of people or companies. This means that the provision and addition of computing resources to the IaaSB IIoT Platform should be as simple as possible using smart contracts. Currently, it is possible to implement this only with the help of the Blockchain which, in addition to the usual Blockchain functions for storing unchanged transaction information, has the following advanced functionality:

• The possibility of voluntary participation, connection, disconnection and compensation of providers of computing resources even with small computing power.
• Supports Billions of connected Devices and Millions Users
• Supports Accounts & Permissions for Resource Usage & Rate Limiting
• Rich Smart contract toolkit
• Sequential Performance
• Parallel Performance
• Low Latency
• Easy Upgrades and Bug Recovery
• Inter Blockchain Communication

None of the functioning Blockchain projects active in the world today have all of these properties at the same time. We hope to see product releases this year of distributed blockchain supercomputers, on which it will be possible to launch a decentralized IIoT Platform solution.

IIoT Telecom considers hosting its IIoT Platform on EOS.IO or SONM. In February 2018, EOS.IO published its DAWN 3.0 Alpha Announcement. Major changes in Dawn 3.0 include changing “eos” to “eosio” in all locations throughout the code. They also renamed “message” to “action”, and removed the need for developers to manually specify ‘scope’; all scope specification is now automated. The rest of the functionality repeats already released EOS.IO DAWN 2.0. It already has these functions applicable for IIoT:

• P2P Network Code
• Wasm Sanitation & CPU Sandboxing
• Resource Usage Tracking / Rate Limiting
• Genesis Import Testing
• Inter-Blockchain Communication
• Database Storage

EOS.IO contracts have access to an in-memory database where they can store application states. The contract is billed, based upon the total data they store plus a constant overhead factor for each independent database entry. This in-memory database is independent and separate from the EOS.IO Storage protocol for decentralized bulk hosting and storage.

The Blockchain EOS.IO is deployed only to Test Net, and Public Test Net EOS.IO consisting of 21 nodes using only EOS.IO DAWN 2.0, which is not compatible with DAWN 3.0. The It Telecom team actively studies oesio source codes and is planning to test IIoT Platform components in Public TestNet EOS.IO. Currently IIoT Telecom, based on Ubuntu 16.10, deployed a multi-node local test net EOS DOWN 3.0 Alpha. It performed functional testing of Smart Contracts and Database Storage.

Smartcontract developer’s API EOS DAWN 3.0.1 currently includes 11 different API modules, including the necessary Contract API, account API, Math API, Database API and others.

First of all, we are testing the capabilities of functions for recording data from IIoT devices and preserving the integrity of the database.

Database API EOS.IO DAWN contains two modules:

- Database C APIs for interfacing with the database.

- Database C++ API for interfacing with the database. It is based on pimpl idiom.

There are several supported table types identified by the number and size of the index:

- Single 64 bit Index table
- Dual 128 bit Index table

The database APIs assume that the first bytes of each record represent the primary and/or secondary keys followed by an arbitrary amount of data.

The Database C++ API provides a simple interface for storing any fixed-size structure as a database row.

One of the major benefits of using EOS.IO software for the Industrial IoT, is that the amount of bandwidth available to an application is entirely independent of any token price. If an application owner holds a relevant number of tokens on a Blockchain adopting EOS.IO software, then the application can run indefinitely within a fixed state and bandwidth usage. In such case, developers and users are unaffected from any price volatility in the token market and therefore not reliant on a price feed. In other words, a Blockchain that adopts the EOS.IO software enables block producers to naturally increase bandwidth, computation, and storage available per token, independently of the token’s value.

IIoT Telecom has already had the required volume of EOS tokens in its asset, sufficiently to start a functioning IIoT Platform. If we want to increase the power of such network, we will be able to buy tokens or rent them.

IIoT Telecom does not only consider the EOS.IO project as a base blockchain for its IIoT Platform. The SONM project promises to create a decentralized supercomputer based on network mining, but we will talk about that later. Follow our news!

Don’t forget that we started 1th Stage Token Distribution on February 19, 2018! You can get 100% Bounus only till Febrary, 28.

Visit https://iiot.tel for more information. WP: https://iiot.tel/wp-iiot.pdf

Our channels:

https://bitcointalk.org/index.php?topic=2907326
https://facebook.com/iiottel
telegram: https://t.me/iiottel