Have been watching these guys for a while now. Good to see them showing their ambitious plans.
Are they developing any NFT modules, I wonder?
Topic: Q1 Roadmap Report: FLETA Mainnet Update Completion (Read 75 times)
We are happy to announce our achievement for Q1.
FLETA has been developed firmly for the last three months to follow up its roadmap. Therefore, we share with you all about our valuable and significant achievements of the first quarter in 2021.
1. Mainnet Update — Apply Time Slot Based Transaction Control
Time-based Transaction Control technology is developed to prevent Replay Attack and solves the problems occurring with current methods and provides more beneficial features. As Time Slot Based Transaction Control is applied to FLETA mainnet, FLETA chain’s TPS, and token transfer and processing will be more efficient.
To reduce the capacity, a time concept such as expiration date was required. If a transaction can only be accepted for a certain period of time, then the range of transaction identifiers that need to be stored is limited, which means that all transaction identifiers can be stored to prevent Replay Attack with less capacity. Therefore, we decided to use a method of validating transactions based on time.
Time-based Transaction Control technology compares the timestamp of a block with the timestamp of a transaction so that only the transactions that satisfy the following conditions are reflected in the block.
Condition : (Block.Timestamp — TransactionExpireDuration) < Transaction.Timestamp <= Block.Timestamp
In blockchain, it’s Block(n).Timestamp < Block(n+1).Timestamp, so the Replay Attack can be prevented by saving only the identifier of the transaction that meets the above condition. When having 120 seconds of valid time, a TxHash identifier, and using int64 Timestamp at 30,000TPS, following memory capacity are needed.
Memory Size: (32 Bytes + 8 Bytes) * 30,000 TPS * 120 Seconds = 144MB
Using this technology to prevent the Replay Attack allows independent evaluation of transactions, small capacity with fast prevention, and transaction expiration.
Independent evaluation of a transaction can be generated and processed at the same time, even if the account uses the same address. For example, in a blockchain game, if item purchase and character data change transactions are required at the same time, even if the item purchase transaction is not added to the node due to insufficient balance, the character data change transaction can be sent and processed directly, resulting in an improvement of response and user experience. When using Nonce, I will need to reuse the Nonce if there is an invalid transaction, so I have to wait for the item purchase transaction to reflect and then send the character data change transaction.
A part of the code update is as follows. To check the detailed code update, please visit
https://github.com/fletaio/fleta/commit/a864fbaccf4d74e7481e811f70cf52d836aa12a8
https://i.imgur.com/RCrOcWP.png
Transaction expiration is an essential technology for developing a service that can actually be provided to many users. If unprocessed transactions continue to float on the chain, it will slow network performance and the transaction process will be put on hold. If I can find out the expiration time of the transaction without the need for external network communication, then I can either reissue the transaction or perform the additional process by knowing the failure of the transaction. Processing can be done by reissuing the transaction. When connecting blocks, I only need to know if the transaction expired based on that block, so I can check the transaction expiration at a lost cost without the need for external network communication.
2. FLETA-based Token Code Update
FLETA will first support ERC-20 and ERC-721 token standards as those features are used the most.
Code updates are as follows
https://i.imgur.com/N0Aaa3a.png
FLETA will also add an API that will read the latest token information data from the node. FLETA plans to support View Method that uses both ERC-20 and ERC-721.
Above FLETA-based token features are going to be added along with the updated FLETA Wallet launch in Q2, 2021.
3. Partnership
FLETA x GeoDB
https://i.imgur.com/WDmh29Q.png
On 20th January 2021, FLETA partnered with GeoDB a decentralized peer-to-peer big data sharing system based in the United Kingdom. GeoDB is a project to resolve the existing inefficiencies of the big data industry with blockchain technology. We expect to expand our ecosystem and improve FLETA’s data system.
https://medium.com/fleta-first-chain/fleta-partners-with-geodb-to-expand-our-network-and-ecosystem-b4a6de0bc2db
FLETA x Medical 4th Chain
https://i.imgur.com/EMDiReB.png
On 15th February 2021, FLETA partnered with Medical 4th Chain(M4th) the blockchain-based medical data platform. M4th has the most human microbial DNA data and uses those data to develop medicine, cooperate with medical organizations, and so on. We expect to support the M4th to develop their DApp and develop more use-cases using blockchain technology.
https://medium.com/fleta-first-chain/sendsquare-cooperates-with-medical-4th-chain-to-develop-dapp-8e45dd28f9e0
For the next second quarter in 2021, FLETA will launch the upgraded version of FLETA wallet, SDK & Dev Portal, DApp onboarding, and so on.
Please look forward to Q2 as well.
Thank you.
About FLETA
FLETA is a blockchain platform that aims to offer infrastructure that can be applied to real-world business models. FLETA has its own core blockchain technologies like Level Tree Validation, Independent multi-chain Structure, Block Redesign, FLETA Gateway and PoF(Proof-of-Formulation) which is its own consensus algorithm. With them, it aims to solve problems that existing platforms have such as slow speeds, scalability limitation, and excessive fees and provide a flexible development environment. Moreover, through its Gateway technology, it enhanced its interoperability by allowing projects issuing their tokens through other mainnets to maintain their mainnets while using FLETA chain.
Feel free to join and connect with us through any of our official channels below:
Website: https://fleta.io
FLETA Store: https://fleta.ogn.app/#/
Twitter: https://twitter.com/fletachain
Telegram: https://t.me/FLETAofficialGroup
Github: https://github.com/fletaio
Xangle: https://ko.xangle.io/project/admin/FLETA/disclosure-board
FLETA has been developed firmly for the last three months to follow up its roadmap. Therefore, we share with you all about our valuable and significant achievements of the first quarter in 2021.
1. Mainnet Update — Apply Time Slot Based Transaction Control
Time-based Transaction Control technology is developed to prevent Replay Attack and solves the problems occurring with current methods and provides more beneficial features. As Time Slot Based Transaction Control is applied to FLETA mainnet, FLETA chain’s TPS, and token transfer and processing will be more efficient.
To reduce the capacity, a time concept such as expiration date was required. If a transaction can only be accepted for a certain period of time, then the range of transaction identifiers that need to be stored is limited, which means that all transaction identifiers can be stored to prevent Replay Attack with less capacity. Therefore, we decided to use a method of validating transactions based on time.
Time-based Transaction Control technology compares the timestamp of a block with the timestamp of a transaction so that only the transactions that satisfy the following conditions are reflected in the block.
Condition : (Block.Timestamp — TransactionExpireDuration) < Transaction.Timestamp <= Block.Timestamp
In blockchain, it’s Block(n).Timestamp < Block(n+1).Timestamp, so the Replay Attack can be prevented by saving only the identifier of the transaction that meets the above condition. When having 120 seconds of valid time, a TxHash identifier, and using int64 Timestamp at 30,000TPS, following memory capacity are needed.
Memory Size: (32 Bytes + 8 Bytes) * 30,000 TPS * 120 Seconds = 144MB
Using this technology to prevent the Replay Attack allows independent evaluation of transactions, small capacity with fast prevention, and transaction expiration.
Independent evaluation of a transaction can be generated and processed at the same time, even if the account uses the same address. For example, in a blockchain game, if item purchase and character data change transactions are required at the same time, even if the item purchase transaction is not added to the node due to insufficient balance, the character data change transaction can be sent and processed directly, resulting in an improvement of response and user experience. When using Nonce, I will need to reuse the Nonce if there is an invalid transaction, so I have to wait for the item purchase transaction to reflect and then send the character data change transaction.
A part of the code update is as follows. To check the detailed code update, please visit
https://github.com/fletaio/fleta/commit/a864fbaccf4d74e7481e811f70cf52d836aa12a8
https://i.imgur.com/RCrOcWP.png
Transaction expiration is an essential technology for developing a service that can actually be provided to many users. If unprocessed transactions continue to float on the chain, it will slow network performance and the transaction process will be put on hold. If I can find out the expiration time of the transaction without the need for external network communication, then I can either reissue the transaction or perform the additional process by knowing the failure of the transaction. Processing can be done by reissuing the transaction. When connecting blocks, I only need to know if the transaction expired based on that block, so I can check the transaction expiration at a lost cost without the need for external network communication.
2. FLETA-based Token Code Update
FLETA will first support ERC-20 and ERC-721 token standards as those features are used the most.
Code updates are as follows
https://i.imgur.com/N0Aaa3a.png
FLETA will also add an API that will read the latest token information data from the node. FLETA plans to support View Method that uses both ERC-20 and ERC-721.
Above FLETA-based token features are going to be added along with the updated FLETA Wallet launch in Q2, 2021.
3. Partnership
FLETA x GeoDB
https://i.imgur.com/WDmh29Q.png
On 20th January 2021, FLETA partnered with GeoDB a decentralized peer-to-peer big data sharing system based in the United Kingdom. GeoDB is a project to resolve the existing inefficiencies of the big data industry with blockchain technology. We expect to expand our ecosystem and improve FLETA’s data system.
https://medium.com/fleta-first-chain/fleta-partners-with-geodb-to-expand-our-network-and-ecosystem-b4a6de0bc2db
FLETA x Medical 4th Chain
https://i.imgur.com/EMDiReB.png
On 15th February 2021, FLETA partnered with Medical 4th Chain(M4th) the blockchain-based medical data platform. M4th has the most human microbial DNA data and uses those data to develop medicine, cooperate with medical organizations, and so on. We expect to support the M4th to develop their DApp and develop more use-cases using blockchain technology.
https://medium.com/fleta-first-chain/sendsquare-cooperates-with-medical-4th-chain-to-develop-dapp-8e45dd28f9e0
For the next second quarter in 2021, FLETA will launch the upgraded version of FLETA wallet, SDK & Dev Portal, DApp onboarding, and so on.
Please look forward to Q2 as well.
Thank you.
About FLETA
FLETA is a blockchain platform that aims to offer infrastructure that can be applied to real-world business models. FLETA has its own core blockchain technologies like Level Tree Validation, Independent multi-chain Structure, Block Redesign, FLETA Gateway and PoF(Proof-of-Formulation) which is its own consensus algorithm. With them, it aims to solve problems that existing platforms have such as slow speeds, scalability limitation, and excessive fees and provide a flexible development environment. Moreover, through its Gateway technology, it enhanced its interoperability by allowing projects issuing their tokens through other mainnets to maintain their mainnets while using FLETA chain.
Feel free to join and connect with us through any of our official channels below:
Website: https://fleta.io
FLETA Store: https://fleta.ogn.app/#/
Twitter: https://twitter.com/fletachain
Telegram: https://t.me/FLETAofficialGroup
Github: https://github.com/fletaio
Xangle: https://ko.xangle.io/project/admin/FLETA/disclosure-board
Jump to: