Transaction Related Information of Edenchain

1_3UZs4pFWbRziVd1t6i2DPg.jpeg

Edenchain is the blockchain based platform capitalizing and trading tangible and intangible assets. It is making the technology worth by the adoption of the programmable economy. The programmable economy is a platform for low-cost transaction, redistribution of profits and for creating a new market for the capitalization of domestic and foreign materials.

Transaction Execution Scheduling

Edenchain has the client for update the data on the DLL for the use of transactions. The smart contracts will execute the possible transaction where Eden will use a batch and a block for units of grouping transactions. These transactions are gathering to form a batch and batches from the block.

The transactions of EL are processed on the basis of a block-by-block. The transactions will be in groups of batches including dependency among the transactions occurring into the smart contract and it can be observed easily. The similar batches of transactions are assumed to the related and there are problems in the execution of certain transactions. Other transactions may become invalidated.

If the hypothetical transaction of A generates through transaction B and transaction C, it will prove that the transactions are related and the processing will be considered to be completed normally when the transactions are executed successfully. If the transactions are grouped into batches and any error occurs to the transaction, one or all of the transactions will include into the baths for making it invalidated without any consideration for executing the orders or correlation among the transaction. It will be the result of dependency problems to be solved easily.

Transaction Data Structure

Edenchain_Token_and_use_of_proceeds.png

The transaction consists of the header and body containing few data fields. Such as;

Transaction Header

  • The public key field for the clients

  • Dependency field for the transaction data with dependency

  • Namespace field for a namespace for differentiating among the transactions

  • The nonce field for random data that differentiate among the transactions

Transaction Body

  • Header field for transaction header data

  • Header_Signature field for signature data

  • Payload field for payload data

Designing

Just like other blockchain technologies, Edenchain has designed for signing the transactions by the use of the client’s public key. The transaction header and body are configured as a pair where the dependency field of the transaction header will specify the transaction for corresponding the transaction and dependency.

This dependency field indicates the involvement of transactions while the transaction will run parallel to schedule the transactions to be performed by the accordance of the relationship and order. Even the namespace plays a vital role to delimiter by the indication to the nature of the transaction.

Eden can create its own coin and blockchain system to use the smart contracts. An example can be like this, Alice might need to generate Alice Coin and therefore, it will need to issue Alice Coin through the use of a supplied smart contract template. The issued Alice coin can transact only if it is generated when Alice is assigned as a namespace for indicating the transaction related to Alice Coin.

The collection of processing Alice Coin is related to the transaction by the reference of the transaction header. It will be used by the approach enabling Edenchain and it will improve the performance greatly with scalability and it will parallelize the transactions according to the namespace.

Edenchain is making ways out to enrich the technology with all the related advancement possible and making the system feasible to its user clearing the concept.

Website : http://edenchain.io/
Whitepaper : https://drive.google.com/file/d/1qUUUm8mNuL-7f5yYsNza1gqcZE6PoDhN/view
Telegram : https://t.me/edenchainio
Twitter : https://twitter.com/edenchainio