Built on Industry Standards

At this point we have over 3,000,000 lines of code written, mainly on C++ and C#, alongside with its extensive documentations for a better future of the DLT environment.

Read More

Offline mode

The Green Chains are built to be a community of interconnected  individual ledgers through a network, but it can also be used in offline mode for applications that do not require constant interaction with other nodes, provided that it happens for a brief period. This is very useful for low-powered devices, like the ones used in IoT environments.  Devices implementing the GreenChains standard may generate new records while remaining disconnected if their purpose is not to interact directly with other instances. Such devices must be connected to the network only to publish their records and get interlocks from other instances. After that is done, they can go back offline. Until published and mirrored, though, offline records are not considered part of the InterlockLedger network.

Read More

Security and Data Privacy

Each record added to our Green Chain for instance can be assigned to a given application. Actual application data contents are meaningless to the network, of which only its raw bytes are used to ensure data integrity.
The Green Chain standard implementation does not require application data to be stored in any particular way, applications are free to define their own data structures, which can be encrypted if the data used requires privacy. As long as the record remains unchanged, our Green Chains ensures the stored information integrity. Data integrity is always public, but actual data content can be kept private. Our Green Chain safety is strongly based on its inner cryptographic primitives security, together with the cascading effect achieved by interlocks and distributed replications. As long as, at least one secure hash algorithm and one secure digital signature algorithm exist, a Green Chain network can be built.

Read More

No Need for Global Consensus

The Green Chain approach removes the need to have global  distributed consensus for all transactions. 

Since only the nodes which is directly involved in a transaction (and the ones subscribing to watch their changes) need to be synchronised, there is no need to perform complex algorithmic operations to keep in synchronisation with a crowd of individuals or duplicate copies of the entire set of transactions that ever happened on traditional blockchain.

Read More

No Token

Read More

No Need for Mining

The addition of a new DLT block only requires the computation of a few hashes (at least two) and of a digital signature. This way, each application becomes responsible for all operations it demands, removing the need for miners and making the process way lighter and fully scalable.

Read More
error: