Hoosat Network is dedicated to realizing a vision of cryptocurrency as an accessible, low-barrier digital currency designed for real-world adoption. Leveraging the high-speed capabilities of GhostDAG, Hoosat aims to create a robust and inclusive financial ecosystem. Our mission is to ensure cryptocurrency remains a viable tool for global transactions, even in an era where artificial intelligence may surpass human labor. By enabling mining with consumer-grade mobile and personal computer CPUs and GPUs, Hoosat empowers individuals to generate value and participate in a decentralized economy, facilitating seamless, worldwide purchases with true financial sovereignty.
Despite facing significant challenges and targeted misinformation campaigns, Hoosat Network remains steadfast in its commitment to delivering a cryptocurrency that prioritizes accessibility, speed, and practical utility for all.
This document serves as a comprehensive resource to address and debunk false claims, misinformation, and Fear, Uncertainty, and Doubt (FUD) directed at Hoosat Network. The purpose is not to focus on the individuals spreading misinformation but to clarify the facts surrounding key topics, providing a reliable reference to counter inaccuracies and uphold the truth about Hoosat Network’s mission, technology, and operations. Below is a structured list of common FUD topics and the corresponding facts to set the record straight.
¶ Purpose of This Document
Hoosat Network is committed to creating an accessible, low-barrier cryptocurrency optimized for real-world use, leveraging the high-speed GhostDAG protocol. Misinformation campaigns have sought to undermine this vision. This document aims to:
- Clarify false claims with factual, evidence-based or experience based responses.
- Serve as a public resource for community members, supporters, and stakeholders to reference when encountering FUD.
- Promote transparency and trust in Hoosat Network’s mission to provide a decentralized and accessible cryptocurrency.
¶ Claim: Discord deleted and premine burned - True
I have made mistakes, I'm just a human. I apologize for deleting the Discord server and burning the premine in the early day's of Hoosat Network, because I was having an argument with my wife on how much I spend time on the project. This is one main case Fudders spread that to show that i'm trigger happy and as such should not be trusted for possibly abandoning the project. I'm sorry for deleting the Discord, as lost early days of Discord data.
¶ Claim: Premine is hidden and bigger than I say - False
!Nuelron2 started to FUD about the premine amount and size after he was kicked out of the original launch team for not collaborating well. He tried to spread bullshit that explorer did not display premine blocks. They were there and I had been pointing it out, but he continued that the premine is bigger than the 364 blocks, because they were not mined at 1 BPS.
Premine-blocks includes list of all of those blocks and you can browse from the last to the first through the blocks parents.
First of all the BPS amount is target, not a fact that blocks are found at 1 BPS and difficulty depends on if the target is met. Difficulty drops if block rate raises over the target, difficulty raises if block rate drops below the target. Genesis started at 10K difficulty and ~2048 was difficulty adjustment window.
I mined that 364 blocks at constant 10k difficulty as first difficulty adjustment window had not be met, with a single core of AMD Ryzen 5 3600 CPU, because the original Golang CPU miner included node did not support more than one thread.
In a sense, that just means my single core CPU could not produce blocks with Pyrinhash at 1 BPS.
¶ Claim: Hoosat Network is illegal because of MiCA - False
Hoosat Network is not illegal project according to MiCa. Under the Markets in Crypto-Assets Regulation (MiCA, Regulation (EU) 2023/1114), if a Proof-of-Work (PoW) cryptocurrency or other crypto-asset falls under the exemptions listed in Article 4(2)–(3), a whitepaper is not required to be prepared, published, or notified to the competent authority for a public offer. Consequently, there is no notification obligation to the National Competent Authority (NCA) in these cases, as the whitepaper requirement itself is waived. Below is a detailed explanation:
MiCA, Regulation (EU) 2023/1114 direct link for reference.
This means if whitepaper is not drawn up and notified to the National Competent Authority (NCA), Article 5(2), when a crypto-asset is admitted to trading within the Union on the initiative of the operator of a trading platform and a crypto-asset white paper has not been published in accordance with Article 9 in the cases required by this Regulation, the operator of that trading platform for crypto-assets shall comply with the requirements set out in paragraph 1 of this Article.
Shortly, it means CASP looking to add Hoosat Network is required to handle the MiCa requirements.
Which also means those Exchanges, Escrows, etc, which would need to register as CASP that are not based in Europe can include Hoosat Network in their Exchange without registering as CASP if they can comply with the only narrow exception Article 61: if EU users access the platform exclusively at their own initiative (no active solicitation, marketing, or targeting by the exchange).
However:
- This is strictly interpreted: Features like EU-targeted ads, fiat on-ramps in euros, or non-geoblocked access typically void the exemption.
- Relying on it is risky, as NCAs (e.g., in the Netherlands or France) have challenged it in enforcement actions.
Which means that those exchanges which have listed Hoosat Network are themselves taking the risk if they are accepting european users to their system.
As such Hoosat Network is not illegal according to MiCa, because Hoosat Network is a Proof of Work cryptocurrency where the crypto-asset is automatically created as a reward for the maintenance of the distributed ledger or the validation of transactions and CASPs are required to create the public offer and admission to trading.
¶ Claim: kHeavyHash bug does not exist and Deshe is right - False
The second case is that i've used the basically unfixable probabilistic shortcut bug in kHeavyHash to market Hoohash. This lead to heated arguments between Deshe Shai and me and the Kaspa maxis started to spread FUD about Hoosat in response. But the words from Deshe Shai forced me to do more research. The fact is kHeavyHash matrix multiplication product values are all 3 in less than 1/10,000 cases. I checked over 2 million Kaspa blocks. More information on the topic can be found from my medium article "How to attack Kaspa!" I'm sorry for arguing with Deshe Shai instead of just doing and publishing research.
¶ Claim: That I spread FUD of other projects - False
The third is that i've been spreading information to protect miners (who do not read code) about few projects and what kind of backhanded things they've been doing. Namely the biggest cases of Pyrin and Cryptix network. Seriously though those red flags should be learned by every person doing any kind of mining or cryptocurrency trading and investing. From anonymous developers, to unconfirmable fake partnerships, to hidden premines, to minting more coin through Hard Fork or creating actually new chains with new premines, and false marketing and fake promises. This has caused these anonymous developers and project holders to spread FUD of Hoosat Network because they are worried about their projects price when actual issues are raised. I'm borderline sorry for spreading the information as that has caused more FUD about Hoosat Network, but i'm proud to be the only doxxed Kaspa fork developer as far as I know currently.
¶ Claim: Patent application does not exist - False
This one I won't apologize at all. The patent applications are major case that is fudded. Europeant patent application was filed 1.1.2025 and when you file a European patent application, it remains confidential for a period of 18 months from the earliest priority date (the first filing date from which it claims priority). So you have to wait at least to 1.6.2026 for public information about "Securing Proof of Work Integrity" patent application and I am under non-discosure agreement as the patent innovator.
During this time, nobody outside the EPO (except authorized representatives) can see the application or its contents. So around 18 months after the priority date, the application is automatically published as an A1 document (or A2/A3 depending on search timing).
From that date:
- The application becomes public.
- It is searchable and viewable in the European Patent Register and in Espacenet (EPO’s public patent database).
- The file history (communications, search reports, applicant responses, etc.) becomes publicly accessible through the “All documents” section of the Register.
From that point on:
- All subsequent correspondence between the EPO and the applicant (search reports, examination reports, amendments, refusals, grants, etc.) are made public shortly after being sent.
- If the application is eventually granted, it appears as a B1 publication, also public.
- If it is refused, withdrawn, or lapsed, that status is also shown in the Register.
¶ Claim: $1, $5 or other price point promises - False
I have never made any price promises. I have only stated that certain prices seem reachable and that certain price points already would be epic. FUD of this started when I responded to iTurkMining stating that only $700 from 0.00018074 to 0.01, that $1 seems to be reachable, but getting past the ATH 0.01 would be epic already. Right away discord alternative account VeronaBond started to spout that i've promised him $5 by Christmas 2024 and this is a false statement that has never happened.
VeronaBond account later came to spout that again, but after the account was banned from Discord, Cryptis has been reiterating this topic pretty often with his bitcointalk alts and project account to spread FUD of HTN as he wants to destroy HTN and make his shitcoin successful.
¶ Claim: Blake3 is slowing down Hoohash Hashrate - False
We’re struggling to find any logical basis for this claim. Blake3, for the small inputs used in Hoohash, is just as fast on CPU, CUDA and OpenCL. Blake3 is un-related to the hash-rate of Hoohash v1.1.0 - it get’s called once at the start, and once at the end; never inside the 4096 serially dependant inner loops that do the FP64 mixing and heavy lifting. Version 1.1.10 of Hoohash, saw a significant hashrate reduction, as it was re-engineered to prevent the use of LUTs to skip some of the FP64 non-linear calculations.
Depending on where Blake3 sits within your kernel, the performance of it can be critical; for Hoohash as we’ve already shown, it doesn’t really matter so much. In any case, the Blake3 performance inside the available miners for Hoohash is gigahash range. It is also complex hash algorithm, which AI does not port between languages easily. We tested this porting again in October 2025, when creating the Motoko Blake3 implementation, which required me to port Blake3 by hand. We’re big fans of Blake3 here, and it plays on important part in the cryptographic security of Hoohash V110, but the miner side performance implications really are insignificant unless you bloat your solver un-necessarily with the Blake3 bits.
¶ Claim: Marketplace postponing - False
I have never given any more estimated timeline for the development of the marketplace than it's development will commence when the network runs stable and it does not need much more fixing or upgrading, as in I'm not 100% of focused on keeping the network running. The only thing that has been probably indefinetly postponed is the hoosat address transalation layer implementation to the wallets.
Cryptis and his supporters or alt accounts started spreading FUD about the marketplace postponing instantly when in Q4 of 2025 I decided to start develop the marketplace, but gotta look at the origins why he has been spreading this false-statement.
I published first public information about the marketplace in the only AMA i've done. Ekklectic was very interested about it in the AMA, and few months later he was launching Cryptix Network with Cryptis and they copycatted HTN's vision of the real item marketplace. It is actually on their roadmap. Cryptis might have been thinking that i'm doing some open source payment gateway or marketplace and has been waiting for my work on it. As seriously if he was a serious competitor he would not need to use his alts to spread the FUD, but actually built it and leave Hoosat Network to dust. This has not happened for 10 months, so probably not in the future as he must compine the FUD like in the following message.
¶ Claim: There is two developer fees - Partially correct
-
There is developer fee on the network of minimum 1% of block reward to me on the Node, defaulting to 5% and requires modification of the Node code to change.
-
There is no developer fee for Hoominer mining Hoosat Network, even though Hoosat Network community has shown that they would allow it to be there.
-
There is developer fee in Foztors miners and he has every right to add developer fee to his miners.
So there is no two developer fees to me, but there are two developer fees to different developers.
¶ Claim: The website mentions "website build with animations?" - False
https://network.hoosat.fi is Hoosat Network homepage, https://hoosat.fi is Hoosat Oy homepage and the claimer is confusing the two websites, because https://hoosat.fi website is example what can be done with https://create.hoosat.fi, though it does not state that but acts as homepage of Hoosat Oy.
¶ Claim: Hoohash v1.1.0 algorithm does not have FPGA resistance - False
Most FPGAs (like Xilinx Ultrascale+ or Intel Stratix 10/Agilex) don’t have native F64 units; they emulate them using logic blocks.
- Clock speeds: typically 200–500 MHz.
- Parallelism: custom pipelines can run many operations concurrently — but each F64 operation costs thousands of logic elements.
- Throughput: limited by available FPGA fabric area and memory bandwidth.
Typical performance:
- Xilinx Virtex UltraScale+ VU9P
- ~100–250 GFLOPS Highly optimized design, max clock ~400 MHz
- Intel Stratix 10 GX
- ~200–400 GFLOPS With dense FPU tiles
- AMD Versal HBM
- ~400–600 GFLOPS Uses dedicated HBM bandwidth and DSP-heavy designs
When in comparison
- NVIDIA A100
- ~9.7 TFLOPS Ampere, 1/2 FP32 rate
- NVIDIA H100
- ~26 TFLOPS Hopper architecture
- AMD MI300A
- ~20 TFLOPS Instinct accelerator
- RTX 4090
- 1,290.2 GFLOPS Consumer GPU, FP64 = 1/64 FP32 rate
- RX 6800
- 1,010.4 GFLOPS Consumer GPU, FP64 = 1:16 FP32 rate
Which means consumer grade GPU's are about two times faster at IEEE-754 standard FP64 even if FPGA's have IEEE-754-F64-FPU's available. That is resistance to giving FPGA's overpower in the algorithm hashrate and making GPU mining obsolete.
¶ Claim: Hoohash v1.1.0 algorithm does not have ASIC resistance - False
Unlike general-purpose GPUs or reconfigurable FPGAs, ASICs (Application-Specific Integrated Circuits) are custom silicon designs optimized for a single algorithm or function. This means that if an algorithm is simple enough or has fixed arithmetic patterns, an ASIC can achieve orders of magnitude higher efficiency and throughput.
However, for algorithms that rely heavily on IEEE-754 standard double-precision (F64) floating-point arithmetic, the economics and complexity of ASIC design change drastically.
Since Hoohash relies on IEEE-754 double-precision math, it inherits ASIC resistance through economic and architectural inefficiency:
- Implementing large numbers of F64 FPUs on an ASIC yields diminishing returns in die size, yield, and power.
- Even a well-funded ASIC project would only achieve marginal gains (perhaps 2–3× over GPUs) at massive cost.
- For comparison, the same effort in integer or fixed-point arithmetic (like SHA-256) yields 1000× efficiency gains, which is why Bitcoin ASICs dominate, but not here.
There is also the fact that Google TPUv3 (mixed FP32/BF16) ~0.6 TFLOPS (FP64 equivalent) Optimized for AI. Hypothetical F64 ASIC (Hoohash-optimized) 3–10 TFLOPS, requires extremely optimized FPU arrays, high cost and power use. When consumer GPUs already do 1–26 TFLOPS IEEE-754 standard FP64.
¶ Claim: The Hoosat Network price is down in the lows - True
From the launch to today, the price has been finding it's floor because fudders have killed the hype and people like Bawls from mining4people generated HTN's price down systemically to purchase more.
Hoosat Network price is currently following the electricity prices defined by miners and those who are supporting Hoosat Network and betting on the patent passing and my development skills are loving the dollar-cost averaging (DCA). As in there is absolutely no-one who forcefully pumps the price up for you to dump the price down.
¶ Claim: Tonto has dumped the price down - False
Here Bawls admitting he generated HTN price down 86.04% + more.
So in that sense. Point your fingers for your losses in the right direction. As after may 2, 2024 (which is around the time of 0.0043 price) HTN price has gone down 95.41% to this date 12.10.2025. Also I burned the premine, did not dump. I have also never pressed to sell button to dump the price down, as for real, i'm not here for quick pump and dump schemes, nor trying to milk some cow. I'm trying to build cryptocurrency that follows Satoshi vision added that it is accessible to everyone and actually usable as currency.
¶ Claim: Hoosat Network is unverified token - False
Hoosat Network is not Layer 2 token and there is no wrapped HTN in any L2 network. Hoosat Network is decentralized Proof of Work CPU and GPU mineable cryptocurrency based on Kaspa!
¶ Claim: Self-custody marketplace can't have escrow, fraud detection, regulatory compliance.
Self-custody in crypto means you take full control and responsibility for your digital assets by holding your own private keys, without relying on a third party service like an exchange. This is example of non-custody service, there exists so called decentralized exchange by Cryptix Networks which runs mostly centralized on their servers but requres using dual signature wallet running on self runnable wallet daemon, where you only have half of the control of the private keys. This means the so called decentralized exchange can steal basically your coins at any given moment.
A self-custody marketplace means the platform never holds your assets or keys. Buyers and sellers execute transactions directly from their own wallets. That removes the biggest risk in Web2 commerce: a centralized custodian controlling your funds and can scam both the buyer and seller.
Self-custody doesn’t mean “no safeguards.” Escrow, dispute systems, compliance, and fraud checks can all be built on-chain or at the marketplace layer without the marketplace ever holding user funds. The blockchain guarantees asset integrity, while the marketplace handles reputation, rules, and enforcement.
Bottom line: users stay in control of their assets, and protections still exist, just without a custodial middleman or a single point of failure.
Only issue is Escrow services: traditional escrow breaks self-custody by forcing users to surrender control to a middleman. Even with multisig escrow, funds stay only partly in the owner’s control and can only move with the proper signatures.
¶ Claim: It's illegal to freeze wallet because of MiCa & SEC!
Neither the EU's Markets in Crypto-Assets Regulation (MiCA) nor the U.S. Securities and Exchange Commission (SEC) regulations make it illegal to freeze Proof of Work (PoW) cryptocurrency deposit addresses. In fact, both frameworks explicitly enable or require such actions under specific circumstances, primarily for compliance with anti-money laundering (AML), counter-terrorism financing (CTF), sanctions enforcement, or risk management. Freezing addresses, often by blacklisting them on a platform or refusing to process incoming transactions is a standard tool for entities to mitigate illicit activity, and it aligns with broader financial regulations like the EU's AML Directives and U.S. Bank Secrecy Act (BSA) requirements.
¶ Claim: Freezing wallet breaks decentralization
Freezing an address on-chain (e.g., a node or pool refusing to relay/validate transactions from a specific address) does not break decentralization:
- Mempool is local & voluntary: Every node independently chooses what to include there, as there is no global mempool. One or two nodes freezing an address doesn’t stop others from relaying/mining it.
- Consensus rules still apply: As long as a transaction follows PoW protocol (valid sig, fees, etc.), any miner can include it in a block. A freeze is just one node’s policy.
- Network routes around censorship: Users can connect to non-censoring nodes, decentralization ensures no single choke point.
In short: freezing is soft censorship, easily bypassed on a truly decentralized PoW chain like Hoosat Network. As in we can not completely freeze any wallet, we can make it harder to use the wallet.
There has been community vote about the freezing Xeggex Exit Scam funds of HTN in 9/8/2025.
Link to the discord poll as Cryptis is using his Safebase alternative account to spread lies that the voting was made with fake discord accounts. You should be able to view the voters in the discord poll.
¶ Claim: Tonto was not the first to implement DAGKnight
Tonto's open DAGKnight Testnet preceded Kaspa's public implementation work by 19 Days!
- Tonto at Hoosat publicly launched an open DAGKnight testnet on February 8, 2026. This allowed community participation, node syncing, mining, and testing of a live DAGKnight-based implementation.
- In contrast, the Rusty-Kaspa repository saw the first public commit toward a DAGKnight implementation on February 27, 2026. This initial commit by coderofstuff (titled "[DK-protocol] Init full DK base implementation") marks the start of visible, open-source work on DAGKnight for Kaspa: https://github.com/kaspanet/rusty-kaspa/commit/977c223f8f9e6843c2efb9fe4047b26616e3fe91
While Kaspa had been discussing/planning DAGKnight integration earlier (e.g., via KIPs like KIP-2 proposed by Yonatan Sompolinsky and others), and theoretical/design work likely predated both, Tonto's effort appears to be the first publicly deployed and openly readable/testable/participatory DAGKnight implementation in a live testnet environment.
¶ How to Use This Document
- Community Members: Reference this document when encountering false claims about Hoosat Network. Share links to this resource to counter misinformation with facts.
- Developers and Supporters: Use the outlined facts to educate others about Hoosat’s mission and technology.
- General Public: This document is a single source of truth to verify Hoosat Network’s legitimacy and address concerns raised by misinformation.
¶ Commitment to Truth
I personally finally acknowledge that addressing FUD directly with individuals can be time-consuming and often unproductive, as some may spread misinformation intentionally. By maintaining this document, we aim to shift focus from reactive debates to proactive clarity, ensuring the community has access to accurate information. This resource will be updated regularly as new FUD topics emerge, keeping it a living document for truth and transparency.
If you encounter additional FUD topics or have questions, please reach out through Hoosat Network’s official channels for clarification or to contribute to this document.