Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the reading-time-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /usr/html/blog/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":142,"date":"2023-05-31T17:44:00","date_gmt":"2023-05-31T15:44:00","guid":{"rendered":"https:\/\/prodtest.hacken.ai\/blog\/?p=142"},"modified":"2023-05-31T17:44:00","modified_gmt":"2023-05-31T15:44:00","slug":"trust-army-beta-key-results","status":"publish","type":"post","link":"https:\/\/site.hacken.ai\/blog\/?p=142","title":{"rendered":"Trust Army Beta: Key Results"},"content":{"rendered":"\n

<\/p>\n\n\n\n

The development of Trust Army 1.0 is on its track. This week, we released the first Development Update to keep you informed about the tasks completed during the last sprint. While the Dev Team continues to bring us closer to the full release, let\u2019s oversee the main results achieved during the Beta version operation, which ended on March 27.<\/p>\n\n\n\n

Trust Army Beta, also the MVP, was a pivot assignment set designed to make users quick-start at Trust Army, test the platform functionality, and try their hand at first blockchain data research. The Beta version is designed to identify bottlenecks, test hypotheses, and consider its findings in the full version.<\/p>\n\n\n\n

<\/p>\n\n\n\n

The main test objectives of Trust Army Beta were to:<\/strong><\/h2>\n\n\n\n