Horizon is utilized by other ecosystem applications for tasks necessitating heightened levels of user and data security.

Within this public network, the operation monitor provides real-time information on all system events and allows independent verification of data integrity.

Horizon encompasses both system and private nodes, along with the users of ecosystem applications.

The network's public structure resembles a bush that grows simultaneously with all processes.

Within Horizon, an unlimited number of transactions can be carried out in parallel without any loss in performance.

Each user within the system acts as the initiator of a new process on the bush, owning a chain composed of user-generated blocks.

Each block serves as a distinctive identification of a specific user during a particular time period.

A personal chain is established by linking blocks on the user's device, and the combined hash from the block and related data is transmitted to the public network.

The user always retains the ownership of the block source, which is never shared with anyone.

Each user has the ability to confirm multiple blocks belonging to other users for every block they create.

During the confirmation process, unique horizontal connections are established for each block. The aggregate of all blocks from each user and their connections at that moment produces a distinctive pattern of horizontal links at levels 1-4. This pattern is crucial in crafting a personal digital signature.

Within the public network, a block must live for a considerable duration, typically at least 1 week, with many blocks' lifespan turning into months. The block's value to the network escalates as it ages and accumulates more confirmations from other network members, making it more valuable and thus more costly.

When constructing a transaction, blocks are selected based on the contract requirements. Additionally, if permitted by the contract, the initiator's personal settings can be applied. For instance, the selection of blocks can be tailored by unique block features or the geographic location of the block or its creator.

A specialized algorithm for random selection, operating on the principle of deriving a random value from data not yet on the network, is utilized to choose blocks. This selection process essentially looks ahead to the future for its randomness.

Transactions carry different levels of importance, each with distinct block requirements and values. Within a transaction, the blocks must undergo validation. The network reaches out to the block creator for validation procedures. If the source is unavailable, the block is deemed unusable for the transaction.

Validated blocks must undergo a confirmation process where other participants, typically 5-10 per block, verify the accuracy of the calculations.

If the author's request authenticity remains unverified, the subsequent actions cannot be deemed trustworthy.

Authentication procedures occur on both the author's device and the public network, irrespective of communication availability.

Horizon imposes varying requirements on authenticating requesters based on the operation's significance. Authentication is conducted through specialized operations utilizing a public bush and personal chain.

For authentication via the public bush, a validation request is made for a block from a chain older than 2 weeks. This parameter is customizable.

For instance, in the event of profile data theft, the perpetrator won't be able to perform user activities, alter email or phone details, send messages, or conduct financial transactions for a minimum of 2 weeks post the initial authorization. The genuine owner, upon the initial unsuccessful authentication of the requester, will promptly be alerted to a possible threat and can regain profile control harmlessly.

Ensuring not only the system's confidence in participant authenticity but also participants' trust in the system regarding data and operational instructions is crucial.