FLETA, a Korean blockchain platform, is aiming to create a sustainable DApp ecosystem. It has announced the release of its beta testnet with its code being accessible via GitHub. At the testnet launch, FLETA demonstrated its performance credentials, using an unidentified 6 core CPU, by achieving 10,000 average transactions per second (TPS) – with a peak 15,000 peak TPS with 6 core CPU. FLETA openly aspires to delivering 20,000 TPS when its mainnet launches in July.
“FLETA beta testnet launch marks a monumental milestone on our roadmap. The ultimate goal of FLETA mainnet is to create a blockchain system with the greatest efficiency, and to achieve a successful fusion of existing services and blockchain technology with unmatched speed,” said Paul Seungho Park, co-founder and CEO of FLETA.
“DApps are key drivers to accelerate blockchain adoptions in our everyday lives. We will strive to provide the developer-friendly environment which helps entrepreneurs and developers to stay relevant and incorporate all the positive features of blockchain technology.”
FLETA’s promise
FLETA believes its new beta blockchain platform is developer-friendly with:
- long-term scalability
- high throughput
- decentralisation
- security.
By adding FLETA Gateway on its mainnet, FLETA hopes to enhance interoperability with other existing platforms, including:
- Ethereum
- Tron
- EOS.
The core of FLETA technology and innovation would appear to lie in its;
- ‘Independent Multi-chain’ structure
- consensus algorithm (aka ‘Proof of Formulation’ or PoF
- block redesign
- LEVEL Tree validation
- parallel sharding.
FLETA and DApps
In parallel, FLETA is actively working on one of the major challenges for DApp developers, the cost. It hopes to make use of its mainnet as developer-friendly as practical. In addition to the Go programming language, FLETA smart contract capabilities will support Solidity and a C Library in order that developers can migrate projects onto FLETA.
In addition, the FLETA Gateway network will address DApp interoperability via a seamless transition between FLETA and other platforms. This should enable existing DApps to use FLETA’s service chain which (it says) is both faster and cheaper, for exchange purposes. The intended effect is to negate any risk associated with a token migration process. If this functions as designed, projects will have the freedom to set transactions for free so that users can use the chain without expenses.
FLETA microkernal architecture
FLETA’s system architecture uses a Microkernal system. The kernel constitutes the blockchain – such as Consensus and Store, Generator – and takes care of their operation. Each chain supports its own account, transaction and contract.
The fundamentals of FLETA’s microkernal approach consist of the following processes:
- exchanging each other’s data into P2P
- storing the same history and authenticating through hash chaining
- managing authority of generation/change/deletion of data through digital signatures
- changing data by proceeding history through consensus.
This microkernal-based architecture has a structure of abstracting:
- transactions
- accounts, which store and manage transactions
- contracts.
Other procedures process in the microkernal. For example, a transaction modifies an account, account data and UTXO through context. This means that the Account and Contract operate in accordance with that modification.
Enterprise Times: what does this mean
2019, as Enterprise Times anticipated at the turn of the year, see more and more organisations chasing high performance TPS, Other proponents this year have included EduHash, Devvio and Metahash.
While FLETA claims a peak 15,000 TPS on an unidentified 6 CPU system, the latest testnet report, dated in November 2018, says it used a 4 CPU system. Thus it is not (yet) clear what the evidence is for the claimed high throughput. And, as Enterprise Times has said before, high TPS throughput must be demonstrated in commercial production environments to attain credibility.
