<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hacken.AI on Medium]]></title>
        <description><![CDATA[Stories by Hacken.AI on Medium]]></description>
        <link>https://medium.com/@hackenclub?source=rss-a70d0274ef3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1gXMLQ7oitcUoREG42La4Q.png</url>
            <title>Stories by Hacken.AI on Medium</title>
            <link>https://medium.com/@hackenclub?source=rss-a70d0274ef3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:26:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hackenclub/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[The Hacken Group IPO preparation continues.]]></title>
            <link>https://hackenclub.medium.com/the-hacken-group-ipo-preparation-continues-28732bad7b7d?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/28732bad7b7d</guid>
            <category><![CDATA[real-world-asset]]></category>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[rwa]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[public-listing]]></category>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 11:12:16 GMT</pubDate>
            <atom:updated>2026-03-04T11:12:16.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*505T4_itDmQ7UqrrcMtmbw.png" /></figure><p>The Hacken Group IPO preparation continues. An extraordinary amount of work has already been completed, with further intensive efforts ahead across governance, reporting, compliance, and long-term transparency. This is what serious public-market preparation looks like; it’s one of the most intensive and rewarding business processes a company can undertake.</p><p>In line with our commitment to transparency and compliance with global regulations and standards, we clearly state the following, which supersedes any previous statements:</p><p>HAI is a utility token and has no features or rights as a security. It does not represent equity, ownership, voting rights, dividends, or any other claim on Hacken Group or any of its subsidiaries, and is intended solely for use within its designated ecosystem and related products or services.</p><p>Our strategy remains unchanged. However, at this stage, we cannot make premature promises that could jeopardize the IPO process.</p><blockquote>Therefore, we are revising the wording of our previous communications.</blockquote><p>Any transactions involving executive shareholdings, if and when they occur, will be conducted independently, in accordance with applicable law, and without reference to token ownership or participation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28732bad7b7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The $HAI Advantage Period]]></title>
            <link>https://hackenclub.medium.com/the-hai-advantage-period-98d8298c6404?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/98d8298c6404</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 16:06:18 GMT</pubDate>
            <atom:updated>2026-01-15T13:28:09.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*banRXcVESi0Kz5beLYA8RA.jpeg" /></figure><p><em>Holder-Only Brief</em></p><p><strong>HAI Group is charting a course that no project has ever navigated.</strong> In 2017, Hacken began as an ICO startup fresh off a pitch competition win. Eight years later, we stand between our wild crypto origins and the regulated world, choosing to become a public company through a crypto IPO. Our case is the first of its kind in the industry, and it requires changes.</p><p>Behind the scenes, $HAI was steadily preparing to divide into two separate entities.</p><p>But the market still prices $HAI as a single company with one future. And that’s yesterday’s news.</p><p>Today’s $HAI effectively represents 2025’s two high-growth assets at 2023’s consolidated price.</p><p><strong>As HAI Group transitions to a public company, the $HAI token will no longer be supported after our crypto IPO. Instead, new asset classes will fuel HAI Group’s growth and the expansion of its on-chain ecosystem.</strong></p><h3>The Structural Why</h3><p>Over the past eight years, since the $HKN ICO, Hacken matured into the HAI group: we expanded into regulated security markets, AI auditing infrastructure, security prediction, and CORE3’s global self-regulatory framework. The token, backing it all, must evolve too, as it cannot simultaneously represent:</p><ul><li><strong>ownership</strong> of a regulated company, and</li><li>liquidity-aligned <strong>utility </strong>layer powering access and interactions across the industry.</li></ul><p>By splitting the $HAI token into two separate assets, we can resolve the paradox.</p><p>First, and most importantly, HAI Group becomes a public company, offering a new class of tokenized RWA in which the price is set not by buybacks but by the company’s real value.</p><p>Secondly, we bring to market a utility token aligned with 2026 standards, not 2020.</p><p>The success of both assets is based on three core principles: transparency, accountability, and business growth.</p><p>Thus, if you hold $HAI right now, you’re in a unique spot. You have one token that’s about to become two. Once they split, that’s it. You’ll either own it before they are priced independently, or you’ll have sold the chance to.</p><h3>The Big Plays Around Two Big Assets</h3><p>During the transition period, $HAI holders have the whole game to play, not just one role to stick to forever. The details of the transition will be shared later; for now, we will introduce you to both classes of post-split assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKge8yE8jgD0wV5cSDAiIg.png" /></figure><h3><strong>1. The Security Direction — Tokenized Shares of HAI Group</strong></h3><p>A <strong>fixed percent of HAI Group</strong> will be allocated exclusively to $HAI holders for conversion.<br>This will be the <strong>only token-based path</strong> to acquire equity in HAI Group — ever.</p><ul><li>This will be a <strong>one-time equity allocation</strong> for $HAI token holders.</li><li>HES (Hacken Equity Shares) holders already have <strong>1:1 secured</strong> equity in HAI Group; nothing changes for them except the upgrade to the new Security Token on IPO.</li><li>Conversion pricing for this phase will differ from that in the previous structured equity phase (HES Round) and will depend on HAI Group’s valuation as well as the size of allocation.</li><li>Tokenized shares will be represented as an RWA asset in the crypto IPO category, the same one that OKX, Kraken, and Ledger plan to file.</li><li>All converted Security allocations will be <strong>subject to a lock</strong> until future milestones are defined in the official roadmap (timing, structure, and conditions will be disclosed later).</li><li>Allocation will be <strong>first-come, first-served</strong> within the pool and subject to minimum amounts and HAI membership-based conditions (LVL2/LVL3).</li><li>This route opens access to post-IPO trading under regulated conditions, where the valuation will reflect not only the core entity, but the full weight of the HAI Group holding.</li><li><strong>As the entire process is regulated, full KYC will be required.</strong></li><li>Once this pool is filled or the deadline passes, there will be <strong>no further opportunity</strong> to become a shareholder of HAI Group on a token conversion basis.</li></ul><p>To prepare for the crypto IPO, HAI is currently undergoing financial audits as well as operational and legal restructuring; once complete, we’ll be able to publish a <strong>pre-IPO prospectus for investors</strong>. Future equity access, if any, will follow the same terms as traditional instruments trading/investment.</p><h3>2. The Utility Direction (DEX-Only)</h3><p>A new token designed for transparency, liquidity, and product interoperability across all current and future HAI utilities (Hackpot, HAI Rounds, DYOR / Trust Army, AI Audits, CORE3, and future HAI Group utilities)</p><ul><li><strong>DEX-focused </strong>— the asset is mainly focused on enriching HAI Group’s on-chain utilities, creating demand for products and services, instead of encouraging speculation.</li><li>The utility token will be subject to lock and vesting after the swap.</li><li><strong>Liquidity-focused</strong> asset with a mechanism for DAO-controlled inflation rates.</li><li>One of the features will allow holders to bridge the value of external assets to fuel HAI Group’s ecosystem’s growth.</li><li>Detailed mechanics and conversion rates will be described in future communication.</li></ul><p><strong>The design goal is simple:</strong><br>The utility token’s tokenomics creates natural alignment, where long-term holding and use of the token are the most rational and beneficial choices for participants.</p><p>Technical diagrams, contract logic, and exact conditions will be provided in the <strong>Whitepaper</strong>, <strong>Tokenomics,</strong> and <strong>Swap Documentation</strong>.</p><p>This asset will be built as a <strong>DEX-native</strong> asset with visible liquidity, structured unlock mechanics, and optional fast-track unlocks tied to liquidity commitments.</p><h3>The Schedule</h3><p>All elements of the transition will be communicated step-by-step. This announcement is a preliminary overview; the complete roadmap, technical parameters, and conversion rules will be presented publicly in the upcoming releases.</p><ol><li><strong>The announcement </strong>— <strong>Dec 31, 2025<br></strong>The official declaration: $HAI’s last epoch as a single token.</li><li><strong>Roadmap reveal</strong> — <strong>Q1, 2026<br></strong>Visual map of the split: equity route, utility route, mechanics.</li><li><strong>Code &amp; numbers</strong> — <strong>Q1, 2026<br></strong>Lightpaper, vesting &amp; liquidity logic.</li><li><strong>Swap opens</strong> — <strong>Q2, 2026<br></strong>Holders start choosing allocations. Supply begins to migrate.<br>The market will see flows. You’ll know what kind of hands you’re surrounded by.</li><li><strong>Legacy $HAI Sunset</strong> — <strong>End of Q2, 2026<br></strong>$HAI stops being supported.<br>From that day on, the world only talks about <strong>HAI Group equity</strong> and <strong>DEX-native utility token</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfwNtbUF8MX0K7M-cvqIhA.png" /></figure><h3>What This Moment Represents</h3><p>Right now, HAI Group is pioneering the industry as a company that began as an ICO and is now filing a crypto IPO<strong>.</strong> No crypto projects have holders that started as ICO participants and ended up with equity RWAs.</p><p>Thus, the split is your opportunity to secure long-term participation in the ecosystem and the opportunity to define both your growth trajectory and your potential exit pathway.</p><p>Now, each asset can be valued for what it actually is. The regulated security company can be valued like a tech stock. The future utility token can be valued for the benefits it provides. The mechanics are built to reduce sell pressure and make long-term holding the logical choice.</p><p>For current $HAI holders, this is the framework for a cleaner start — own the company, or own the on-chain ecosystem. It’s the point where the market finally catches up to the building that’s already been done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98d8298c6404" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The DYOR-Ready Playbook: How to Earn Trust Faster and Cheaper Than Paid Hype]]></title>
            <link>https://hackenclub.medium.com/the-dyor-ready-playbook-how-to-earn-trust-faster-and-cheaper-than-paid-hype-032a8c6cb47f?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/032a8c6cb47f</guid>
            <category><![CDATA[dyor]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[influencer-marketing]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 11:56:08 GMT</pubDate>
            <atom:updated>2025-09-26T11:56:08.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QDziFuGBW4uMlv9HXDzIw.png" /></figure><p>A new Web3 project launches with a large marketing budget, paying influencers and flooding social media with hype. However, in a market marked by scepticism, the most likely outcome will be inundating your community with short-term speculators, who will leave the project within a week without any positive price movement.</p><p>Every project founder must ask themselves a fundamental question: “What kind of community do we actually want to build?” If you’re reading this, it’s clear you’re not looking to attract short-term gamblers just to launch and exit. You’re aiming higher: to build a lasting crypto project with a core community of crypto-fluent, long-term believers who will actively support it.</p><p>For that specific goal, the traditional “hype-first” approach is one of the most expensive and inefficient strategies a project can take.</p><p>In this case, instead of preparing a marketing campaign in the pre-seed stages, Hacken recommends that Web3 builders initially focus on becoming ready for thorough community fundamental research.</p><h3>The DYOR-Ready Framework: The 5 Pillars of Transparency</h3><p>The most powerful strategy for building a lasting trust doesn’t hide in social media hype; it lies in proving that you have nothing to hide. Being “DYOR-ready” from day one builds a community of brand advocates more effectively and cheaply than any paid promotion. This playbook provides a framework for doing exactly that.</p><h3>1. Documentation: Does the Project’s Story Make Sense?</h3><p>After a quick look at a project’s website, the deep dive always starts with the documentation. Some might think that the whitepaper is a place where you include every concept trending right now and hope it will be successful when reviewed. But in reality, it must simply describe your business, its economy, and its technology. The perfect whitepaper example is <a href="https://ethereum.org/en/whitepaper/">Ethereum</a>.</p><p>Next is the roadmap, which should be treated just as your map for project development, not a wishlist of “would be nice to do” points.</p><p>Crucially, it should have a verifiable track record of past milestones that can be checked against on-chain data or market calendars. A history of shipping on time is one of the strongest signals a project can have.</p><p>Finally, there’s technical transparency. This means a clean, well-commented GitHub and, most importantly, a clear, easy-to-find list of all core smart contract addresses. If these contracts are difficult to find, it’s usually assumed there’s something to hide.</p><p>It all comes down to this: if the story a project tells in its documentation isn’t clear, credible, and verifiable, it will be dismissed before getting a real look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zjLsDJbBTFDhEiAZLzMYw.png" /><figcaption>Ethereum whitepaper fragment</figcaption></figure><h3>2. Tokenomics: Show Me the Vesting</h3><p>When it comes to tokenomics, the real story is found on-chain. Marketing narratives can say anything, but the blockchain data is the only immutable source of information.</p><p>The analysis begins with a simple question: why does this token exist? Is it essential for the protocol to function, or is it primarily a fundraising tool for insiders? A token without a clear, sustainable purpose is just exit liquidity waiting to happen.</p><p>After establishing purpose, the due diligence moves to the money trail. A simple pie chart doesn’t cut it. A proper analysis involves tracing the token from its creation at the Token Generation Event, following it to the primary multisigs, and then to every single allocation wallet — team, VCs, treasury, and so on. The best projects facilitate this by providing a clear map with block explorer links.</p><p>The most critical part of this on-chain verification is the vesting. The cliff period, the unlock schedule, and the distribution logic must all be examined. Any difference between the promises made in a whitepaper and what the vesting contract actually enforces is an absolute deal-breaker.</p><p>The investors’ goal here is to calculate future sell pressure from every unlocked token and to verify every promise made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vtExLXI7A2JTd8gT.png" /><figcaption>$UNI token release schedule</figcaption></figure><h3>3. Security: Audits, Bounties, and Who Can Rug You?</h3><p>Having the “Audited By ✅” badge on a project’s website is a plus, but that’s just the beginning of the conversation. The key thing to understand is that an audit is not a one-time event; it’s a reflection of an ongoing security culture.</p><p>A single token audit from a year ago might appear satisfactory, but what about the core smart contracts? The scope of the reports falls under the field of research. If the contracts have been revised, a new security audit is necessary. Savvy investors are not lazy, as their money is at stake — they will certainly verify whether the deployed code matches the audited code.</p><p>Being “DYOR-ready” also means having a running bug bounty. Even the greatest auditor might miss something that a 15-year-old white-hat hacker will find. A project doesn’t need a million-dollar prize pool to get started. Launching even a small bounty shows a real commitment to user security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*CFSLaFJsMAS-WDBl" /><figcaption>Example of valid audits page in project’s documentation</figcaption></figure><h3>4. On-Chain Integrity: Does the Project Practice What It Preaches?</h3><p>Who will track the flow of tokens from the project’s mint smart contract to the burn addresses to prove the tokens are really burned? Actually, any engaged enough investor will do that.</p><p>Their first check is basic hygiene: are all core protocol smart contracts verified on a block explorer?</p><p>From there, the forensic analysis of a project’s finances begins, tracing the entire on-chain history from the Token Generation Event.</p><p>This is why transparent projects make this process easy. They label their primary wallets using services like ENS — treasury.eth, team-vesting.eth, etc. — and provide direct links in their docs to the TGE and initial distribution transactions.</p><p>Most importantly, their treasury is managed professionally. Every transaction is public, and large, unexplained transfers to new anonymous wallets are one of the biggest red flags there is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/0*Dx6kARnXJEcE9So3" /><figcaption>How the on-chain data looks like on practice</figcaption></figure><h3>5. Team &amp; Governance: Who is Truly in Control?</h3><p>Ultimately, every investment in a decentralized project is a bet on the people behind it. A brilliant idea is worthless without a credible and responsible team to execute it, making the assessment of this human element crucial.</p><p>The due diligence process looks beyond simply checking if a team is “doxxed” and delves into their actual history. For example, a team of marketing professionals claiming to develop a new ZK protocol will face intense critique. A public track record on LinkedIn or GitHub relevant to the project mission is, on the other hand, a big plus. Past projects will also be examined — a record of success is highly valuable, while any links to failed or questionable projects are immediate red flags.</p><p>It all hinges on the human element. A public, credible team with transparent governance offers the strongest defence a project can have against failure. It demonstrates that real people with reputations on the line are dedicated to creating something lasting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaEg7aolUY5gGQJdITQSdQ.png" /><figcaption>Transparent team example</figcaption></figure><h3>The ROI of Transparency</h3><p>It’s easy to look at the crypto market and see a casino, but that’s only a snapshot. Even speculative traders learn to look closer at fundamentals, and a new wave of capital is arriving from Web2 demanding transparency and a clear future of the projects they invest in — they are used to playing the long game and to profit on it.</p><p>But the current situation looks more like a chaotic market, where it’s almost impossible for a new user to separate the real builders from scams because everyone appears the same.</p><p>In just Q1 2025, <a href="https://hacken.io/insights/q1-2025-security-report/">$2B was lost in DeFi</a>, which is 96% higher than in Q1 2024. Think of the newcomer who trusts the hype behind a new project, invests their savings, and gets rugged. They wake up to a dead token and a deleted Discord. They lose both the money and all the faith in Web3 and become its newest, loudest critic. This is what kills mass adoption.</p><p>Hacken’s solution to this problem is to train a new generation of DYOR experts through our Trust Army initiative. When you combine this newly DYOR-certified group with existing smart money, you get the highest-quality community a project could ever attract — the long-term believers and powerful advocates.</p><p>And you can’t win this audience with paid hype. You win them by being “DYOR-ready” — having a project that advocates for its real value, transparency, and openness. And that’s where transparency becomes the best marketing tool.</p><p>At the same time, being transparent and DYOR-ready makes B2B life of the project easier, as they have tons of ready data to show to VCs, launchpads, CEXs, grants and others.</p><h3>In a Market of Cults, Verifiable Truth Wins</h3><p>The playbook for launching a Web3 project is changing. In a maturing market, the old strategy of building trust with a massive marketing budget will no longer be effective.</p><p>The projects that will survive and define the next era of crypto will be those with the most verifiable integrity. This shift doesn’t just benefit investors; it raises the standard for the entire industry. If we want to onboard the next wave of retail users instead of creating more crypto horror stories that scare them away, this level of transparency is the only path forward. When projects are built for scrutiny from day one, they create a market where capital flows to substance, not just speculation — and that is how we build the trust needed for mass adoption.</p><p>Preparing for rigorous, community-led due diligence isn’t the easy path, but it’s the only one that leads to lasting trust.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=032a8c6cb47f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust Army 1.0 Public Release: Meet Role changes, Leaderboards, Raffles, and GEM economy]]></title>
            <link>https://hackenclub.medium.com/trust-army-1-0-public-release-meet-role-changes-leaderboards-raffles-and-gem-economy-4b026a054a6d?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b026a054a6d</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 09:36:43 GMT</pubDate>
            <atom:updated>2025-08-25T09:36:43.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kR1RtfZwvPOnAoZl" /></figure><p>When we launched the Alpha Intelligence community, our goal was to build a space dedicated to real, community-driven Web3 research.</p><p>Today, the Alpha Intelligence community has grown into a powerful force, with hundreds of active researchers making a real impact on Web3 transparency. Since our soft launch, we have attracted 4,348 users from 16 countries, who have received more than $10,000 in rewards for their high-quality contributions to creating a safer ecosystem.</p><p>This growth is why it’s the perfect time to evolve the way Alpha Intelligence works. We’ve listened to your feedback, and now we are releasing a major update where the research process will become more professional, quality work will be better rewarded, and experience will matter even more.</p><p>With the official launch of our Trust Army Certification Platform, we introduce significant changes for the Alpha Intelligence community. The article serves as a guide, breaking down changes in the DYOR Alpha Intelligence roles and new GEM economics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*50qQbSb1M1-TGpGB" /></figure><h3>SoulBound DYOR Certificates</h3><p>For the many community members who have been patiently waiting, the time has finally come. The DYOR Certificate is here, and we made everything so it is worth the wait.</p><p>The DYOR Certificate is presented in the form of a non-transferable <strong>SoulBound Token (SBT)</strong> that serves as verifiable proof of a wallet holder’s expertise in Web3 research methodology. For its holders, the SBT certificate marks the beginning of a portable, on-chain reputation that is tied to a specific, high-value skill.</p><p>Within the Hacken ecosystem, the DYOR Certificate is now the definitive standard for identifying our expert contributors. As a direct reward for their expertise, Certificate holders receive a 1.25x multiplier on their $stHAI minting rate. This gives our skilled researchers faster access to private investment rounds and a greater stake in the ecosystem.</p><p>Our vision, however, extends across the entire DeFi market.</p><p>As the industry moves towards a greater emphasis on on-chain reputation, credentials like this SBT will become really valuable. It is designed to be a signal to other projects, DAOs, and communities — a clear indicator that the holder is a knowledgeable and verified contributor worthy of trust and better kind of opportunities.</p><h3>DYOR Certificate Is Now Essential</h3><p><strong>❗ To keep the DYOR Champion role and unlock the Research2Earn benefits in the new system, holding the DYOR Certificate is a mandatory requirement.</strong></p><p>All current Champions will have a two-week grace period (until <strong>September 8th, 2025</strong>) to complete the Trust Army course and mint their certificate. During this time, research rewards accrual will be paused until certification is complete.</p><h3>Alpha Intelligence Role Changes</h3><p>We’re introducing a clear three-stage career path for our researchers. It’s a merit-based system where you grow from a beginner researcher to a paid expert. Each tier has transparent requirements and offers rewarding benefits.</p><h4>Stage 1: DYOResearcher</h4><ul><li><strong>Requirements:</strong> Complete the <a href="https://app.galxe.com/quest/hackenai/GCq1Nt1cst">Galxe educational course</a> to receive the role automatically.</li><li><strong>Privileges:</strong> Submit up to two reports per week to practice the methodology.</li><li><strong>Rewards:</strong> Earn GEMs to use for advancing to the next level.</li></ul><h4>Stage 2: DetectiveYOR</h4><ul><li><strong>Requirements:</strong> DYOResearcher role, 2+ validated reports, and 35 GEMs to spend on the upgrade.</li><li><strong>Privileges:</strong> Access “DYOR NEEDED” projects and earn a spot on the community leaderboards.</li><li><strong>Rewards:</strong> Earn higher amounts of GEMs for your reports.</li></ul><h4>Stage 3: DYOR Champion</h4><ul><li><strong>Requirements:</strong> DetectiveYOR role, 8+ validated reports, 70 GEMs to spend, and the official <strong>DYOR Certificate</strong>.</li><li><strong>Privileges:</strong> Get full research access and the responsibility of validating reports from other members.</li><li><strong>Rewards:</strong> Receive $HAI payouts for your expertise — $10 for standard reports and $12 for “DYOR NEEDED” projects.</li></ul><h3>Meet the New GEM Economy</h3><p>With this update, GEMs will become a currency for the Alpha Intelligence community, with more ways to earn and a new set of use-cases.</p><h3>Earning GEMs</h3><p>You’ll earn a base amount of GEMs for every validated report, with additional bonuses that reward quality work and active community participation.</p><p><strong>Base Rewards</strong></p><ul><li><strong>5 GEMs</strong> for each validated standard research report.</li><li><strong>7 GEMs</strong> for each validated “DYOR NEEDED” research report.</li></ul><p><strong>Bonus Rewards</strong></p><ul><li><strong>+1 GEM</strong> for reports that get high community engagement (10+ GEM reactions).</li><li><strong>+2 GEMs</strong> for being selected as “Research of the Month.”</li><li><strong>+5 GEMs</strong> for being an active community reviewer (giving feedback on 10+ reports from other members within 10 days).</li></ul><h3>Using GEMs</h3><p>The biggest change to GEMs is their new utility. They become a flexible asset with a range of new use-cases designed to reward your contributions.</p><ul><li><strong>Enter the Raffle:</strong> Use GEMs as tickets for our quarterly raffle, with a chance to win a share of the <strong>10,000 $HAI</strong> prize pool.</li><li><strong>Claim Priority Slots:</strong> (Champions Only) Use GEMs to reserve “DYOR NEEDED” project slots.</li><li><strong>Appeal a Decision:</strong> Spend GEMs to request a second review on a rejected report.</li></ul><p>These utilities will <em>be released gradually</em>, allowing researchers to spend GEMs once they have accumulated enough.</p><h3>Seasonal Rewards &amp; Recognition</h3><p>We’re moving away from a simple routine of just submitting reports and praying for rewards. With Seasons, we introduce a competitive ladder where your GEMs directly reflect your rank and reputation.</p><p>A higher GEM count means a higher position on the leaderboard, earning you more visibility and respect within the community.</p><p><strong>Loyalty Bonuses:</strong></p><p>We are also adding new bonuses to reward community spirit:</p><ul><li><strong>Sponsorship:</strong> Earn +2 GEMs on the first three validated reports from a researcher you invited.</li><li><strong>Comeback:</strong> Get +3 GEMs on your next five reports after returning from an absence of over one month.</li></ul><p><strong>The Rules of the Game</strong></p><ol><li><strong>Stay Active Researcher:</strong> Accounts with no submissions for 30 days will receive a -5 GEM penalty, with further deductions for each additional inactive week.</li><li><strong>One Person, One Account:</strong> Our zero-tolerance policy for multi-accounting remains. Any user found trying to cheat with multiple accounts will have all of them permanently banned.</li></ol><h3>Conclusion</h3><p>Our goal is to make Web3 a more trusted space. We’re doing that by building a decentralized research ecosystem that can serve as the standard for the entire industry. The vision is simple: a future where any investor, before putting money into a new project, can check the Alpha Intelligence platform to get a clear, unbiased view of its real fundamentals.</p><p>These updates are how we build that future. A trusted platform can only be built by a community of trusted experts, and this new system with a clear career path and real rewards is designed to do just that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b026a054a6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing stHAI — access private rounds]]></title>
            <link>https://hackenclub.medium.com/introducing-sthai-access-private-rounds-97c5dadb1cdb?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/97c5dadb1cdb</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 15:20:00 GMT</pubDate>
            <atom:updated>2025-08-05T15:20:21.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iFqTROTBW-EIQNC0IRwxog.jpeg" /></figure><h3>Introducing stHAI — access to private rounds</h3><p>The Web3 space is overflowing with <strong>investment opportunities</strong> — but only a few are worth your time and capital. Finding them early and verifying their credibility is where the real alpha lies.</p><p><strong>Hacken’s network</strong> — built since 2017 — spans thousands of audited projects, launchpads, and protocols, giving us <strong>first-mover access</strong> to private rounds long before they hit the public radar. Combined with the <strong>DYOR community</strong>, which researches these opportunities in-depth, we now have something rare in crypto:</p><p><strong><em>exclusive deals that are deeply vetted, not hyped.</em></strong></p><p>Until today, this access was limited to internal circles.<br> <strong>stHAI changes that — putting Hacken-curated deals in the hands of every $HAI holder.</strong></p><h3>What is stHAI?</h3><p>stHAI is an <strong>ERC20 token on Base</strong>, minted when you stake $HAI through<a href="https://linktr.ee/hAIapp"> the hAI App</a>.<br>It’s not designed for yield. It’s designed for <strong>access</strong> — specifically, guaranteed seats in <strong>Hacken Rounds</strong>, our private Web3 deals platform.</p><p>Here’s the core mechanic:</p><ul><li><strong>1,000 HAI staked = 1 stHAI per month</strong> (baseline, no boosts).</li><li>Choose <strong>6, 12, or 18 months</strong> lock — longer means higher multiplier.</li><li>Boost your minting rate via <strong>Membership level, DYOR Certificate, or HES</strong> (the highest role applies).</li></ul><p>stHAI works like a <strong>ticket system</strong>: each token represents a share of allocation in upcoming deals, usually <strong>0.01% per stHAI</strong> (subject to deal terms). The more you stake and the higher your role, the more access you unlock.</p><p>Unlike typical staking tokens:</p><ul><li>There’s <strong>no instant shortcut</strong> — minting happens monthly.</li><li><strong>Supply is naturally limited</strong> — boosting long-term demand.</li><li>Non-HAI holders interested in hot rounds will have two choices: <strong>wait and stake</strong> or <strong>trade for stHAI</strong> from those who already hold it — creating new opportunities for raffles, peer trades, and community-driven mechanics.</li></ul><h3>The Core Mechanic: 1,000 HAI = 1 stHAI per Month</h3><p>stHAI is minted in a <strong>simple, predictable way</strong>:</p><ul><li>For every <strong>1,000 HAI you stake</strong>, you mint <strong>1 stHAI per month</strong>.</li><li>Lock periods: <strong>6, 12, or 18 months</strong> — longer lock = higher time multiplier.</li></ul><p><strong>Example</strong>:</p><ul><li>1,000 HAI for 6 months = 6 stHAI (baseline, no boosts)</li><li>1,000 HAI for 12 months = 18 stHAI (1.5× boost)</li><li>1,000 HAI for 18 months = 24 stHAI (2× boost)</li></ul><p>This means <strong>minting is a process</strong>, not a one-time claim. You build stHAI month by month — and that matters because:</p><ul><li><strong>You can’t shortcut demand</strong> — new entrants can’t just buy HAI today and instantly flood a hot round tomorrow.</li><li><strong>Existing holders have the edge</strong> — they’re already minting and can choose to use, trade, or raffle their stHAI on their terms.</li></ul><h3>How Boosts Work</h3><p>stHAI minting scales with your <strong>ecosystem role</strong> and <strong>lock duration</strong>.<br>Boosts don’t stack — your <strong>highest role</strong> applies (Membership LVL3, DYOR Certificate, or HES).</p><p><strong>Formula</strong></p><p>(HAI staked ÷ 1,000) × months × role multiplier × time multiplier = stHAI minted</p><p><strong>Role Multipliers (Baseline)</strong></p><ul><li><strong>Membership LVL1</strong>–1.0×</li><li><strong>Membership LVL2</strong>–1.25×</li><li><strong>Membership LVL3</strong>–1.5×</li><li><strong>DYOR Certificate</strong> — 1.25×</li><li><strong>HES</strong> — 2.0×</li></ul><p><strong>Time Multipliers</strong></p><ul><li>6 months — 1.0×</li><li>12 months — 1.5×</li><li>18 months — 2.0×</li></ul><p><em>(Max combined multiplier = 4×, e.g., HES with 18-month lock.)</em></p><h3>Two Scenarios</h3><p><strong>Scenario 1: Newcomer, Membership LVL1, 6-Month Stake</strong></p><ul><li>Stake: <strong>10,000 HAI</strong></li><li>Role: <strong>LVL1 (1.0×)</strong></li><li>Lock: <strong>6 months (1.0×)</strong></li></ul><p><strong>Calculation:<br></strong> 10,000 ÷ 1,000 × 6 × 1.0 × 1.0 = <strong>60 stHAI</strong></p><ul><li>After 6 months: <strong>60 stHAI minted</strong></li><li>Approx allocation: <strong>0.6% seat</strong> in a Hacken Round (60 × 0.01%)</li></ul><p>For a $100,000 allocation round, that equals <strong>$600 guaranteed access</strong> — no lottery, no gas war.</p><p><strong>Scenario 2: HES Holder, 18-Month Stake</strong></p><ul><li>Stake: <strong>50,000 HAI</strong></li><li>Role: <strong>HES (2.0×)</strong></li><li>Lock: <strong>18 months (2.0×)</strong></li></ul><p><strong>Calculation:<br></strong> 50,000 ÷ 1,000 × 18 × 2.0 × 2.0 = <strong>3,600 stHAI</strong></p><ul><li>After 18 months: <strong>3,600 stHAI minted</strong></li><li>Approx allocation: <strong>36% seat</strong> in a Hacken Round (3,600 × 0.01%)</li></ul><p>For a $100,000 allocation round, that equals <strong>$36000 guaranteed access</strong> — purely from staking $HAI.</p><p>These examples show two key points:</p><ol><li><strong>Even newcomers</strong> can access meaningful allocations by starting small and staking consistently.</li><li><strong>Higher roles and longer locks</strong> unlock disproportionately larger seats, rewarding long-term commitment to the ecosystem.</li></ol><h3>Why This is Big</h3><p>Web3 is saturated with <strong>hype-driven deals</strong> — but true early access to projects vetted by real research communities is rare. stHAI changes this dynamic in three key ways:</p><p><strong>1. Real Access, Not Hype</strong></p><p>stHAI grants <strong>guaranteed allocations</strong> in <strong>Hacken Rounds</strong>, which feature projects deeply analyzed by the <strong>DYOR (Trust Army) community</strong> — filtering out noise and surfacing only high-potential opportunities.</p><p><strong>2. Scarcity Built In</strong></p><p>Minting is <strong>gradual</strong>: 1,000 HAI = 1 stHAI/month (boosted by role/lock).<br>There’s <strong>no instant shortcut</strong> — newcomers can’t flood a round by buying HAI today. This creates <strong>natural scarcity</strong> and rewards early and consistent stakers.</p><p><strong>3. Expanding Deal Flow</strong></p><p>Hacken’s network spans <strong>audited clients, partners, and launchpads</strong>. With the formation of <strong>HAI Group</strong>, access widens even more: exclusive rounds across security, DeFi, RWA, and AI — all gated by stHAI.</p><h3>What You Can Do with stHAI</h3><p>stHAI isn’t just a static token — it’s a flexible <strong>access instrument</strong> you can use strategically:</p><p><strong>1. Enter Private Rounds</strong></p><p>Claim your guaranteed allocation in Hacken-curated deals — <strong>no lottery, no waitlist, no gas war</strong>.</p><p><strong>2. Trade or Raffle During Demand Spikes</strong></p><p>Because stHAI is an <strong>ERC20 on Base</strong>, you can <strong>transfer, trade, or raffle it</strong>.</p><ul><li>Hot round announced? <strong>Non-HAI holders will chase stHAI</strong> to get in.</li><li>You decide whether to <strong>use it for yourself</strong> or <strong>sell it to the highest bidder</strong>.</li><li>Raffles and giveaways can also <strong>grow your personal audience</strong> while offloading extra stHAI.</li></ul><p><strong>3. Leverage Special stHAI-Only Deals</strong></p><p>Some allocations will be <strong>exclusively stHAI-based</strong> — no USDC, no HAI needed. If you’re minting consistently, you’ll have an advantage over those scrambling to enter.</p><p><strong>4. Stack for Bigger Plays</strong></p><p>stHAI accumulates over time. A newcomer starting small can build meaningful access month by month — or choose to <strong>upgrade their role / lock period</strong> to accelerate minting and aim for <strong>larger seats</strong> in future rounds.</p><h3>Quick Start: How to Get Your stHAI</h3><p>Getting started is straightforward — whether you already hold HAI or are just entering the ecosystem.</p><ol><li><strong>Get $HAI</strong></li></ol><ul><li>If you’re new, acquire $HAI on supported exchanges (VeChain + LayerZero OFT).</li><li>Already a holder? Move your tokens into the <strong>Base</strong>.</li></ul><p><strong>2. Stake in the hAI App</strong></p><ul><li>Choose your <strong>lock period</strong> (6, 12, or 18 months).</li><li>Longer lock = higher multiplier.</li><li>Baseline: <strong>1,000 HAI = 1 stHAI/month</strong> (boosted by your highest role).</li></ul><p><strong>3. Mint stHAI Monthly</strong></p><ul><li><strong>You will receive stHAI for the first month of staking — IMMEDIATELY.</strong></li><li>Watch your stHAI grow over time — no inflation, no shortcuts.</li><li>Boost minting with <strong>higher Membership</strong>, <strong>DYOR Certificate</strong>, or <strong>HES</strong>.</li></ul><p><strong>4. Enter Hacken Rounds</strong></p><ul><li>Use stHAI for guaranteed seats in private Web3 deals curated by the DYOR community.</li><li><strong>Optional:</strong> trade or raffle stHAI when demand spikes around hot rounds.</li></ul><p><a href="https://apps.apple.com/app/id1501384789">Download hAI App (iOS)</a> |<a href="https://play.google.com/store/apps/details?id=com.hackenai.hackenaiapp&amp;pli=1"> Android</a></p><h3>Final Word &amp; TL;DR</h3><p>The launch of stHAI marks a shift for $HAI holders:</p><ul><li><strong>From passive holding → to active access</strong></li><li><strong>From speculative hype → to researched, community-approved deals</strong></li><li><strong>From public rounds → to private allocations across one of Web3’s widest partner networks</strong></li></ul><p><strong>How it works:</strong></p><ul><li>Stake $HAI → Mint stHAI monthly (<strong>1,000 HAI = 1 stHAI/month baseline</strong>)</li><li>Boost minting via <strong>Membership, DYOR Certificate, or HES</strong></li><li>Use stHAI for <strong>guaranteed seats in Hacken Rounds</strong> — or trade/raffle when demand spikes</li></ul><p><strong>Why it matters:</strong></p><ul><li><strong>HAI Group’s network</strong> unlocks early access to some of the most competitive Web3 deals</li><li><strong>DYOR community approval</strong> means every opportunity is vetted by people, not bought hype</li><li><strong>Gradual minting</strong> ensures scarcity and long-term advantage for committed stakers</li></ul><h3>Why stHAI Matters</h3><p>Most of today’s “alpha” is just hype — paid KOLs, promo-heavy launches, and retail left holding the bag.</p><p><strong>stHAI changes the game.<br></strong>Deals are vetted <strong>by the largest DYOR community in Web3</strong>, with real people doing real research — for people, not for payouts.</p><p>In this space, <strong>people trusting people</strong> is the only real edge.<br>And now, that edge is amplified by the early-access network of <strong>HAI Group</strong>.</p><p>The earlier and deeper you commit to $HAI, the more stHAI you mint — <br>and the bigger your guaranteed slice of the hottest private rounds in Web3.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97c5dadb1cdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AMA Recap with Dyma Budorin]]></title>
            <link>https://hackenclub.medium.com/ama-recap-b651d08a8965?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b651d08a8965</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Sat, 26 Jul 2025 16:32:34 GMT</pubDate>
            <atom:updated>2025-10-01T14:00:32.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPmsKMIVhEa67VG_wf1MDQ.png" /></figure><p>The latest AMA wasn’t about feel-good updates — it was about <strong>foundations, direction, and clarity</strong>.</p><p>We’ve completed the migration to the OFT standard, and now we’re building forward on real infrastructure, long-term strategy, and clear priorities.</p><p>Here’s everything that matters.</p><p><strong>From Fragmentation to Foundation: Why OFT Matters</strong></p><p>The $HAI token is now an Omnichain Fungible Token (OFT) — a single canonical asset across all EVM chains. No more bridging fragmentation. No more wrapped tokens. Just one native HAI everywhere.</p><p>This means:</p><ul><li><strong>Unified liquidity</strong> across chains and access to the new</li><li>Seamless listings and DeFi integrations</li><li>Omnichain growth without future migrations</li><li>Full support by <strong>LayerZero</strong> and <strong>SafeSwap</strong></li></ul><p>This new architecture provides the foundation for everything ahead: staking, Hacken Rounds, DYOR certification, and broader ecosystem expansion.</p><p>As we prepare to activate integrations and reach new users, we want to hear from you. <strong>Where should $HAI go next? </strong>Which chains, tools, or ecosystems do you actively use? Which DeFi protocols or platforms should we explore first?</p><p>Your input can help shape our omnichain rollout — share your thoughts and let’s build forward together.</p><p><strong>HES Round 2 — Not Planned, But Possible</strong></p><p>The “security” initiative is real — a completely different type of asset that <strong>reflects an ownership stake in the HAI Group</strong>, and HES holders have already won by getting the best early terms.</p><p>No second round is planned for now. But if the community shows strong demand, a limited HES Round 2 may be considered. Pricing will reflect the updated company valuation.</p><p><strong>Important note:</strong> There will be no equity farming, legally and strategically, we’re focused on value-aligned long-term participants.</p><p><strong>Expansion Plans &amp; Franchise Opportunities</strong></p><p>At the BGA Summit, we teased the next evolution: <strong>HAI Group</strong> — a federation-style model beyond just Hacken.</p><p>This structure will open the door to:</p><ul><li>Regional security service franchises</li><li>Expansion into new verticals</li><li>Access and permissions powered by $HAI</li></ul><p>A major statement is coming, and it will revolve fully around $HAI.</p><p><a href="https://x.com/B4GSummit/status/1939989249455018347">📺 Watch Dyma’s speech at the BGA Summit → 4:47:29</a></p><p><strong>On Burns, Buybacks, and Long-Term Value</strong></p><p>Let’s be clear — <strong>burning is nonsense</strong>, often pushed by those looking to exit.</p><p>Short-term burn = short-term spike, but it does nothing for long-term value.</p><p>The treasury is a strategic asset. It exists for real use cases, including potential partnerships, ecosystem growth, and even project or token mergers. Reducing it arbitrarily would limit our ability to act when it matters most.</p><p>The truth is, the price upsets us more than it upsets you. Because price is a reflection of your confidence in the project, and we take that seriously. We’re confident in what we’re doing and what we’re building. If you’re not, that’s okay. You’re free to exit at your levels.</p><p>We’ve already supported the market, over the past few months, we’ve spent close to $200K doing so. But this is a market, and some of you still selling.</p><p>We’re focused on long-term fundamentals, especially on what drives value: building the product, expanding R&amp;D, and delivering what comes next.</p><p><strong>AI-Based Utility <br></strong>In contrast to random burns, we are working on a more meaningful form of token utility: AI-based security services, based on Virtuals Agents. A prototype is being developed, a smart contract auditing agent that can be accessed even through platforms like Twitter. Users will pay in $HAI to access its services, introducing a real revenue loop tied directly to product usage.</p><p>In this case, we see a valid reason to burn if it’s tied to actual value creation. Burning profit generated by the AI agent is a concept we’re actively considering.</p><p>If you support this approach, let us know.</p><p><strong>Status of hDAO?</strong></p><p>hDAO isn’t active right now — apart from DYOR, there’s no consistent community initiative.The idea of transferring token control has been brought up, but doing so only makes sense when there’s something tangible to govern.</p><p>The original goal of hDAO was to enable productive self-governance, and that can still happen — if there’s renewed energy and direction from the community.</p><p><strong>DYOR + Trust Army = The Growth Engine</strong></p><p>DYOR will be one of the driving forces in the next phase. Work has already started on <strong>a new platform</strong>, which will be fully utilized</p><ul><li>Research leaderboards</li><li>Contributor Benefits &amp; Promotions</li><li>Scalable infrastructure for researchers</li></ul><p><strong>About Listings</strong><br>Bitpanda and Whitebit listings didn’t meet expectations. They were technical steps aimed at increasing visibility, attracting new holders, and stimulating trading activity around $HAI. We invested heavily, both in resources and top-tier marketing packages to make those launches successful.</p><p>But the reality is, there’s been little to no organic trading. It’s unclear whether some participants came purely for speculative opportunities and then lost interest, or whether expectations weren’t met and they moved on.</p><p>This was a learning experience and an expensive one. Going forward, we are no longer pursuing listings unless they make sense strategically and align with the stage we’re in. Only Tier 1 exchanges are under consideration.</p><p><strong>With that said, market conditions don’t alter our goals — they just shape how we reach them.</strong></p><p><strong>Road to $1B — Still On</strong></p><p>The market today is driven by speculation and liquidity is harder to capture, and attention doesn’t stick unless it’s tied to real fundamentals. That’s why our approach has shifted: we’re not chasing short-term volume or hype. We’re focused on real product, real token utilities and even on other type of token — security as an option, and mechanisms that reward long-term holders.</p><p>The goal remains the same. The road to $1B is still active, and the only way forward is through infrastructure, utility, and fundamentals.</p><p><strong>Final Note<br></strong>This AMA wasn’t about short-term performance. It was about committing to long-term fundamentals. With OFT in place and new mechanics, the next chapter isn’t about waiting. The foundation is ready. Now it’s time to build on it.</p><p>Check our roadmap for August → <a href="https://t.me/hackenai/2083">https://t.me/hackenai/2083</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b651d08a8965" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HAI Infrastructure Update]]></title>
            <link>https://hackenclub.medium.com/hai-infrastructure-update-861161892330?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/861161892330</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 18:16:25 GMT</pubDate>
            <atom:updated>2025-09-04T18:59:50.997Z</atom:updated>
            <content:encoded><![CDATA[<p>This post follows our <strong>main statement</strong> detailing the root cause and technical breakdown of the recent exploit. If you missed it, we recommend starting <a href="https://x.com/hackenclub/status/1937261965014933923">here</a> — it covers what happened, how the breach was contained, and why no client funds or core infrastructure were impacted.</p><p>This post is about <strong>what’s next for $HAI</strong>, and how we’re restoring order, trust, and value — step by step.</p><p><strong>TL;DR</strong>:</p><ul><li>The incident was caused by a <strong>legacy private key</strong> tied to an old bridge.</li><li><strong>$HAI will be restarted</strong> via a secure LayerZero-based OFT token for EVM-compatible chains.</li><li>$HAI on VeChain will remain on its current contract, as it wasn’t affected. All CEXs and DEXs on VeChain will continue to use the same token.</li><li><strong>All legitimate token holders before the incident</strong> will be restored 1:1 based on a pre-incident snapshot.</li><li><strong>BSC&lt;&gt;VeChain, BSC&lt;&gt;ETH &amp; ETH&lt;&gt;VeChain Native Bridges are down and will remain down.</strong> Infrastructure is being rebuilt — properly.</li><li><strong>New contracts = safer design.</strong> Multi-sig, pausable, blacklist, no custom bridges.</li><li><strong>Manual claim happens <em>exclusively</em> in the official hAI App (no websites). 6‑month window.</strong></li><li>A portion of $HAI is <strong>locked on Base </strong>due to old mechanics. We’re working on a fix and will update soon.</li></ul><h3>What We’re Doing — and Why</h3><p>We’re not patching the system. We’re rebooting it — clean, secure, and aligned with the vision we already announced: turning $HAI into a fully tokenized asset, with real business exposure.</p><p>This migration isn’t about fixing a mistake. It’s about removing every weak point from the previous outdated design, and giving $HAI a fresh foundation for long-term growth.</p><h3>What’s Coming — Step by Step</h3><ol><li><strong>Snapshot Taken<br></strong>After the initial investigation, the last pre-incident blocks are <strong>51800329</strong> and <strong>22747526</strong> on BSC and ETH, respectively. The last pre-attack block timestamps are <strong>Jun-20–2025 06:40:00 PM +UTC</strong> and <strong>Jun-20–2025 06:39:59 PM +UTC.</strong><br>We will also include the $HAI tokens that users had locked in Flash Pools (HackPot) on Base, as well as the SafeSwap bridge transactions to Base before it was shut down.</li><li><strong>Deploy New OFT Token</strong><br>Issue a fresh HAI token on Ethereum, BSC, and Base (Coinbase’s Layer-2), using LayerZero’s OFT standard to unify supply across chains. The new token uses the same name/symbol, total supply, and tokenomics as before, but starts from the snapshot distribution.</li><li><strong>Distribution</strong><br>Deploy a claim contract on Base that holds the total amount of HAI tokens from the snapshot. All eligible addresses and their token amounts are encoded in a Merkle tree (calculated from the snapshot),<a href="https://medium.com/coinmonks/erc20-snapshot-using-merkle-trees-aeeac48ce925#:~:text=A%20Merkle%20Tree%20is%20an,Let%E2%80%99s%20see%20how%20this%20works"> read more here</a>. Users will interact with the hAI App to claim their tokens: they submit a transaction with a Merkle proof of inclusion to withdraw their allocated HAI. A fixed claim of 6 months will be set; after this deadline, any unclaimed tokens will be withdrawn by the contract owner. The contract owner will be a multi-signature wallet for security (addressing the previous single-key failure).</li><li><strong>Claims happen only in the hAI App (no website)</strong><br>Our claim contract uses a <strong>Merkle‑proof</strong> system. The hAI App generates your <strong>up‑to‑date</strong> proof and lets you submit the claim <strong>without ever exposing or storing</strong> your private key. Running a web claim flow (as many projects do) would dramatically increase phishing risk via fake sites impersonating Hacken. <br><strong>Bottom line: there is no claim website. Only the official hAI App.</strong></li><li><strong>SafeSwap bridge migration</strong> <br>The only non-LZ bridge that will be left is SafeSwap with only one route — Vechain &lt;&gt; Base. Users can then bridge their tokens from Base anywhere else via LayerZero (i.e. built-in mechanics to the OFT token).</li><li><strong>Security Hardening</strong><br>The new contract will be upgradeable and secure. Key features include: a multi-signature “Ownable” governance structure, a Pausable emergency brake, an address blacklist for bad actors, and strict access controls. No custom bridges will be written; cross-chain transfers use LayerZero’s native messaging. Upgrades will be carefully controlled via a multi-sig policy.<br><strong>Single claim surface:</strong> no web claim dApp; restricting claims to the official hAI App reduces phishing and key‑theft vectors.</li><li><strong>Best-Practice Deployment</strong><br>Leverage OpenZeppelin’s upgradeable library and proxy pattern to allow future fixes. Thorough testing (including pause/unpause and blacklist tests) will be done. The team will coordinate with LayerZero to configure Verifier networks (DVNs) and executors for secure cross-chain messaging.</li><li><strong>Comprehensive Extractor integration</strong> <br>Leverage Instructor’s watchers to ensure that all potentially vulnerable areas of the contracts are covered (admin role changes, transfers to suspicious or blacklisted addresses, minting events, emergency changes or governance interactions)</li><li><strong>Post-Migration Liquidity Pool Initialization<br></strong>After the successful deployment and distribution of the new HAI token, all existing liquidity pools on BSC, Ethereum, and Base that use the old HAI token will be shut down completely.</li></ol><p>⚠️ <strong>Note on Base</strong></p><p>Due to long-term locking mechanics, a portion of current $HAI supply remains in a <strong>Virtuals pool (</strong><a href="https://app.virtuals.io/virtuals/18632"><strong>https://app.virtuals.io/virtuals/18632</strong></a><strong>) on Base</strong>. This creates complications for full migration. We’re actively working on a solution or viable option to address this. An update on this part will follow shortly.</p><h3>Omnichain Fungible Token (OFT) Standard</h3><p>The new HAI token will be implemented as a LayerZero Omnichain Fungible Token (OFT). The OFT standard lets an ERC-20 token exist on multiple chains with a<a href="https://docs.layerzero.network/v2/developers/evm/oft/quickstart#:~:text=The%20Omnichain%20Fungible%20Token%20,receiver%20on%20the%20destination%20chain"> <em>unified supply</em></a>. Under this model, when a user sends HAI from chain A to chain B, the token is burned on A and minted on B (read more<a href="https://docs.layerzero.network/v2/developers/evm/oft/quickstart#:~:text=The%20Omnichain%20Fungible%20Token%20,receiver%20on%20the%20destination%20chain"> here</a> and<a href="https://l2beat.com/bridges/projects/layerzerov2oft#:~:text=Omnichain%20Fungible%20Tokens%20,to%20mint%20the%20bridged%20asset"> here</a>). This ensures the total cross-chain supply remains constant and prevents double-spends or inflation. For example, sending 100 HAI from Ethereum to BSC will call _debit on the Ethereum contract (burning 100 HAI) and _credit on the BSC contract (minting 100 HAI).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jeYuP5uUYC593RuN" /></figure><p>LayerZero’s OFT is implemented by having each chain’s HAI contract inherit from OFT.sol, which itself extends LayerZero’s OApp (omnichain application) plus a standard ERC-20. This provides both the usual ERC-20 functions and cross-chain message handling. Internally, the OFT contract emits a cross-chain message via LayerZero’s endpoint; decentralized verifiers (LayerZero’s DVNs) confirm the message, and then a transaction on the destination chain executes the mint. All chains use LayerZero’s official protocol, avoiding any custom bridging code. Notably, we will configure the OFT as a “native OFT” rather than using an adapter escrow: HAI tokens are burned and minted directly on each chain. This makes HAI itself the bridged asset, instead of locking it behind an escrow contract.</p><p>In summary, the HAI token architecture will follow LayerZero’s recommended OFT pattern:</p><ul><li>Unified Supply: Only one total supply across all chains. Tokens move by burn/mint.</li><li>Cross-Chain Messaging: Uses LayerZero endpoints and DVNs to relay transfers.<br> No custom bridge contracts are needed.</li><li>Mint/Burn Logic: _debit() will burn on send, _credit() will mint on receive. The initial supply of HAI will be minted on Base and distributed to eligible users using the distributor contract via the hAI App.</li><li>Chain Configuration: The contract owner can set which Verifier networks (DVNs) and executors to use on each chain.We will configure at least the default LayerZero DVNs for security, and consider adding more verifiers for higher trust.</li></ul><p>Using the OFT standard means HAI on Ethereum, BSC, and Base will each be the same token in a logical sense, with balances flowing via messages. This simplifies future expansion: to support a new chain (e.g. Arbitrum), the team just deploys the same OFT contract on that chain and configures its LayerZero endpoint, rather than designing a new bridging solution.</p><h3>Upgradeable Contract Design</h3><p>Given the need for future fixes and governance changes, the HAI contracts will be upgradeable proxies rather than immutable deployments. Following OpenZeppelin’s guidelines, we will deploy a proxy (transparent or UUPS) pointing to an implementation contract that contains the logic (read more<a href="https://docs.openzeppelin.com/upgrades-plugins/writing-upgradeable#:~:text=You%20can%20use%20your%20Solidity,this%20restriction%2C%20head%20to%20Proxies"> here</a> and<a href="https://docs.openzeppelin.com/upgrades-plugins/writing-upgradeable#:~:text=This%20means%20you%20should%20not,upgradeable"> here</a>). This allows future upgrades of functionality.<br> Key points for the upgradeable design:</p><ul><li><strong>Initializers Instead of Constructors</strong>: As required for proxies, the HAI contract logic will have no constructor. Instead, we’ll implement an initialize() function with the initializer modifier,<a href="https://docs.openzeppelin.com/upgrades-plugins/writing-upgradeable#:~:text=You%20can%20use%20your%20Solidity,this%20restriction%2C%20head%20to%20Proxies"> useful link</a>. This function will set the token’s name, symbol, total supply, and any initial state. Using OpenZeppelin’s Initializable ensures it can only be called once. For example, __OFT_init(“Hacken DAO”, “HAI”) would set up the ERC-20 name/symbol. All parent initializers (e.g. ERC20Upgradeable, OwnableUpgradeable, etc.) must be called within this function.</li><li><strong>Upgradeable Libraries</strong>: We will import from @openzeppelin/contracts-upgradeable (ERC20Upgradeable, OwnableUpgradeable, PausableUpgradeable, etc.) to ensure the code is compatible with proxy deployment. Normal OZ contracts (with constructors) cannot be used.</li><li><strong>Disable Implementation Initialization</strong>: The implementation contract itself will call _disableInitializers() in its constructor to prevent it from being initialized or taken over. This is a standard best practice to lock the logic contract.</li><li><strong>Ownable/Multi-Sig Ownership</strong>: We will make the proxy’s “owner” a multi-signature wallet rather than an EOA. Although we’ll use the Ownable2Step pattern for access control, the actual owner key will be a safe with M-of-N signers. This prevents a single compromised key from taking over upgrades or pausing the contract. As explained in guidance, multi-sig “requires multiple signatures for transactions, providing security against lost or compromised keys” (read more<a href="https://www.alchemy.com/docs/multi-sig-contracts#:~:text=Multi,smart%20contract%20deployer%20on%20Ethereum"> here</a>) and avoids a single point of failure.</li><li><strong>Proxy Deployment</strong>: We may use deterministic deployment (CREATE2) if we choose to align addresses across chains, but it’s not strictly necessary. On each chain we’ll deploy an upgradeable proxy pointing to the HAI logic, and then call initialize with the new total supply and initial distribution parameters.</li></ul><p><strong><em>Important note — </em></strong>the total supply of the token, along with its name, symbol and decimals will not be upgradeable or changeable in any way.</p><h3>Security Features</h3><p>The new HAI contract will include <strong>multiple built-in protections</strong> to prevent a repeat exploit and allow emergency response:</p><ul><li><strong>Pausable</strong>: Using OpenZeppelin’s Pausable module, the owner can pause all token transfers (except perhaps whitelist functions) in an emergency,<a href="https://medium.com/@pavusa/smart-contract-security-101-mastering-pausable-contracts-blacklists-and-critical-tests-d9cd72b0c500#:~:text=1,Emergency%20Brake"> read more here</a>. This emergency brake means that if a new vulnerability is detected, the team can freeze token movement instantly. For example, transfer and transferFrom will have the whenNotPaused modifier. This follows established practice: tokens like USDC are pausable, allowing maintenance during exploits,<a href="https://blog.openzeppelin.com/workshop-recap-secure-development-workshop-1#:~:text=Tokens%20that%20can%20be%20paused"> more info here</a>.</li><li><strong>Blacklist</strong>: The contract will maintain a blacklist (mapping of addresses) that prevents certain addresses from transacting,<a href="https://medium.com/@pavusa/smart-contract-security-101-mastering-pausable-contracts-blacklists-and-critical-tests-d9cd72b0c500#:~:text=2"> read more here</a>. In practice, the contract’s transfer and transferFrom functions check require(!isBlacklisted[msg.sender]). The owner (multi-sig) can add or remove addresses. This lets us block known malicious actors or sanctioned wallets,<a href="https://medium.com/@pavusa/smart-contract-security-101-mastering-pausable-contracts-blacklists-and-critical-tests-d9cd72b0c500#:~:text=2"> more info</a>.<br>For instance, if an attacker address tries to re-enter the system, it can be immediately blacklisted.</li><li><strong>Ownable (Multi-Sig Governance)</strong>: All privileged functions (pausing, blacklisting, upgrading) will require the contract owner. We will set the owner to be a secure multi-signature wallet,<a href="https://www.alchemy.com/docs/multi-sig-contracts#:~:text=Multi,smart%20contract%20deployer%20on%20Ethereum"> read more here</a>. This means multiple key holders must agree to upgrades or emergency actions, removing single-key risk. Multi-sig wallets are “commonly used as wallets” to avoid single points of failure. In other words, instead of one private key controlling HAI upgrades, M of N admins must sign transactions.</li><li><strong>No Custom Bridges</strong>: The token will only use LayerZero’s messaging for cross-chain transfers. We will not implement any custom bridging logic, unlike older tokens that wrote their own bridge contracts. By relying on LayerZero’s battle-tested protocol, we inherit its security model (validator set, retries, etc.). Practically, this means users call a function like sendFrom() in the OFT contract, and we let LayerZero handle the rest. This avoids introducing new bugs in a custom bridge.</li><li><strong>Safe Libraries</strong>: We will use OpenZeppelin’s libraries for all standard functionality (ERC20, SafeMath if needed, etc.). For example, if we ever need to transfer underlying tokens (in an adapter), we would use SafeERC20. Additionally, careful attention will be paid to any non-standard behavior. The OZ security guidance notes that integrating tokens with unusual behavior (fee-on-transfer, hooks, etc.) requires extra care, read more<a href="https://blog.openzeppelin.com/workshop-recap-secure-development-workshop-1#:~:text=Tokens%20that%20execute%20arbitrary%20code,on%20senders%2Freceivers%20using%20hooks"> here</a> and<a href="https://blog.openzeppelin.com/workshop-recap-secure-development-workshop-1#:~:text=To%20handle%20most%20of%20these,library%20available%20in%20OpenZeppelin%20Contracts"> here</a>.</li><li><strong>Testing and Audits</strong>: We will write extensive tests for pause/unpause and blacklist scenarios. Only the owner should be able to pause or blacklist; paused state should block transfers; blacklisted addresses should be blocked.<br> We will also simulate the previous exploit: for example, test that only the correct privileged accounts can mint or that revoke-minter functions work. We will carry out a comprehensive in-house audit that will verify that these controls cannot be bypassed.</li></ul><p>By combining these features, the risk of a single key compromise is greatly reduced. If an admin key is lost, we can pause the contract and/or upgrade to replace it. If a malicious user is detected, they can be blacklisted. Pausable contracts and blacklists are “your first line of defense” in high-stakes scenarios.</p><h3>Cross-Chain Operations and Best Practices</h3><ul><li><strong>Decentralized Verifier Network (DVN) Configuration</strong>: In LayerZero V2, each OFT can customize which Verifiers validate cross-chain messages. By default, LayerZero uses a multisig (e.g. “LayerZero Multisig 3/5”) as its verifier. For extra security, we may add additional verifiers (e.g. community-run endpoints) so that even if one fails, others can attest. We will set a high threshold of confirmations before minting on the destination. This reduces censorship and exploits risk.</li><li><strong>Gas Management</strong>: The cross-chain executor (LayerZero relayer) pays gas on the destination chain. We will allow the payer to be either the sender or the contract owner, depending on use cases. For user transfers, typically the user includes destination gas.</li><li><strong>Future Chain Additions</strong>: If we later add HAI on a new chain, we simply deploy the OFT there and repeat the setTrustedRemote and config steps. Because OFT is designed to be “natively multichain”, adding a chain does not require a new bridge logic.</li><li><strong>Monitoring and Upgrades</strong>: The owner (multi-sig) will keep an eye on LayerZero announcements for any required endpoint changes or critical fixes. If a vulnerability is found post-deployment, the upgradeable pattern allows us to patch by deploying a new implementation and pointing the proxy to it (subject to multi-sig approval).</li><li><strong>No Further Minting</strong>: $HAI contracts will have no arbitrary mint function available (except via LZ bridge flows). We will remove or disable any “mint” function that is not part of the OFT interface to prevent future inflation. Only cross-chain sends will create new tokens on a chain (which exactly offset burns).</li></ul><h3>Testing and Quality Assurance</h3><p>Before launch, we will conduct extensive testing (unit tests and integration tests) for all critical features. In particular:</p><ul><li><strong>Test pause/unpause</strong>: Ensure transfers revert when paused, and succeed again after unpause,<a href="https://medium.com/@pavusa/smart-contract-security-101-mastering-pausable-contracts-blacklists-and-critical-tests-d9cd72b0c500#:~:text=3,Safety%20Net"> more info here</a>.</li><li><strong>Test blacklist</strong>: Ensure a blacklisted address cannot send/receive, and after unblacklist normal function resumes.</li><li><strong>Test bridge transfers</strong>: Simulate LayerZero messages (can use mocks or testnet) to ensure tokens move correctly.</li><li><strong>Test upgrades</strong>: Use Hardhat Upgrades to simulate an upgrade, verifying storage is preserved.</li><li><strong>Check all non-critical fallback behaviors</strong> (e.g. sending to the zero address should fail as usual).</li><li><strong>Test distribution</strong>: Test the manual claims to reassure that it works as expected.</li></ul><h3>Estimates (Action Item / Timelines)</h3><ul><li>Snapshot pre-attack holders on BSC &amp; ETH — 24/6/2025</li><li>Prepare Token Contracts — 24/6/2025–26/6/2025</li><li>Prepare Distributor Contracts — 24/6/2025–27/6/2025</li><li>Implement the new claim screen in the hAI App — 27/6/2025–04/7/2025</li><li>Compile &amp; Audit All Contracts — 26/6/2025–01/7/2025</li><li>Deploy Logic — 03/7/2025</li><li>Configure LayerZero Endpoints — 03/7/2025</li><li>Security Initialization — 03/7/2025</li><li>Bridge Testing — 04/7/2025</li><li>App release (post-stores review) — 07/7/2025</li><li>Post-Launch Checks — 07/7/2025</li><li>Post-Migration Liquidity Pool Initialization — 07/7/2025–11/7/2025</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=861161892330" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Revelation: Final Form of DYOR AI]]></title>
            <link>https://hackenclub.medium.com/the-revelation-final-form-of-dyor-ai-7dcbbd9c9e48?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dcbbd9c9e48</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Fri, 09 May 2025 16:25:50 GMT</pubDate>
            <atom:updated>2025-05-09T18:11:27.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PdPG9JWXAcDsbOfiwSr2zg.png" /></figure><h3>From Research2Earn to Research-as-a-Service</h3><p>Back in <a href="https://hackenclub.medium.com/the-first-tool-trust-army-the-birth-of-research2earn-d0887d3dd2e1">Article 3</a>, we showed how Research2Earn started as a bold experiment. A bet on human curiosity. A structured path from “I want to earn” to “I want to understand.” We didn’t preach DYOR. We turned it into a skill. One that could be learned, practiced, validated, and rewarded.</p><p>And the result? It worked.</p><p>Today, every weekly DYOR Digest is packed with submissions. Quarterly reports are shared, reposted, dissected. Founders read them. Some rewrite tokenomics based on them. Others open calls with our researchers to debate their conclusions.</p><p>What started as a community initiative became a real source of <strong>value</strong>.</p><p>And then something unexpected happened.</p><p>B2B players started asking for our data. APIs, direct integrations, regular feeds. Not just to read — but to build on top.</p><p>But that was only half the story.</p><p>Because in parallel, something bigger was growing: <strong>the retail audience</strong>. People who don’t want to join the Trust Army, but still want to survive web3. People flooded with social campaigns, retrodrops, and token races. People who ask:</p><blockquote>“Should I even touch this project?”</blockquote><p>They don’t need 15-page reports. They don’t need academic frameworks.</p><p>They need an entry point.<br> A context.<br> A signal.</p><p>Something fast, clean, and trusted.</p><p>And that’s where we made the pivot:<br> <strong>From Research2Earn to Research-as-a-Service.<br></strong> From reports for readers to tools for everyone.</p><h3>The Power of AI-Driven Decision Making</h3><p>But then came the harder question:<br> <strong>Why not just scale the research community?<br></strong> Why AI?</p><p>The answer starts with <strong>bias</strong>.</p><p>Even the best researchers bring perspective. That’s part of the magic — but also a limit. Two people can write two great reports… and reach two opposing conclusions. Multiply that by hundreds? It becomes noise again.</p><p>This variability underscores the need for a system that can synthesize diverse viewpoints into coherent insights.</p><p>Moreover, human analysis has its limitations. According to our internal surveys:</p><ul><li>Only <strong>40%</strong> of individuals check a project’s audit status during their research.</li><li>Merely <strong>30%</strong> investigate the backgrounds of project founders.</li><li>Alarmingly, <strong>81%</strong> have experienced a rug pull at least once.</li></ul><p>These figures highlight a significant gap in due diligence practices, contributing to the staggering <strong>$2.9 billion</strong> in losses reported in the Web3 space in 2024, based on the <a href="https://hacken.io/insights/2024-security-report/">Hacken Security Report</a></p><p>Now add another layer:<br><strong>Decay.</strong></p><p>Data in Web3 doesn’t stay fresh.</p><ul><li>Tokenomics change after IDO.</li><li>Founders rotate.</li><li>TVL inflates with farm incentives.</li><li>Audits get published, bugs get patched.</li><li>Сommunities die.</li><li>GitHub goes silent.</li><li>etc.</li></ul><p>Try applying that to <strong>9,799 projects</strong> on CoinMarketCap.<br> Now try doing it across <strong>40+ data layers</strong> per project.<br> Now try delivering <strong>conclusions</strong>, not dashboards.</p><p>That’s why this couldn’t be manual anymore.<br>This needed to scale like the space it’s built for.</p><h3>One Click, All the Answers: The Future of DYOR</h3><p>The future we’re building is simple:<br><strong>You enter a ticker.<br></strong>You get a conclusion.</p><p>Not a feed. Not a data dump. Not a thread.</p><p>A real-time, bias-resistant, dynamically updated insight — powered by:</p><ul><li>Historical datasets from the Trust Army.</li><li>Expert-curated logic from Alpha Intelligence.</li><li>Real-time 3rd party APIs (CMC, Coingecko, GitHub, KOL metrics, etc).</li><li>Cross-checked human-labeled conclusions from certified researchers.</li></ul><p>No signup. No dashboard.<br><strong>Just one click. One line. Your decision, your timing.</strong></p><p>It’s not financial advice.<br>It’s not a verdict.<br>It’s your <strong>entry point</strong> — but one backed by more thought than 99% of crypto.</p><p>Because we all know:<br>People are busy.<br>People are overwhelmed.<br>And the myth of the “everyone DYORs” user? Let’s be real.</p><p>The Bybit x Toluna Joint Research Report reveals:</p><ul><li><strong>31%</strong> of investors rely on social media as their primary source of information.</li><li><strong>24%</strong> depend on advice from friends or family.</li><li>Only <strong>11%</strong> consult official project documentation.</li></ul><p>These statistics indicate a reliance on potentially unreliable sources, leading to uninformed investment decisions.</p><p>DYOR AI aims to change this narrative. By aggregating data from trusted sources and presenting it in an accessible format, it empowers users to make informed decisions with minimal effort. Whether you’re a seasoned investor or new to the crypto space, DYOR AI provides a reliable starting point for your research, reducing reliance on hearsay and increasing confidence in your investment choices.</p><h3>A New Standard for DYOR Reports</h3><p>The shift is bigger than we thought.</p><p>Because suddenly, founders started referencing DYOR insights in their own pitch decks.<br>VCs started pinging us for red flags.<br>Wallets asked how to display research scores.</p><p>And that’s when it hit us:</p><p>DYOR AI isn’t just a better way to do research.<br>It’s becoming a <strong>new standard</strong> for what counts as credible.</p><p>Just like Etherscan defined “on-chain transparency” years ago — <br>We’re building the layer that defines “research clarity.”</p><p>And yes, it will plug into wallets.<br>And yes, it will integrate into trading AIs.<br>And yes, learning dApps are already testing it.</p><p>But its real power?<br>It’s the <strong>signal beneath the chaos</strong>.<br>The checkpoint before you act.<br>The reflection of 1,000 minds — streamlined into 1 insight.</p><h3>Closer Than Ever</h3><p>We built Research2Earn to teach the world how to research.<br>But DYOR AI?<br>It’s how we’ll teach the world to trust again.</p><p>Not through hype.<br>Not through narratives.<br>But through a system that sees clearly, even when we don’t.</p><p>We’re close.<br>And next time you type a ticker, you won’t be guessing anymore.<br>You’ll be seeing the future of DYOR.</p><p>Get real research, not hype.<br><a href="https://x.com/hackenclub">👉 Follow us</a> | <a href="https://t.me/hackenclub">Join the discussion</a> | <a href="https://discord.gg/hacken">Get insights on Discord</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dcbbd9c9e48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Road of Trials: Building the Most Advanced DYOR System]]></title>
            <link>https://hackenclub.medium.com/the-road-of-trials-building-the-most-advanced-dyor-system-aee348266ddc?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/aee348266ddc</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Fri, 02 May 2025 12:59:05 GMT</pubDate>
            <atom:updated>2025-05-02T12:59:05.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WBD3pp_myELdrhf_QCNPwg.jpeg" /></figure><h3>The Real Challenge: Creating an AI That Thinks Like a Researcher</h3><p>By the end of Article 5, we had crossed a line we couldn’t uncross. We made the decision to build DYOR AI. But as we previously revealed, this wasn’t about following a trend — it was about solving a deeper problem that had been building long before “AI agents” became the latest narrative.</p><p>We weren’t building a tool to automate output.<br>We were attempting to create an AI that can think like a researcher.</p><p>That’s not a small leap. Because thinking like a researcher means more than just processing data. It’s knowing what matters, when it matters, why it matters — and understanding how those truths evolve across time, context, and intention. It means judgment. Pattern recognition. Skepticism. A mental model that works like a conditional statement: <strong>if… else…</strong> but one that remembers, questions, and resists bias.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YrqqRrvtI1uVVNlS" /></figure><p>This was our real challenge:<br>Not replacing human insight — but learning how to structure it, encode it, and scale it with precision.</p><p>DYOR AI had to learn how to form a conclusion, not simply report inputs. And to do that, it had to first observe how the best human researchers form theirs.</p><p>So we went back to the source.</p><h3>Gathering the Knowledgebase: A Library of Web3 Truths</h3><p>As explained in earlier chapters, <strong>Trust Army</strong> was never a gimmick. It wasn’t a bounty board. It was our testbed for methodology. Each of its tasks (only 4 of 12 released in beta) was designed to teach users how to extract, verify, and evaluate project data with rigor and logic.</p><p>Later, Hacken’s <strong>Alpha Intelligence subcommunity</strong> emerged from its top performers. What they produced wasn’t surface-level content. These were analytical judgments — flagging flawed tokenomics, identifying red flags in governance models, even exposing undeclared founder affiliations.</p><p>That’s when we realized:<br>This wasn’t a dataset. It was a growing body of crypto truth.</p><p>And we weren’t archiving it. We were designing a system to keep it alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ai85fdMI5S9K4YN7" /></figure><p>From that need, the <strong>DYOR scheme</strong> was born — a complete, layered map of crypto research logic. Every data type, from immutable facts to real-time signals, had its own update rules, validation logic, and risk tolerance:</p><ul><li>Token vesting schedules — updated monthly or after unlocks.</li><li>KOL sentiment — monitored in real-time, with spike detection.</li><li>Audit status and bug bounty disclosures — tracked post-publication.</li><li>GitHub development — parsed every 48 hours using commit metrics.</li></ul><p>There are nearly <strong>10,000 listed projects</strong> on CoinMarketCap today. Most will never matter — but new ones appear every day. Each has <strong>dozens of metrics</strong>, each on its own clock.</p><p>That’s why DYOR AI isn’t a luxury.<br>It’s the only way to scale this library.</p><p>No human analyst, no matter how passionate, can monitor that much data. Not even across a global, 24/7 network.</p><h3>The 12 Research Tasks: Training the Future of AI-Powered Due Diligence</h3><p>Our researchers weren’t hired to farm bounties. Trust Army wasn’t built to measure speed. It was built to measure depth of thought.</p><p>Each of the 12 research tasks was carefully crafted not just to gather information, but to map human logic — decision-making in motion.</p><p>We didn’t ask people to extract facts.<br> We asked them to weigh evidence.</p><ul><li>Why is this project suspicious?</li><li>What subtle indicator triggered concern?</li><li>How were contradicting data points reconciled?</li><li>What deserves inclusion in a final verdict — and what doesn’t?</li></ul><p>Even during the 4-task beta, a clear signal emerged:<br>The best researchers weren’t compiling — they were reasoning.</p><p>And that, more than anything, became the architecture for AI training. Not checklists, but decision trees. Not summaries, but rationales.</p><p>Each approved report — reviewed by validators and Alpha leads — became a labeled dataset for teaching context-aware models to force AI to form questions:</p><ul><li>“Is this vesting logic typical for projects at this stage?”</li><li>“Does this founder’s online behavior raise new risk factors?”</li><li>“How does stated TVL compare to verified wallet patterns?”</li></ul><p>These tasks weren’t tutorials.<br>They were templates for trust.</p><p><strong>The DYOR Certification: Making Research a Recognized Skill</strong></p><p>If AI was to learn from real researchers, we had to ensure those researchers had credibility. Not assumed. Proven.</p><p>That’s why we introduced <strong>DYOR Certification</strong>.</p><p>This isn’t resume filler. It’s a logic passport.<br>It links your work, your conclusions, your methodology — to your reputation. Via a soulbound identity layer.</p><p>What does it validate?</p><ul><li>Consistently low error rate</li><li>Pattern-aware thinking</li><li>Objective judgment</li></ul><p>Why does this matter?<br>Because AI won’t learn from randomness. It will learn from structure.<br>Certified researchers are more than users — they’re signal filters.<br>They anchor the machine’s learning loop.</p><ul><li>First: human insights</li><li>Then: AI reflects, enhances, or challenges</li><li>After: updated facts shift conclusions</li><li>Finally: feedback re-enters the system</li></ul><p>This isn’t annotation.<br>This is <strong>human ethos</strong>, encoded.</p><h3>The Unexpected Allies: The First True Believers in Our Vision</h3><p>We hadn’t even launched the full Trust Army yet. DYOR AI was still forming as a concept. But suddenly — people came knocking.</p><p>Project founders. Wallets. DeFi teams. AI Trading platforms.<br>They didn’t want partnerships or promo.</p><p>They wanted integration.</p><p>They wanted DYOR.</p><p>Even without a full release, they saw it:<br>DYOR isn’t a dashboard — it’s a standard.</p><p>And as demand grew, we realized the shift:</p><blockquote>DYOR AI won’t be only where users go.<br>It should be built into where they already are.</blockquote><p>Wallets. Browsers. On-chain risk monitors. Trading bots.<br>The DYOR AI concept is becoming a <strong>layer</strong>, not a destination.</p><p>We’re not building one more tool.<br>We’re architecting the infrastructure of credibility in Web3.</p><p><strong>And before this AI learns to form its own conclusions, we’re teaching it how to inherit ours — truthfully, transparently, and together.</strong></p><p><a href="https://x.com/hackenclub">👉 Follow us</a> | <a href="https://t.me/hackenclub">Join the discussion</a> | <a href="https://discord.gg/hacken">Get insights on Discord</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aee348266ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Breakthrough: Choosing to Build DYOR AI]]></title>
            <link>https://hackenclub.medium.com/the-breakthrough-choosing-to-build-dyor-ai-6a8a7d38779c?source=rss-a70d0274ef3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a8a7d38779c</guid>
            <dc:creator><![CDATA[Hacken.AI]]></dc:creator>
            <pubDate>Fri, 25 Apr 2025 15:35:38 GMT</pubDate>
            <atom:updated>2025-04-25T15:36:50.547Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OU7Sv5GdQ34GsWkfBCBwgw.jpeg" /></figure><h3>The Truth No One Wants to Admit: Why Even Web3 Lacks Transparency</h3><p>As we revealed earlier, the crisis at the heart of Web3 wasn’t simply about scams or bad actors — it was about <strong>the absence of real transparency</strong>.</p><p>Even after the rise of DYOR mantras, despite thousands of dashboards and analytic platforms, most users were still trapped. Information was everywhere, but understanding was rare. Founders made key decisions on incomplete data. Users followed hype cycles instead of fundamentals. Research remained fragmented and superficial.</p><p><strong>The core truth?<br></strong>Web3 wasn’t suffering from a lack of data.<br>It was suffering from a lack of <strong>living, evolving, verifiable insight.</strong></p><p>And without it, even the best intentions couldn’t prevent systemic mistakes.</p><h3>Why the DYOR Problem Is Bigger Than Scams</h3><p>Throughout our journey — from launching TrustArmy to building the first Research2Earn model — we kept encountering the same deeper problem.</p><p>As we saw before, the industry didn’t just need to catch obvious scams.<br><strong>It needed to uncover blind spots</strong> — flaws inside legitimate projects, overlooked risks in beloved communities, hidden patterns that could make or break entire ecosystems.</p><p>The real DYOR crisis was bigger than fraud.<br>It was about <strong>building a way to understand Web3 at its core</strong>, not just react to its symptoms.</p><p>And while our community proved that decentralized research could work — thousands of reports, validators, peer-reviewed conclusions — it still wasn’t enough.<br>It was powerful.<br>But slow.<br>Heavy.<br>And ultimately, limited by human bandwidth.</p><h3>What If DYOR Had No Barriers?</h3><p><em>(The Thought That Changed Everything)</em></p><p>This was the moment when everything shifted.</p><p>In the previous phase, TrustArmy gave us raw momentum. DYOR Alpha Intelligence showed us that people could evolve from passive observers to real builders of insight.</p><p>But what if the conclusions, dependencies, patterns they found — what if those <strong>could live beyond manual work</strong>?</p><p>When the AI wave hit Web3 in 2024, it was tempting to dismiss it as another hype cycle — after all, most early tools just pumped out shallow summaries and fake engagement.</p><p>Yet we saw something deeper.</p><blockquote><strong>What if research itself could become a living, breathing system?</strong></blockquote><p>An AI that doesn’t replace people — but learns from them.<br>An AI that doesn’t just fetch data — but dynamically updates <strong>conclusions</strong>, identifies <strong>hidden dependencies</strong>, projects <strong>future risks</strong> based on <strong>real-time</strong> changes.</p><p>Not AI as a buzzword.<br>AI as the second heart of DYOR.</p><p><strong>Dynamic, evolving, collaborative.<br></strong>Not instead of humans.<br><strong>With humans.</strong></p><h3>Risk vs. Reward: The Decision That Would Define Our Future</h3><p>It was not an easy decision.</p><p>We had already built momentum with TrustArmy and DYOR Alpha Intelligence.<br>The safe choice would be to double down, scale the existing model, maybe grow by 2–3x each year.</p><p>But safe wasn’t the goal.</p><p>We knew:<br>To really fulfill the vision we started — to make real DYOR accessible to <strong>everyone</strong> — we had to leap.</p><p><strong>We had to recognize the risks and consciously step into them:</strong></p><ul><li>Building a complex AI system no one had yet proven possible.</li><li>Training a foundational LLM capable of understanding the unique context, depth, and nuance of crypto data.</li><li>Designing an infrastructure to integrate TrustArmy reports, community intelligence DYOR, real-time APIs, sentiments, GitHub activity, tokenomics dynamics — all into a single evolving ecosystem.</li><li>Committing massive internal resources and talent <strong>long before</strong> the market would clearly validate such a solution.</li></ul><p>We knew the path was uncertain.<br>But we also knew: <strong>without this leap, the real vision of DYOR would stay trapped in the past.</strong></p><p>And yet, the reward was too big to ignore:</p><ul><li>A real Intelligence Layer for Web3.</li><li>Research that doesn’t get outdated the moment it’s written.</li><li>DYOR that lives, breathes, evolves — and helps every participant, from newcomers to seasoned investors, make smarter decisions.</li></ul><p>We weren’t chasing the AI trend.</p><p><strong>We were answering the same call</strong> that brought us to TrustArmy and Research2Earn:</p><blockquote><strong>A Web3 where transparency wins by design, not by luck.</strong></blockquote><h3>The Leap of Faith: Choosing to Build DYOR AI</h3><p>In early 2025, DYOR AI will emerge from vision to reality.</p><p>A new kind of system:</p><ul><li><strong>Foundational LLM:</strong> A custom model trained on real-world crypto intelligence, not just scraped articles.</li><li><strong>Dynamic Knowledgebase:</strong> Feeding from TrustArmy, Alpha Intelligence, external market data, and social signals.</li><li><strong>Human-Complementary Reasoning:</strong> Not competing with our community, but constantly learning from it — adapting, validating, and expanding insight.</li></ul><p>DYOR AI is not a shortcut.<br>It’s not an “instant alpha generator.”</p><p>It’s the natural evolution of everything we fought for from the beginning.</p><blockquote><strong>What if the power to DYOR properly — deeply, accurately, in real-time — finally belonged to everyone?</strong></blockquote><p>Not hidden behind paywalls.<br>Not reserved for whales or insiders.<br>Not broken by bias or hidden agendas.</p><p>Real research.<br>Real transparency.<br>For a real Web3.</p><p><a href="https://x.com/hackenclub">👉 Follow us</a> | <a href="https://t.me/hackenclub">Join the discussion</a> | <a href="https://discord.gg/hacken">Get insights on Discord</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a8a7d38779c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>