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":103,"date":"2023-05-31T15:10:58","date_gmt":"2023-05-31T13:10:58","guid":{"rendered":"https:\/\/prodtest.hacken.ai\/blog\/?p=103"},"modified":"2023-05-31T18:08:06","modified_gmt":"2023-05-31T16:08:06","slug":"hai-etd-2-0-market-buys-liquidity-adds-and-burns","status":"publish","type":"post","link":"https:\/\/site.hacken.ai\/blog\/?p=103","title":{"rendered":"HAI-ETD 2.0: Market Buys, Liquidity Adds, and Burns"},"content":{"rendered":"\n

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

Last year Hacken released the first cybersecurity stablecoin that bakes time for auditors\u2019 teamwork \u2014 ETD (Engineering Team Day). It delivers HAI as a B2B utility, connecting the Hacken business services with the HAI token. B2B clients and partners purchase HAI from the market, convert them into ETD and use it as payment for Hacken.io<\/a> services and products.<\/p>\n\n\n\n

In fact, a Web3 cybersecurity market leader with 1,200+ clients and $9+ million in annual revenue merges its business success with its token.<\/p>\n\n\n\n

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

ETD Utility<\/h2>\n\n\n\n

ETD prospective holders are VC companies, cryptocurrency accelerators, L1 protocols, and blockchain companies that require numerous smart contract audits to maintain operations securely.<\/p>\n\n\n\n

For 1 ETD, they get 1 workday from a Hacken Auditor team of 4 people. Its price is $4,500, representing the expenditures of this team workday. The total amount of ETDs is limited to 1,000 due to the Hacken scheduled workload and person-day available in a year.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Introducing Innovative ETD 2.0 Smart Contract<\/h2>\n\n\n\n

ETD 2.0 purchase, minting, and usage models became much more mature to transfer all B2B success into HAI value. To reflect community and client feedback, we have designed an ETD 2.0 smart contract that allows clients to buy ETD at a fixed HAI\/USDT price.<\/p>\n\n\n\n

Innovative ETD solution merges Hacken business growth success with 3 pillars of successful tokenomics:<\/strong><\/h3>\n\n\n\n