Insolar Technology

Vision and
purpose

Insolar is creating a distributed environment for efficient processes between enterprises, without demanding extra IT efforts or skills.

Distributed business networks

Real competitive benefits

Enabling new ways of getting competitive benefits within and across industries

Full compatibility

Providing efficient DLT solutions that can be used together with the existing legacy instruments

Enhanced business interactions

Handling increasing complexity and intensive diversification of business interactions

Comprehensive approach

Perfect combination of business capabilities and technology

Insolar and other platforms:
What's the difference?

Public Networks
Private Networks
Hybrid Networks
Open Source Code
YES
Public Permissioned
YES
Private Permissioned
YES
Public and private networks can work simultaneously
YES
NO
YES
Private Permissioned
NO
PARTIAL
Public Docker is not compiled from the public source code
NO
YES
Private Permissioned
NO
YES
NO
NO
NO
NO
YES
Public Permissionless
NO
NO
YES
YES
Public Permissioned
NO
PARTIAL
Hybrid solution planned but not released yet
YES
YES
Public Permissioned
NO
NO
YES
YES
Public Permissionless
NO
NO
YES
YES
Public Permissioned
NO
NO
PARTIAL
Testing forks are private and system does frequet hot-swaps
YES
Public Permissionless
NO
NO
YES
YES
Public Permissioned
NO
NO
YES
YES
Public Permissionless
NO
NO
YES
Smart Contract Support
Smart Contract Languages
Advanced Contracts
Amendable Smart Contracts
YES
Java, Golang, JavaScript
YES
Multiple Smart Contract Types + Confidential contracts + Public contracts
YES
YES
Golang, JavaScript
YES
Multiple Smart Contract Types + Confidential contracts
NO
YES
Kotlin, Java
YES
Multiple Smart Contract Types + Legal contracts integration
NO
YES
Solidity
YES
Private & public contracts
NO
YES
Solidity
NO
NO
PARTIAL
Only with Codius
Any programming languages
NO
NO
PARTIAL
Not turing complete
Multiple languages
NO
NO
YES
C++, WASM enables multiple others
NO
NO
YES
C#, VB.Next, F#, Java, Kotlin, Python
NO
NO
YES
Abra
PARTIAL
Not natively - recently supported with TOQEN
NO
YES
Solidity
NO
NO
YES
Plutus (Haskell-based)
NO
NO
Throughput
Scalability
Block Time, s
Finality Time, s
Large transactions
Long transactions
Node Specialisation
HIGH
10,000 tps on 20 nodes
YES
Scalable business logic domain structure and cloud structure to provide performance
1 - 10
2 - 30 sec (2-3 blocks)
YES
YES
YES
2 Groups (storage and processing), each group with 3 validation Layers
MEDIUM
400 tps (practical) vs 2,250 tps max benchmark
YES
Channel based, limited to not more than 50 nodes per channel
0.5 - 2
1 - 10 sec transactiondepents on number of node in channel and its remoteness) / 60 sec channel creation
YES
NO
YES
(orderer + nodes)
MEDIUM
1,700 tps (1 node) and 170 tps (2 nodes)
PARTIAL
Not all nodes see all transactions
0.5 - 2
1-10 sec transaction (depends on transaction and net configuration)
YES
NO
YES
(notary + nodes)
MEDIUM
2,100 tps & 650 tps (private contracts)
YES
The consensus is among relatively few nodes)
2
2
YES
NO
YES
(node, tx manager, enclave)
LOW
20 tps
PARTIAL
Low now, but a lot of ongoing work on state sharding
15
180
NO
NO
Full nodes (validation) and light nodes (fast sync)
MEDIUM
1,500 tps
YES
3.5
3.5
NO
NO
YES
(public server validating server signing server)
MEDIUM
1,000 tps
YES
Hardware dependent
2 - 8
2 - 8
NO
NO
Watcher, Archiever, Basic validator, full validator
MEDIUM
4000 tps
PARTIAL
Allows only horizontal scalability
0.5
180
NO
NO
Validators (21 nodes each round) and non-validators
MEDIUM
1,000 tps (average, long time between blocks)
YES
Consensus among relatively few nodes
18 - 24
18 - 24
YES
NO
Consensus nodes (byzantine) and non-consensus nodes
LOW
500-800 tps
PARTIAL
Allows only horizontal scalability
2
120
NO
NO
Full node, light node and headless nodes
HIGH
10,000 max (50 tps average)
YES
Unproven yet
10
60
YES
NO
Authority and Economic Nodes
LOW
10 tps
YES
Unproven yet, multiple consensus groups in parallel (sharding)
20
120
NO
NO
Partially. Multiple roles in protocol, but over time an individual node can take on all roles
Consensus Models Supported
Dynamic Consensus
Different
YES
Defined by Domain politics.
PBFT (RAFT announsed in 1.4)
YES
Plug-in Based Consensus
Validity consensus and Uniqueness consensus
Validity consensus and Uniqueness consensus
Raft-based Consensus and Istanbul BFT/PBFT
NO
Proof of Work
Testing a version of Proof of Stake
NO
RPCA - 4-round heuristic consensus
NO
Federated Byzantine Agreement
NO
Delegated Proof of Stage
NO
Delegated Byzantine Fault Tolerance
NO
Proof of Work
NO
Proof of Authority
NO
Leader based Proof of Stake
NO
Customizable Data Governance
Data Regulations
Atomic Swaps
Side Chains
National Cryptography Standards
Multi-Zone Security
Yes, also with data sharding
GDPR
HIPAA
EHR & EMR
YES
YES
YES
Signing and TLS levels
YES
YES
but without data sharding
GDPR
HIPAA
YES
NO
YES
Endorsement only
NO
YES
but without data sharding
HIPAA
EHR & EMR
YES
NO
NO
NO
YES
but without data sharding
Partially (with private contracts through public/private state separation)
YES
using parity-bridge
NO
NO
NO
NO
NO
YES
based on Altcoin Exchange
YES
(using Loom Network)
NO
NO
NO
YES
only with ILP
PARTIAL
based on Atomicwallet
NO
NO
NO
NO
PARTIAL
support for private transactions with Lightning
YES
based on rate3, Atomicwallet
NO
NO
NO
NO
NO
YES
via Hashed Timelock Contracts
NO
NO
NO
NO
NO
YES
via superconducting transactions
NO
YES
NO
NO
NO
No, not yet (might be possible with TOQEN)
NO
NO
NO
NO
SO27001 standards, GDPR and China Cybersecurity Law
YES
NO
NO
NO
NO
NO
No, but planned for the Daedalus wallet
NO
NO
NO
Primary Purpose
Flexibility
Interoperability
Enterprise General purpose
YES
Flexibility by design
YES
with Hyperledger Fabric and Corda
Enterprise General purpose
YES
Customizabile by add-ons
PARTIAL
within Hyperledger family
Enterprise Financial Industries
YES
Customizabile by add-ons
NO
Enterprise Financial Industries
PARTIAL
Only for financial and reporting businesses
NO
General purpose Value transfer
LOW
NO
Payments
LOW
NO
Payments
LOW
NO
General purpose Value transfer
YES
Flexibility by design
NO
General purpose Value transfer
LOW
NO
Machine to Machine economy (IoT)
LOW
NO
Enterprise Integration
YES
Flexibility by design
NO
General purpose Value transfer
LOW
NO

