FLETA applies an independent multi-chain structure, by using the existence of a sub-chain separated from the main-chain, solving the main-chain overload issue and overcoming unnecessary fees both for developers and users.

Introducing Independent Multi-chain Structures

The independent multichain structure on the FLETA network allows for each DApp to operate on its own chain, this means that only when an additional request for tokens for an ICO happens or an interchain function occurs, will it interact with the main chain. Besides these functions, DApps are maintained independently, moreover, the DApp’s chain continues to operate even if the main chain ceases to operate by independently composing a formulator using the DApp token.

The independent Chain — requires FLETA’s DApps to facilitate each token. Using the information to designate the independent Chain node can be done via setting the Genisis information, in turn, the Account is created. The information needed to do this is may range from:

The total quantity of token

Account composition

Observer node public key

seed node

IP

Lockup

This data can next be utilised to assign a independentChain node, containing a network. This is still in the beginning steps of the production, furthering from this point, the chain divides from the main chain, and now each block is operating independently. The Smart Contract of the DApp operates in each independent Chain, fixing the execution fee or overload problems in the earlier methods.

Token Issue Transaction — is the mechanism by which FLETA exchanges token, with the token going through the administrator’s address, simultaneously driving a Token Issue Transaction. Independent Chain verifies the Issue Transaction and renders the amount in the address to which deposit is made, this is done by generating designated tokens.

Interchain Communication — DApps on the Fleta network perform as if on independent blockchains, interchain technology is called for then to support the interchain communication among DApps. Interchain technology is achieved in the way each DApp chain routinely reports its block header to the main chain, commencing the recording of that data. This, in turn, allows tokens to be transferred from one DApp to another. Following this transaction, the transferred token is entirely erased from the original chain. The chain that acquires the token receives the newest block header data from the main chain. It also assigns the chain with Light Node, receiving tokens and concluding the process to generate tokens.

FLETA’s block consists of a block header and a transaction list, using a Level structure to support Light Node and parallel processing. The basic block structure is:

Block: {BlockHeader, TransactionSignature[], Transaction[], BlockSignature}

BlockHeader: {Version, HashPrevBlock, HashLevelRoot,Timestamp, Timeout, FormulationAddress}

Benefits of Interchain Communication:

Each chain can hold various types of tokens

Smart Contract can be operated using different types of tokens.

Only tokens that are authenticated can be transferred to DApps that validate the act of drawing tokens from different DApps.

The execution fee and token to be paid are set.

In conclusion, by separating the performance of the main-chain and the data domain, each DApp is operated independently, without being mutually influenced, leading to a limitless number of DApps being available. This, in turn, results in the reduction of excessive development costs of DApps and execution fees caused by using DApps. Even though the chains are independent they are still able to interact with one another. This means the users have the ability to transfer tokens between various chains and use several token types for any DApp or smart contract on the network.