Horizon Security System

The interface of the Horizon security system operations monitor has undergone a major update. Improvements were made with regard to synchronizing with other components of the ecosystem and to integrate with third-party systems. The updated monitor also includes enhancements to blocks, transactions, workers, and operations, along with the addition of telemetry and network analytics. Ongoing work is being done to implement a search module across the public network and special settings for users. You can access the Activity Monitor at: http://ankhorizon.com

https://t.me/horizonsecurity/154 https://t.me/horizonsecurity/160 https://t.me/horizonsecurity/173 + https://t.me/horizonsecurity/174 https://t.me/horizonsecurity/178 https://t.me/horizonsecurity/186 + https://t.me/horizonsecurity/192 https://t.me/horizonsecurity/195 https://t.me/horizonsecurity/196

The Add System Asset Balance contract was used for the first time. https://ankhorizon.com/transaction/8183b219-f268-49a8-900e-8ae82a352bbb This contract is responsible for depositing system assets for operations. In this instance, a transaction for 50,000 rubles was made to deposit the Horizon Ruble system asset.

The first system contract revision update transaction was successfully completed. https://ankhorizon.com/transaction/9b7c7bf2-276e-45ca-82af-14107bdef22e The most recent version will be used for any new operations that call for this contract. The terms of the contract that were in force at the time of the previous contracts viability still apply to previously completed transactions.

The initial preparations for the first Horizon system node are coming to fruition. Set the date and time for January 19, 2024, 13:00 UTC Enough source data has been generated to launch a public network. On January 19, 2024, a chain of system contracts will be registered, and system users in the network will begin to be verified, the first system assets will be created, among other things. Horizon will be able to perform the tasks assigned to it following this event, including maintaining security events, verifying operations, authenticating requests, signing documents, transferring assets, and much more. The entire process will be livestreamed, both in the official Telegram channel and on other official platforms.

The first official node of the Horizon security blockchain has been initiated. System worker blocks are now being accumulated, and plans are underway to launch the contract factory and register the first system’s service contracts. This step is required for system operations, servicing security events, authenticating data and author query mechanisms, creating system assets, and performing other tasks. Horizon is a level 0-1 network with a proprietary consensus, built on a model for organizing horizontal loyal connections, reputations and real-world behavioral patterns. Within the network, workers create blocks, which are then confirmed and used in transactions. System worker blocks are used exclusively in system transactions. The Horizon network contract factory is set to begin operations in the coming days. The exact time of the launch will be announced shortly and will be livestreamed online across platforms. Stay tuned for more info! Source: https://coinmarketcap.com/community/post/332905534/

Young system workers on the first official node are preparing blocks for the first transactions. The network launch is coming soon!

The network has been updated. A chain of system contracts, as well as the first system asset, have been successfully created. The System Reward contract was used to transfer the system asset. The operations were subjected to integrity checks. The system's operations were examined for fault tolerance. Anyone who has signed up for the test program will soon begin receiving automatic task notifications. fenomy.io is the network's test node, on which all updates are tested and implemented.

Information! Currently undergoing a major network upgrade, registering working contracts, and setting up the environment for testing. As soon as the work is completed, we will publish an official announcement.