Insolar architecture basics

DOMAINS

Domains

Domains manage and adjust Insolar capabilities to different applications by establishing work rules, policies, standards, generic processes and data formats. Insolar only registers domains. Management procedures are defined by each domain individually.

CONTRACTS

Contracts

Insolar is a unified platform designed on the everything-is-a-contract principle. Contracts include a compact, stand-alone application (smart contract), a contract aggregator, an oracle providing access to an external system, etc. Contracts guarantee full compliance with the rules established by domains.

CLOUDS

Clouds

Insolar's cloud is a set of nodes represented by computing power and storage providers. Clouds ensure storage and the execution of contracts in domains bound to the cloud. A standard cloud implementation is based on blockchain technology. Alternatively, a cloud may be implemented on a single node, via DBMS, for example.

Streamlined interactions between different companies and jurisdictions

01

Business logic domains with fully customizable governance models

02 SEPARATION OF BUSINESS LOGIC

Separation of business logic between network, ledger and cloud layers

03 SUPPORT OF VARIOUS NETWORK TYPES

Support of open, federated, private and hybrid networks

04 DECETRALIZED AND CENTRALIZED LEDGERS

Utilization of distributed and centralized ledgers in global and regional configurations

05 PROCESSING OF CONSIDERABLE PAYLOAD

Processing of considerable payload

06 INTEROPERABILITY

Interoperability of different domains and networks with relevant security features

07 SUPPORT AND MAINTENANCE TOOLING

Support and maintenance tooling

Innovation

The innovation behind Insolar is the result of collaboration between our architectural, product, engineering and research teams.

01 SEPARATION OF CONSENSUS

Separation of consensus

Open-source and open operation model

02 DYNAMIC BALANCING

Dynamic balancing

Unified tools and rules management for all elements – from nodes, pools and networks to data standards, business services and regulation policies

03 NEAR-LINEAR SCALABILITY

Near-linear scalability

Modularity at all levels from the bottom of core code to smart contracts, with the ability to reuse the embedded functionality of different domains

04 LOGIC AND STORAGE CONSENSUS

Logic and storage consensus

Disambiguation of logical consensus (e.g. signatures of parties, plus notary) and storage consensus (distribution of data, number of backups, etc)

05 DOCUMENT-BASED TRANSACTIONS

Document-based transactions

Customizable governance models over smart contracts and transactions for versioning, amending, detecting and managing cascading effects

06 SCATTERED PROCESSING AND STORAGE

Scattered processing and storage

Network segments / domains can run in different styles (e.g. isolated / private, connected, open, and arranged in different hybrid combinations)

Learn how Insolar will deliver value to your enterprise CONTACT US