Testing EOS and Ledgable for use as Private Blockchains. EOS too Slow and too Unstable to be Taken Seriously.

Avatar for Sowjanya Putrevu
By
Overview data-sheet downloads Icecat 2010-2017
Likethumbsup(4)Dislikesthumbsdown(0)

We tested two blockchain platforms, EOS and Ledgable, to potentially store internal Icury off-chain transactions within the Icecat ecosystem, and got some interesting outcomes. Below, is the comparison table from the outcomes of our two tech pilots.

Though both blockchain systems have their pros and cons, EOS is relatively less favourable because of the very low speed in TPS (transactions per second) compared to Ledgable, and thus not any better than the Ethereum platform. Data missing can be very problematic as the data is not stored in multiple chains: the risk is real that data might be lost forever if a chain crashes. One other big issue for EOS is that the node needs to be restarted each time after a system change or update (or randomly sometimes) as it stops responding. In some cases we needed to use the hard-replay-blockchain option, which is very time consuming and ineffective in long run. The most fundamental and critical drawback of EOS is that private data is not stored fully privately, but in the public blockchain. Some data is just too sensitive to be dependent on the functioning of a bunch of open source hackers like EOS’s.

According to our pilot, EOS can not be used to store private database transactions, and EOS cannot replace Ethereum tokens any time soon as the stability of the environment is not beyond any doubt.

Possible scenarios to be tested in our next pilot: 

  1. Using a database system to record transactions and develop applications on top it to use and analyse data, and use a private blockchain system as backup. 
  2. Using Ledgable with multiple nodes for data consistency, and an application is used to control the (voting) rights, and a traditional database can be used as additional backup. 

Subscribe to our newsletter and stay updated.
Loading

  • commented on November 29, 2019 by Rhett Oudkerk Pool

    The EOS Mainnet runs 5000 Tx/s on a global network. We EOS Amsterdam do not recognize these results.

    Likethumbsup(0)Dislikesthumbsdown(0)
    • It depends of course on the configuration. In a high capacity configuration 5000 tps is still not a lot. In the financial market the typical benchmark is millions of tps.

      Likethumbsup(0)Dislikesthumbsdown(0)

Leave a Reply

Your email address will not be published. Required fields are marked *

Icecat xml

Open Catalog Interface (OCI): Manual for Open Icecat XML and Full Icecat XML

This document describes the Icecat XML method of Icecat's Open Catalog Inte...
 November 3, 2019
 October 4, 2018
Manual

Manual for Icecat Live: Real-Time Product Data in Your App

Icecat Live is a (free) service that enables you to insert real-time produc...
 June 10, 2022
Manual for Icecat CSV Interface

Manual for Icecat CSV Interface

This document describes the manual for Icecat CSV interface (Comma-Separate...
 September 28, 2016
Manual

Manual for Open Icecat JSON Product Requests

JSON (JavaScript Object Notation) is an increasingly popular means of trans...
 September 17, 2018
Icecat Addons plugins

Icecat Add-ons include Magento, PrestaShop, Shopify, Magento, Google Shopping, Pimcore, Bol.com. NEW: Mirakl

Icecat has a huge list of integration partners, making it easy for clients ...
 November 24, 2022
 January 20, 2020
New Standard video thumbnail

Autheos video acquisition completed

July 21, Icecat and Autheos jointly a...
 September 7, 2021

Iceclog: Content Log New Ideas like a Free Vendor Central

“Iceclog” (Icecat content log) is the Icecat ...
 June 26, 2019
Manual

Manual Personalized Interface File and Catalog from Icecat

With Icecat, you can generate personalized or customized CSV or Excel files...
 May 3, 2022