The main system employs blockchain technologies to implement an algorithm for authenticating and protecting user data from the influence of criminal activity. How does it work Each system participant has their own chain of blocks built on the user's mobile device. On the main network, user blocks are registered. In the main network, the user's mobile device stores the initial data of each block as well as a hash (source + the previous block's hash). If the user needs to perform any system operation that involves changing user data or interacting within the system, the system will prompt the user to calculate a block of a certain age with a lifespan of 7 days or longer, depending on the type of action. In this case, to pass the checking phase, the values of all variables in the calculation formula must be provided, as well as the initial data of the block requested by the system. One block can only be used once before it is considered validated. This checking procedure will have no effect on the user's workflow. Everything happens almost instantly and automatically. If the authentication fails, no actions will be recorded in the system. As a result, if an attacker gains access to a user's profile and attempts to perform any actions on the user's behalf, he will be unable to authenticate the action for at least 7 days after the first authorization until a new chain is formed. If an authentication attempt fails, the system will notify the profile owner, who will have at least 7 days to restore access. The verification dates in the profile settings can be set to any number of days greater than 7 by the system user. What operations require authentication but are not limited to Almost any operation within the system triggers automatic authentication using the blockchain. Among these operations are: - system authorization of each new system user - changes in profile details (name, email, phone number, date of birth, avatar, etc.) - sending a message to the user's relations or in public groups - creation of any entities - making changes to any entities already created (groups, companies, objects, etc.) - financial transactions - signing documents via digital signature - obtaining personal data from an encrypted container If the profile owner does not have access to his chain for whatever reason, backup solutions have been implemented to restore access. This blockchain-based solution is universal and can be used in third-party applications outside our ecosystem.

The public table of operation parameters. Each operation has a unique hash. If there are multiple transactions in a single operation, the hash is calculated separately for each transaction. To calculate the hash of an operation, you must first understand which parameters are used in the operation. The parameters' composition is determined by the type of operation. Some operations may have a set of parameters, whereas others may have their own set. The number of parameters varies as well. Parameters can be complex, containing an entire file, image, or digital signature, or simple, containing only letters or numbers, such as the Nonce parameter, which is always present in every transaction. To calculate the hash of an operation correctly, the system employs a special parameter table from which it is possible to determine how to calculate the values of each parameter, as well as the correct order of values, to obtain the correct hash of the operation. There is also a version of the parameter table. When the parameter table is modified, the new table is registered in the blockchain via the system contract, and its version is updated and changed. When checking transaction values, if an older version of the table was used in earlier operations, the version of the parameter table that was current at the time of the operation is used. A public parameter table enables anyone to independently verify the accuracy of any operation. Another important and necessary step in successfully launching the network was the publication of a public and up-to-date table of operation parameters.

New L0/L1 security Blockchain Let the open testing begin! The network will launch in December 2023. To successfully launch the blockchain and integrate it with other components of the ecosystem, open testing must be conducted, during which we will check all stages of operations such as contract performance, versioning, and task execution on the participants end. Anyone can take part! During testing, you will be required to complete simple tasks that should only take a few minutes. Test participants receive: - reward points for each completed task - network reputation growth, which correlates with the reward amount for performing tasks - access to exclusive team airdrops - exclusive team contests - various benefits following network launch Test participants who earn a high number of points will be able to work with the network's most important operations. To take part in testing, sign up through the Telegram bot @fenomy_bot and click on the Testing tab, and complete the first three tasks. The Fenomy ecosystem's Blockchain is a completely novel phenomenon that has never been seen before. The network's primary goal is to support ecosystem operations, ensure personal data security, and control integrity and authenticity. The system does not have its own cryptocurrency, rather transactions can be conducted using various assets. The reputation of participants is the system's most valuable asset. The Blockchain was created from the ground up, beginning with the first line of code. A new consensus is being used, which is based on horizontal connections, reputation, and the behavioral patterns of ordinary people in the real world. The network includes mobile devices used by ecosystem users. The performance of the device is unimportant. Participants in the network compete not on whose equipment is more powerful but on the quality indicators and compliance with the requirements for various types of operations. We look forward to welcoming you to the testing team. Welcome!

There are specific criteria for the blocks to be selected for each transaction type. Only system worker blocks are suitable for some types of operations; for others, blocks from system users are required, which must meet certain criteria depending on the type of operation: - block lifespan from the moment of creation - the reputation of the block's creator - the time since the block's creator registered in the system  - the number of block confirmations since creation As well as other criteria. A transaction that performs an operation must also meet the following criteria: - the transaction's block count  - the percentage of blocks validated in a single transaction  - the percentage of block validation confirmations - the number of transactions in a single operation  - the number of nodes involved in the transaction  - the time it takes to complete the transaction As well as other criteria The higher the criteria for blocks and transactions, the more expensive the blocks and transaction fees are, and hence the greater the reward for the creator of each block. The user who creates the operation can configure the block requirements for specific types of operations.

The basic (parent) system contract was successfully registered and activated within the system. This contract is used to register system contracts for operation types, updating versions, and the operation parameter table of contents. It would be impossible to begin working with transaction-type contracts, maintain them, and monitor versions without starting with the fundamental contract. One of the most crucial phases in preparing to deploy the network is launching and testing system contracts. It is also required to begin open testing and sequentially check the execution of various types of operations. The network provides separate types of operations for different tasks. Each operation is carried out by its system contract's current, at the time of execution, version. For example, registering a new system user summons the register type's system contract. There are also distinct transaction types for: - updates to the user's personal profile - sending a message through the messaging system - Creating and updating a group or company - creating and updating an object - publications of public group news items - user authentication - personal digital signature registration - document and image registration - user system rewards - document signing between users - reputation updates - creating links - transfers between users of financial or other assets and other operations, of which there are more than 20 types in total. Contracts in the system can be of two types: system and user. Transaction type contracts are system-only. The contracts source code can be open-source or encrypted. Contracts are written in the elixir/erlang programming languages.

Resources are being reorganized in preparation for open testing. A full-fledged release will also be carried out in stages and will begin during testing. To test and complete release preparations, a combined approach is used: — System user blocks are used — fenomy.io is designated as a test node — the tracker on the test node displays real blocks that will be used following the full launch — except for the register type, all transactions on the test node are test transactions The node has been updated, and the configurations for initiating transactions under the system contract are being finalized. System user blocks, as well as the confirmation of other people's blocks, are being processed.

The Blockchain system's current state of development What has been launched successfully in test mode: - contract factory, system contracts, transaction contracts - version and parameter accounting system - revised operational mechanism - intelligent algorithm for determining importance values and weight calculation - API for obtaining random values and selecting a set of sets at random During the closed testing period, the following items were tested: - how the network performs when there are many concurrent parallel transactions of various types. - how system workers and ordinary users work together - the addition of documents, photographs, and other sorts of data to operations - network performance under various loads, including false requests Several issues were discovered and resolved during closed testing. We are currently updating the system and are preparing to launch open testing, in which anyone can participate. The rules and participation mechanism will be made public.

General network operations testing Blocks tab A list of the blocks received by the network. Transaction tab Register type successful transactions. The transaction includes only one operation for creating a new entity: registering a new user. Finance type transactions in real time. The transaction is made up of several operations. To execute a transaction, the required number of block validations selected for the transaction must be met. Workers tab - a list of all workers, sorted by reputation. - randomly chosen worker data, his created and confirmed blocks. In result: Confirmed issues and bug fixes that have been brought to our attention during the testing process. Stable node operation across all operation types. What is next: We are preparing for closed testing with existing system users.

Update The two-part Live conference will begin at 17:15 UTC on Thursday, August 31, 2023. The agenda will remain the same, but there will be some additional news from the last few days. Invitations to the conference's public portion will be sent via the Fenomy newsletter. The second private section of the conference will be accessible via a personal invitation and a private link. We'll see you there!

Update The two-part Live conference will begin at 17:15 UTC on Thursday, August 31, 2023. The agenda will remain the same, but there will be some additional news from the last few days. Invitations to the conference's public portion will be sent via the Fenomy newsletter. The second private section of the conference will be accessible via a personal invitation and a private link. We'll see you there!