We’re in preparation of the next step in the ICURY project, in which we want to support internal ICURY transactions off the Ethereum ledger. The main reasons are that the transaction costs of Ethereum are far too high, the transaction speed is too low, and data on Ethereum’s ledger is public, which limits the use case because of privacy concerns.
We do a quick comparison of a few Private DLT/Secure database technologies that we might include as part of our future ICURY transaction architecture. Deliberately, we also compared a situation with a classic private database setup (DBMS), as in corporate environments a blockchain framework might not necessarily be the most effective setup.
The overview is work in progress, as during further tech trials more information about the stability and actual costs will become evident.
Critical for the private ICURY ledger is that internal transaction can be processed at zero transaction costs, and that high transaction processing speeds can be realized.
We starred* the features that are most critical in our evaluation.
Read further: ICURY, In-depth, #ledger, blockchain, CQL, cryptocurrencies, DBMS, EOS, EOSIO, icury, ledgable, SQL
Hi Sowjanya, We are working on the EuropeChain EOS side chain. Please contact me.
Your email address will not be published. Required fields are marked *
This site uses Akismet to reduce spam. Learn how your comment data is processed.