Structure of DEMON Chain

The DEMON Chain structure, while reminiscent of traditional blockchain models, introduces unique elements that distinguish it from its predecessors. One such feature is its novel data structure, designed to incorporate hashes, signatures, timestamps, addresses, transactions, smart contracts, Stories, and index information.

Each component of this data structure serves a distinct role:

Hash: Represents the value of the previous block, thus maintaining the linked nature of the blockchain.

Transaction: Holds the value of each transaction within the list of transactions per block.

Smart Contract: Contains information regarding the smart contracts initiated by a given account.

The term 'Story', a unique element in DEMON Chain's data structure, is designed to track dynamic information, such as the history of distribution. It references the transaction value filled with Story in the transactions of the event block. While it bears similarities to transactions, the Story structure is augmented to include information on inherited properties. This serves to provide a more comprehensive and detailed record of transactions, augmenting the transparency and traceability of operations within the DEMON Chain.

Moreover, the data structure of DEMON Chain incorporates an algorithm designed to prevent duplicate storage into the event block. This mechanism ensures the integrity of data stored within the blockchain and helps enhance the efficiency of data storage and retrieval.

DATA STRUCTURES OF EVENT BLOCK

The DEMON chain incorporates a threefold account structure: externally-owned accounts, contract accounts, and Story accounts.

Externally-owned Accounts: These accounts are controlled by a private key and are capable of initiating transactions of DEMON tokens to other accounts within the network. In addition, externally-owned accounts can also create new contract accounts.

Contract Accounts: These are governed by control code and are designed to execute pre-set instructions when triggered by specific conditions. Notably, a contract account can call upon another contract account, but only when it is first called upon by an externally-owned account.

Story Accounts: These accounts, created by the contract code, are responsible for managing Story information. These accounts store transactions and specific Story data related to the Smart Contract.

A unique feature of the DEMON chain is the incorporation of Smart Contracts, which are programmed to execute automatically when certain conditions are fulfilled. The execution of these Smart Contracts generates a Story within the DEMON chain. The Story, thus, encapsulates the history of automatic executions triggered by the fulfillment of Smart Contract conditions. This design enables comprehensive and transparent tracking of Smart Contract activities within the DEMON chain.

Interactions of accounts within DEMON Chain

A Distributed Application (DApp) within the DEMON chain leverages the network's distributed resources to bolster its reliability and security. Operating directly from the user's browser, the DApp can execute contract code stored within the DEMON network. This application provides the potential for a free and decentralized web ecosystem, fostering the creation of a new digital infrastructure optimized for hyper-connected networks.

In addition, DApps on the DEMON Chain can serve as brokers or central control authorities, facilitating efficient business process transformations. These applications can provide borderless services, transcending geographical restrictions and conventional boundaries.

The DEMON Chain stores data each time a new block is generated or the status of an account alters. Each status value is stored within a block head, which utilizes a hash tree structure based on a Merkle tree. This structure enhances the network's ability to maintain data integrity and consistency.

The DEMON Chain not only provides an environment for the implementation of Smart Contracts but also processes transactions involving Story information. Upon the creation of every new block, the head note is stored into the Story root, contributing to an organized and transparent record of the network's transaction history.