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":93,"date":"2023-05-31T14:39:46","date_gmt":"2023-05-31T12:39:46","guid":{"rendered":"https:\/\/prodtest.hacken.ai\/blog\/?p=93"},"modified":"2023-05-31T18:04:56","modified_gmt":"2023-05-31T16:04:56","slug":"letter-to-community-from-dyma-budorin","status":"publish","type":"post","link":"https:\/\/site.hacken.ai\/blog\/?p=93","title":{"rendered":"Letter to Community from Dyma Budorin"},"content":{"rendered":"\n

Dear Hacken fam,<\/p>\n\n\n\n

I feel inspired by the transformations we are going through. This year was challenging, but even under such circumstances, we exceeded the goals that we set back in 2021. Hacken continues rapidly growing in 2022: our revenue increased by 166%, we gained +537 new clients, and 0 smart contracts audited by our team were hacked. But it\u2019s not today\u2019s topic.<\/p>\n\n\n\n

In this letter, I want to express gratitude to you, our community, our main treasure. With your support, we managed to build the Web3 cybersecurity market leader. I always say that HAI holders are our key stakeholders, and the HAI token is a lifetime liability for the Hacken team, so we have to work hard to repay the trust we have received.<\/p>\n\n\n\n

Another important task for this year was to find a way to merge the interests of Hacken equity stakeholders and HAI holders. So today, we are starting this journey with the first step \u2014 the hDAO<\/a> creation. How did we get there? Let us recall the history.<\/p>\n\n\n\n

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

ICO & Hacken Brand Growth Era, 2017\u20132019<\/strong><\/h2>\n\n\n\n

We used to be a small but very ambitious team in 2017, mostly positioning ourselves as crypto-oriented white-hat hackers. We were working with white-hat hackers worldwide and organized the event visited by Steve Wozniak. Our team visited industry conferences, negotiated partnerships with key industry players, and reached projects to deliver our cybersecurity services.<\/p>\n\n\n\n

2017 was a year of crazy ICOs launches. One could easily collect tens of millions of USD during an ICO. As for that time, the HKN (former \u2014 HAI) ICO was pretty modest and raised $4 million. Looking back to last year and seeing crypto projects crushed, I\u2019m even more sure it was the right decision to be focused on the product. People were always primary for us, but we did not use this power to the fullest. It was time to build expertise and let the industry know about it.<\/p>\n\n\n\n

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

Beginning of Hacken Ecosystem Era, 2020\u20132021<\/h2>\n\n\n\n

In that period, there was a crypto boom. Both mature projects and newcomers enjoyed high popularity among investors and crypto enthusiasts worldwide. Hacken was building the community around the HAI token, enhancing its utility with the released HackenAI application and launches of the HAI membership, hVPN, and hPass applications (still, both are used by HAI holders for free).<\/p>\n\n\n\n

We started organizing family-atmosphere events like Blockchainhackers and Defi Retreats and talking to the community through AMA sessions. To elevate cybersecurity in Web3, we established the Hacken Foundation, which supported the launches of OneArt, HAPI, disBalancer, and PureFi. HAI token holders could farm other cybersecurity tokens with HAI. That time was remarkable as the DeFi boom led to the token\u2019s utility revolving around farming and speculation on the token price.<\/p>\n\n\n\n

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

russian War and New Reality Era, 2022<\/h2>\n\n\n\n

In February 2022, the community migrated to Discord and became more mature. Then the worst forecasts came true \u2014 ruzzia invaded Ukraine, our homeland. HAI holders started selling their tokens due to fear of the possible future. Our decision to block access to our apps for russian users also added some selling pressure, but it was a fundamental thing to be made. Anyway, we had total control over the situation. A few days later, we started fighting on the cyber front by DDoSing ruzzian propaganda websites together with the disBalancer tool, Liberator. We made a product that hundreds of thousands of people use, which helps Ukrainians survive the horrors of war. Now, Liberator continues to work separately from us.<\/p>\n\n\n\n

I\u2019m grateful to everyone from our community who appreciated our decision and actively supported us during that time of uncertainty.<\/p>\n\n\n\n

2022 was hard not only for Ukrainians but for millions of crypto users. The collapse of Luna, 3ac, and FTX has led to the evaporation of trillions of USD. Speculative tokenomics are still crushing. Teams without revenue and products used by their communities are shutting their operations.<\/p>\n\n\n\n

2022 was the time to think strategically. We did very well with the B2B market share increase. But what about B2C? What is the perfect community we want to build? What is the portrait of the Hacken holder in 2025 we want to see? What is on his mind? Is he bothered about another IDO, farming opportunity, or seeking airdrops? No. We want to build a different community.<\/p>\n\n\n\n

Our role model community member in 2025 will:<\/strong><\/h2>\n\n\n\n