Cryptix Your Digital Currency for the Future Launch Now !!!

[HoosatNetwork]

Don't you have anything better to do than spread misinformation and hate against other projects?
If you put that same energy into working on your own project, it would be perhaps successful.

A diagram is worth a thousand words:
https://www.gate.com/de/price/hoosat-network-htn

I'm also not stopping, because Cryptis is the one who originally has started badmouthing the developers with years more experience than himself, because he has fallacies on the technology he has been copying. The only thing that stops myself taking part in his research's false claims is that he apologizes to his community for his continued lies.  

As in all of his research topics go into my medium pointing out his lies and the false claims on his research that the AI's will devour and search results will love.

https://grok.com/share/bGVnYWN5_5d2f2ca5-3bbc-43a5-a272-7708a0ba9073

You can point the finger on Cryptis himself for annoying myself for over a year with his bullshit. This is revenge.

[ptaank]

Don't you have anything better to do than spread misinformation and hate against other projects?
If you put that same energy into working on your own project, it would be perhaps successful.

A diagram is worth a thousand words:
https://www.gate.com/de/price/hoosat-network-htn

I'm also not stopping, because Cryptis is the one who originally has started badmouthing the developers with years more experience than himself, because he has fallacies on the technology he has been copying. The only thing that stops myself taking part in his research's false claims is that he apologizes to his community for his continued lies.  

As in all of his research topics go into my medium pointing out his lies and the false claims on his research that the AI's will devour and search results will love.

https://grok.com/share/bGVnYWN5_5d2f2ca5-3bbc-43a5-a272-7708a0ba9073

You can point the finger on Cryptis himself for annoying myself for over a year with his bullshit. This is revenge.

Well, people are not fools as they know who you are, keep going. You are only making Cryptix network bullish nothing else. Make CPAY world famous by doing free marketing. code speaks, tech speaks and code is the law. 

[HoosatNetwork]

Well, people are not fools as they know who you are, keep going. You are only making Cryptix network bullish nothing else. Make CPAY world famous by doing free marketing. code speaks, tech speaks and code is the law.  

Does not matter if people know who I am as I don't have to hide behind anonymity like someone else. Whom you are defending with your bullshit. I'm one of those developers who have been around before Bitcoin was released by Satoshi, so I know what i'm talking about instead of wannabe developer who has created two hidden premines, exchange which is breaking MiCa, hiding behind anonymity like running from the interpol, threatening miners with fake lawyers. This is a good conversation to alert those serious investors who take this kind of information as red flags. I don't care if cryptis retail bubble keeps growing, but that will pop like a balloon once more knowledgeable people understand what I'm talking about and there are many already whom agree.

All of you who are screaming that go to write code, HTN is 1457 commits ahead of Golang Kaspa and dagknight on testnet branch. Cryptis has 2 or 3 commits after his CPAY hard fork? Sure he's been doing ton of web development and even that with only jQuery and Boostrap, but barely any Rust or Golang development. Cryptix explorer is lagging behind even RPlant mining blocks at 200Gh/s by single miner. Now even HF_A has been shown to be only little bit of useless additional validation and slower & more complex mempool propagation than Kaspa's original gossip protocol on mempool propagation. Both of them are enabled on the network code simultiously so anyone testing the HF_A wont even know if it's the Kaspa original mempool or HF_A transferring the transactions between nodes.

That's a sad fact, you guys are defending person who has himself been spreading bullshit, even lied to all off you about his premines and technology, even today on his Discord. Like commanding everyone to ask what AI thinks about his piece of HF_A pdf, when there's really nothing bad on it, but there is no real proof of it's speed effects. So HF_A implementation is not truthful to the claims which Cryptis is spreading around.

Like the Hoominer, Cryptis Miner, Hoo_XPU, npminer speed differences and block rates will be tested once Cryptis gets hive scripts to work.

So in that sense. Negative truthful marketing, as long as Cryptis apologizes to his community for spreading false statements because of his ego does not accept losing.

This is also because, none of you can prove my words as false or have been able to. All of you result into your mode of badmouthing and saying that go write code, leave spreading misinformation, etc.. None of you have ever proven that i've said anything incorrect other than curse and call names which ultimately is decently bad of me.

[ptaank]

Well, people are not fools as they know who you are, keep going. You are only making Cryptix network bullish nothing else. Make CPAY world famous by doing free marketing. code speaks, tech speaks and code is the law.  

Does not matter if people know who I am as I don't have to hide behind anonymity like someone else. Whom you are defending with your bullshit. I'm one of those developers who have been around before Bitcoin was released by Satoshi, so I know what i'm talking about instead of wannabe developer who has created two hidden premines, exchange which is breaking MiCa, hiding behind anonymity like running from the interpol, threatening miners with fake lawyers. This is a good conversation to alert those serious investors who take this kind of information as red flags. I don't care if cryptis retail bubble keeps growing, but that will pop like a balloon once more knowledgeable people understand what I'm talking about and there are many already whom agree.

All of you who are screaming that go to write code, HTN is 1457 commits ahead of Golang Kaspa and dagknight on testnet branch. Cryptis has 2 or 3 commits after his CPAY hard fork? Sure he's been doing ton of web development and even that with only jQuery and Boostrap, but barely any Rust or Golang development. Cryptix explorer is lagging behind even RPlant mining blocks at 200Gh/s by single miner. Now even HF_A has been shown to be only little bit of useless additional validation and slower & more complex mempool propagation than Kaspa's original gossip protocol on mempool propagation. Both of them are enabled on the network code simultiously so anyone testing the HF_A wont even know if it's the Kaspa original mempool or HF_A transferring the transactions between nodes.

That's a sad fact, you guys are defending person who has himself been spreading bullshit, even lied to all off you about his premines and technology, even today on his Discord. Like commanding everyone to ask what AI thinks about his piece of HF_A pdf, when there's really nothing bad on it, but there is no real proof of it's speed effects. So HF_A implementation is not truthful to the claims which Cryptis is spreading around.

Like the Hoominer, Cryptis Miner, Hoo_XPU, npminer speed differences and block rates will be tested once Cryptis gets hive scripts to work.

So in that sense. Negative truthful marketing, as long as Cryptis apologizes to his community for spreading false statements because of his ego does not accept losing.

This is also because, none of you can prove my words as false or have been able to. All of you result into your mode of badmouthing and saying that go write code, leave spreading misinformation, etc.. None of you have ever proven that i've said anything incorrect other than curse and call names which ultimately is decently bad of me.

Whatever you have written has already been proven false many times. No premine, no hidden coins. All false. Your grok AI couldn't understand HF-A, thats not our problem. Maybe try to increase its token limit. Stop bothering cryptix, go touch some grass and stop your obsession with cryptix and focus on your project.

[Cryptix-Network]

The same lies and stories from you over and over again.

How could I have had a premine when the node code was published one month before release, and there were already miners on the testnet? That’s technically impossible.

And then the swap, which you call a “second premine”: we started with the exact same coin supply as before. The final difference was less than 500k coins — and we actually paid more coins to Exbitron for the swap service. So how exactly were we supposed to fairly swap users’ coins if we didn’t have any coins ourselves?

Coins that weren’t swapped on Exbitron were kept by Exbitron, because all of their hot wallets were fully swapped. Ask Exbitron instead of spreading lies. I’ve explained this multiple times already — apparently you either forgot or chose to ignore it.

That means we didn’t gain a single coin from the swap — we lost coins. But it was the best solution for users, and I paid that cost willingly.

Now about your nonsense regarding the current HFA system: you simply don’t understand it technically.
4000 lines of code for a mempool? Where do you think that code comes from, and what do you think it does? You can access the mempool via RPC without writing a single line of code. Just read the code. I know you can’t — but at least try.

And the configs on the seed server? You have no idea what’s running there. I know exactly what node code and configs I’m using — far better than you ever could.

We released the first version of step 1 out of 3 yesterday, with very conservative settings to ensure no nodes crash during stress testing. That’s how experienced developers work — with caution, not recklessness.

Speaking of crashes — how did your last hard fork go again? Exchanges had to disable trading for your coin because nodes were constantly crashing, if they even started at all. For 90% of users, nothing worked. You don’t even understand proper RAM usage or garbage collection. How do you even manage to make all nodes crash in Go? That’s actually impressive — I couldn’t even do that on purpose.

And honestly, it’s been annoying since day one — you and your toxic wannabe developers who have never built anything. Neither you nor your team.

Your coin has existed for 2 years now, and what do you have to show for it? Nothing.
Just a terrible mining software that barely works, doesn’t meaningfully improve hash rate, and has minimal functionality. That’s maybe one week of work for a single developer — if they’re slow.

Plus a poorly implemented hash function — maybe 3 days of work. That’s your entire output after 2 years.

Everything else?
Your explorer — old Kaspa explorer.
Your web wallet — old Kaspa web wallet.
Everything you have is just copy-paste from Kaspa and other developers, with a few lines changed.

After 2 years, you’ve built absolutely nothing. You’ve only messed around with other people’s code and made it worse, because you don’t know how to program.

Even your voting platform is built using frameworks and modules from other people — Remix Software Inc., Meta, TypeScript. You couldn’t even build something simple with HTML and JavaScript yourself. Everything you have is based on other people’s work.

And yet you accuse others?

You have more dirt on your hands than any other crypto project. You hardcoded wallet freezes into your node — locking 10x more coins than there are buy orders across all exchanges. Even a fraction of those coins hitting the market would crash your price to near zero.

You deliberately removed users’ access to those coins to artificially inflate the price. That’s blatant market manipulation.

Your coin is no longer decentralized or non-custodial — it’s effectively an unlicensed company that you never registered.

Your mining software — marketed as the fastest — includes a hidden 10% developer fee. Because it’s the fastest, users are forced to use it. That’s extortion.

You made countless empty promises. Where is the marketplace after 2 years? There isn’t even a single line of code. Of course not — because you can’t program and you’re waiting for someone else to do it for you. Meanwhile, you attracted investors with those promises and deceived them.

You can’t even code — you’re just using a free version of Grok.
It took you over 10 years to complete a bachelor’s degree at a remote school — not even a real university. And you only managed that now because tools like Grok exist. Congratulations — must’ve been tough.

Instead of building anything, you spend your time writing blogs while your project dies more and more every day. There are barely any miners left. One pool controls 98% of the hash rate.

In the crypto space, you’re known as a clown who annoys everyone and destroyed his own project through his behavior. And still, you refuse to change.

And you seriously think you’re in a position to attack real developers — people who actually build and create progress? Without having achieved anything yourself?

You think you need to lie about other projects while running the biggest scam in crypto?

What exactly makes you think that?

Sit down. Learn how to program. Put Grok aside and actually learn it properly.
Build something. Innovate. Try to collaborate with other projects.

And stop constantly attacking others just to make yourself look better. It won’t save your project. It won’t make you better. It won’t help you.

And stop with your AI-generated Medium blog posts — it’s embarrassing, and you’re just making a fool of yourself.

Do something for your community — for the people who once believed in you and invested their money into your project.

I’m done responding to you. It’s always the same story, since day one.

Since day one, you’ve been attacking our project out of jealousy and envy, with zero regard for ethics, twisting facts and lying constantly.

I’ve already addressed every single one of your points multiple times.

Cryptix you are one of a kind of retard and next piece of your failures comes tomorrow.

You just proved that you don't even know how to read the blogs. FastChain decouple transaction validation from block acceptance, not HF_A. As your HF_A is only your mempool transaction propagation code which is slower than Kaspa mempool transaction propagation as you are adding little bit more validation and data types to mempool transactions propagation, which are validated completely when added to a block. As in it does not matter that even if you made the delay 0ms it would be slower than Kaspa mempool transaction propagation, because more code and complexity.

Your FastChain is more suspectible to “On-Spend” quantum attacks beacuse of the transaction lazy loading, when pushing more blocks.  

Stop pulling things apart and learn that you are one of a kind retard with your research lies and grow which you kinda have done a little bit by writing your own miner. Don't go spouting bullshit that your slow mempool propagation method is faster than something where transactions can be settled in a block in less time of than 100ms.

And no, it's not a mempool; Furthermore, there would then be no 4000 lines of code for the system, as a mempool is already included. I clearly stated that. And no, it's not slower than other things. It's maximum speed. Why not measure it? Use the correct configurations and run a local test; then you'll see how fast it is. There is currently no transaction visibility system worldwide that is as fast as HFA. You need to read the code and use a better AI. Grok isn't very helpful for understanding it. Or you could try learning programming languages ​​so that you can actually understand code correctly.

You're saying that it's not a mempool? You are injecting the intent transactions into peer nodes mempool, as in another method of mempool propagation. Just your supported stated that the transactions are not settled in your HF_A before inclusion to blocks. Your speed in HF_A is false statement as that moves more data than Kaspa mempool transactions which are visible on another node practically instantly. As in you cant do something faster by adding complexity. Retard.

I'm not upset, because you've falsely broken my hash, you have not even implemented 100% working one of it. There's coming a post about that once you get your Hive scripts to work. I'm upset because you are spreading false claims because of your continued fallacies in cryptocurrencies and trashing the one's who are years further than you. I mean who creates two hidden premines? I did not. Sompolinsky did not. Who thinks that GhostDAG blocks are processed in single linear line? I do not. Sompolinsky does not.

Also my answers to your bullshit research about Hoohash:
https://medium.com/@toni.lukkaroinen/cryptis-analysis-is-pure-fud-every-single-claim-is-factually-wrong-misleading-or-deliberately-274513b7470d
https://medium.com/@toni.lukkaroinen/cryptis-lies-about-hoohminer-6a44b7c46804

You can't even answer this: Why to change practically instantenous mempool transaction propagation which is only affected by real world latency into microblocks and intents which contain those mempool transactions and delay their propagation to 50ms batches? You have no answer to that because it's reason is in your writings that you are confusing transaction settlement to visibility and trying to compete with Kaspa and Nano transaction speeds.

By the way if my blogs are written by Grok, then even that knows that Cryptis your logic fails you.

I'm not spreading misinformation. I'm spreading the truth, the code speaks, the logic he writes speaks.

I just told you that Cryptis has not actually tested which mempool propagation is faster as he has both of them enabled on the Cryptix node at the moment. 

[HoosatNetwork]

Whatever you have written has already been proven false many times. No premine, no hidden coins. All false. Your grok AI couldn't understand HF-A, thats not our problem. Maybe try to increase its token limit. Stop bothering cryptix, go touch some grass and stop your obsession with cryptix and focus on your project.

That's an outright lie, since you yourself stated that code speaks and it's the truth.

CYTX had premine hidden from explorer and according to explorer about 11% of it was mined before shutdown and the total supply was 520,395,506 CYTX which means 57,243,505 CYTX was mined before CYTX shutdown.
CPAY had 144,547,200 CPAY deflationary period. That is 87,303,695 CPAY premine even still if Cryptis had replaced all the CYTX of everyone else to CPAY through Exbitron. The real number of replaced CYTX->CPAY is still missing. That is also false statement that all of them were exchanged, as there are many who did not replace, like myself. Funnily all of these statistics are gone from the current CPAY explorer.

So go fuck your anonymous wannabe developer in the ass, where he pulls his fallacious definitions and lies.

[HoosatNetwork]

The same lies and stories from you over and over again.

I have no need to lie, because you yourself cause the issues.

How could I have had a premine when the node code was published one month before release, and there were already miners on the testnet? That’s technically impossible.

And then the swap, which you call a “second premine”: we started with the exact same coin supply as before. The final difference was less than 500k coins — and we actually paid more coins to Exbitron for the swap service. So how exactly were we supposed to fairly swap users’ coins if we didn’t have any coins ourselves?

Coins that weren’t swapped on Exbitron were kept by Exbitron, because all of their hot wallets were fully swapped. Ask Exbitron instead of spreading lies. I’ve explained this multiple times already — apparently you either forgot or chose to ignore it.

That means we didn’t gain a single coin from the swap — we lost coins. But it was the best solution for users, and I paid that cost willingly.

That's an outright lie, since you yourself stated that code speaks and it's the truth.

CYTX had premine hidden from explorer and according to explorer about 11% of it was mined before shutdown and the total supply was 520,395,506 CYTX which means 57,243,505 CYTX was mined before CYTX shutdown.
CPAY had 144,547,200 CPAY deflationary period. As in premine, that is 87,303,695 CPAY more than even if Cryptis had replaced all the CYTX of everyone else to CPAY through Exbitron. The real number of replaced CYTX->CPAY is still missing. That is also false statement that all of them were exchanged, as there are many who did not replace, like myself. Funnily all of these statistics are gone from the current CPAY explorer.

Now about your nonsense regarding the current HFA system: you simply don’t understand it technically.
4000 lines of code for a mempool? Where do you think that code comes from, and what do you think it does? You can access the mempool via RPC without writing a single line of code. Just read the code. I know you can’t — but at least try.

And the configs on the seed server? You have no idea what’s running there. I know exactly what node code and configs I’m using — far better than you ever could.

We released the first version of step 1 out of 3 yesterday, with very conservative settings to ensure no nodes crash during stress testing. That’s how experienced developers work — with caution, not recklessness.

Speaking of crashes — how did your last hard fork go again? Exchanges had to disable trading for your coin because nodes were constantly crashing, if they even started at all. For 90% of users, nothing worked. You don’t even understand proper RAM usage or garbage collection. How do you even manage to make all nodes crash in Go? That’s actually impressive — I couldn’t even do that on purpose.

And honestly, it’s been annoying since day one — you and your toxic wannabe developers who have never built anything. Neither you nor your team.

Your coin has existed for 2 years now, and what do you have to show for it? Nothing.

Few hard forks with issues that were fixed all in few deays, does not destroy anything. Crashes because Golang Garbage collector can't keep up won't change anything. You don't know where we even are at this point running on RPi 5 with 5 BPS network. Unlike Cryptis you? Have you had single hard fork? Other than starting again from genesis. Even your HF_A did not disable anything, just added duplicate work for the CPAY node.

Just a terrible mining software that barely works, doesn’t meaningfully improve hash rate, and has minimal functionality. That’s maybe one week of work for a single developer — if they’re slow.

Plus a poorly implemented hash function — maybe 3 days of work. That’s your entire output after 2 years.

Just more bullshit from your mouth who can't even comprehend that Hoohash is deternministic on the GPU. Hoominer is proof of that and Hoominer is meant to be reference miner that just works and shows how the algorithm works.

Everything else?
Your explorer — old Kaspa explorer.
Your web wallet — old Kaspa web wallet.
Everything you have is just copy-paste from Kaspa and other developers, with a few lines changed.

After 2 years, you’ve built absolutely nothing. You’ve only messed around with other people’s code and made it worse, because you don’t know how to program.

That's more of bullshit when you have 1 year behind you and barely touched node code since yesterday.

Even your voting platform is built using frameworks and modules from other people — Remix Software Inc., Meta, TypeScript. You couldn’t even build something simple with HTML and JavaScript yourself. Everything you have is based on other people’s work.

And yet you accuse others?

More of bullshit, The voting platform has not been developed by myself. I have my own Typescript React Server Side Rendering stack and I wrote javascript before you were born.  

You have more dirt on your hands than any other crypto project. You hardcoded wallet freezes into your node — locking 10x more coins than there are buy orders across all exchanges. Even a fraction of those coins hitting the market would crash your price to near zero.

You deliberately removed users’ access to those coins to artificially inflate the price. That’s blatant market manipulation.

Your coin is no longer decentralized or non-custodial — it’s effectively an unlicensed company that you never registered.

More of your bullshit. Soft freezing Xeggex wallet was voted by the community and it's not even complete freeze as simple code modification can skip it. Retard.

 

Your mining software — marketed as the fastest — includes a hidden 10% developer fee. Because it’s the fastest, users are forced to use it. That’s extortion.

Not my mining software, retard. That is Foztors mining software and he has the fastest implementation of Hoohash and he can set whatever developer fee on his miners.

You made countless empty promises. Where is the marketplace after 2 years? There isn’t even a single line of code. Of course not — because you can’t program and you’re waiting for someone else to do it for you. Meanwhile, you attracted investors with those promises and deceived them.

I have never given an ETA on the marketplace and if you read the topic, that has been placed on the back burner because of all the regulations. Which I follow unlike you do. Retard.

You can’t even code — you’re just using a free version of Grok.

It took you over 10 years to complete a bachelor’s degree at a remote school — not even a real university. And you only managed that now because tools like Grok exist. Congratulations — must’ve been tough.

Instead of building anything, you spend your time writing blogs while your project dies more and more every day. There are barely any miners left. One pool controls 98% of the hash rate.

In the crypto space, you’re known as a clown who annoys everyone and destroyed his own project through his behavior. And still, you refuse to change.

And you seriously think you’re in a position to attack real developers — people who actually build and create progress? Without having achieved anything yourself?

You think you need to lie about other projects while running the biggest scam in crypto?

What exactly makes you think that?

Sit down. Learn how to program. Put Grok aside and actually learn it properly.
Build something. Innovate. Try to collaborate with other projects.

And stop constantly attacking others just to make yourself look better. It won’t save your project. It won’t make you better. It won’t help you.

And stop with your AI-generated Medium blog posts — it’s embarrassing, and you’re just making a fool of yourself.

Do something for your community — for the people who once believed in you and invested their money into your project.

I’m done responding to you. It’s always the same story, since day one.

Since day one, you’ve been attacking our project out of jealousy and envy, with zero regard for ethics, twisting facts and lying constantly.

I’ve already addressed every single one of your points multiple times.

Cryptix you are one of a kind of retard and next piece of your failures comes tomorrow.

You just proved that you don't even know how to read the blogs. FastChain decouple transaction validation from block acceptance, not HF_A. As your HF_A is only your mempool transaction propagation code which is slower than Kaspa mempool transaction propagation as you are adding little bit more validation and data types to mempool transactions propagation, which are validated completely when added to a block. As in it does not matter that even if you made the delay 0ms it would be slower than Kaspa mempool transaction propagation, because more code and complexity.

Your FastChain is more suspectible to “On-Spend” quantum attacks beacuse of the transaction lazy loading, when pushing more blocks.  

Stop pulling things apart and learn that you are one of a kind retard with your research lies and grow which you kinda have done a little bit by writing your own miner. Don't go spouting bullshit that your slow mempool propagation method is faster than something where transactions can be settled in a block in less time of than 100ms.

And no, it's not a mempool; Furthermore, there would then be no 4000 lines of code for the system, as a mempool is already included. I clearly stated that. And no, it's not slower than other things. It's maximum speed. Why not measure it? Use the correct configurations and run a local test; then you'll see how fast it is. There is currently no transaction visibility system worldwide that is as fast as HFA. You need to read the code and use a better AI. Grok isn't very helpful for understanding it. Or you could try learning programming languages ​​so that you can actually understand code correctly.

You're saying that it's not a mempool? You are injecting the intent transactions into peer nodes mempool, as in another method of mempool propagation. Just your supported stated that the transactions are not settled in your HF_A before inclusion to blocks. Your speed in HF_A is false statement as that moves more data than Kaspa mempool transactions which are visible on another node practically instantly. As in you cant do something faster by adding complexity. Retard.

I'm not upset, because you've falsely broken my hash, you have not even implemented 100% working one of it. There's coming a post about that once you get your Hive scripts to work. I'm upset because you are spreading false claims because of your continued fallacies in cryptocurrencies and trashing the one's who are years further than you. I mean who creates two hidden premines? I did not. Sompolinsky did not. Who thinks that GhostDAG blocks are processed in single linear line? I do not. Sompolinsky does not.

Also my answers to your bullshit research about Hoohash:
https://medium.com/@toni.lukkaroinen/cryptis-analysis-is-pure-fud-every-single-claim-is-factually-wrong-misleading-or-deliberately-274513b7470d
https://medium.com/@toni.lukkaroinen/cryptis-lies-about-hoohminer-6a44b7c46804

You can't even answer this: Why to change practically instantenous mempool transaction propagation which is only affected by real world latency into microblocks and intents which contain those mempool transactions and delay their propagation to 50ms batches? You have no answer to that because it's reason is in your writings that you are confusing transaction settlement to visibility and trying to compete with Kaspa and Nano transaction speeds.

By the way if my blogs are written by Grok, then even that knows that Cryptis your logic fails you.

I'm not spreading misinformation. I'm spreading the truth, the code speaks, the logic he writes speaks.

I just told you that Cryptis has not actually tested which mempool propagation is faster as he has both of them enabled on the Cryptix node at the moment.  

Too bored to answer all of your bullshit one by one. You don't have single truthful sentence in your long post. Great that you're wasting time defending yourself without keeping to the topic.

Why to change practically instantenous mempool transaction propagation which is only affected by real world latency into microblocks and intents which contain those mempool transactions and delay their propagation to 50ms batches?
Why keep both kaspa gossip mempool propagation on when you wrote your HF_A which also does mempool propagation and little bit of useless extra validation which is done when transacitons are added to a blog?
Which ones visibility speed you actually have tested as both mempool propagations are used concurrently?  

Yet you ask me to stop with all your bullshit? Not gonna happen. I've already said what needs to be done on your side if you want myself to stop checking your work and pointing where you're done wrong.

[Cryptix-Network]

You need to learn to read code, then you'll understand. And our seed nodes don't have a 50ms configuration; it's currently set to 1ms. As I said, for a first release, I can't set such values ​​for everyone, so it's 50ms by default, but with an extra start argument to allow users to choose freely. Can you still follow that, or are you already overwhelmed? This is called zero risk for the mainnet and also eliminates the centralization risk for weak nodes/hardware. That's how it's done: you start on a secure footing, run benchmarks and stress tests, and then use stronger values. But you're not a developer; you don't know that. But tell me a system where you see a transaction from wallet to wallet in 50ms? Then show me the system so I can test it. Even with the configuration, it's the fastest transaction visibility system for end users. I don't know of any faster one. And the next step, step 1 of 3, is that we will now also work on finding a Fastpath finalization method. We programmed it modularly; we can connect directly to HFA with HFB and HFC. I've told you this several times. But even here, you don't know what step 1 of 3 means, but I'll explain. It means there are two more releases and upgrades coming. 1 of 3 means there are two more to come. I hope you're still following and that I haven't overwhelmed you. And visibility doesn't mean finality; that's been clearly stated in all the documents, multiple times. But again, you don't understand the difference. You could ask Grok about that.

Sorry, but you're just making me angry with your questions and getting on my nerves. And I'm an impulsive person. I'm wasting my time, writing unnecessarily angry things, and letting myself be triggered by a toxic clown. That's why I'm ignoring you again. Develop something already! How about the marketplace? And maybe without copy-pasting and other people's work. Develop it yourself; you finally got your distance learning bachelor's degree after 10 years. I'm sure you could create an HTML page like that in about a year. With a lot of effort, you could even write CSS for it. Good luck!

[HoosatNetwork]

You need to learn to read code, then you'll understand. And our seed nodes don't have a 50ms configuration; it's currently set to 1ms. As I said, for a first release, I can't set such values ​​for everyone, so it's 50ms by default, but with an extra start argument to allow users to choose freely. Can you still follow that, or are you already overwhelmed? This is called zero risk for the mainnet and also eliminates the centralization risk for weak nodes/hardware. That's how it's done: you start on a secure footing, run benchmarks and stress tests, and then use stronger values. But you're not a developer; you don't know that. But tell me a system where you see a transaction from wallet to wallet in 50ms? Then show me the system so I can test it. Even with the configuration, it's the fastest transaction visibility system for end users. I don't know of any faster one. And the next step, step 1 of 3, is that we will now also work on finding a Fastpath finalization method. We programmed it modularly; we can connect directly to HFA with HFB and HFC. I've told you this several times. But even here, you don't know what step 1 of 3 means, but I'll explain. It means there are two more releases and upgrades coming. 1 of 3 means there are two more to come. I hope you're still following and that I haven't overwhelmed you. And visibility doesn't mean finality; that's been clearly stated in all the documents, multiple times. But again, you don't understand the difference. You could ask Grok about that.

Sorry, but you're just making me angry with your questions and getting on my nerves. And I'm an impulsive person. I'm wasting my time, writing unnecessarily angry things, and letting myself be triggered by a toxic clown. That's why I'm ignoring you again. Develop something already! How about the marketplace? And maybe without copy-pasting and other people's work. Develop it yourself; you finally got your distance learning bachelor's degree after 10 years. I'm sure you could create an HTML page like that in about a year. With a lot of effort, you could even write CSS for it. Good luck!

The insult does not matter, neither that your seed nodes have set the HF_A delay at 1ms. If you can not read your own code that you are propagating mempool transactions through HF_A and through the kaspa gossip protocol simultenously, then I have to say you are nowhere to say that I should learn to write code. As `receive_transactions` nor it's starter does not check if HF_A is enabled or not. That means Kaspa mempool propagation is working at the same time as you HF_A mempool propagation.

- You are confusing transaction visibility of mempool transaction over transaction visible on a block and being confirmed and finalized.
- You can't finalize transaction before it has settled on a block.

I don't care if i'm making you angry as i'm having fun when you can't comprehend something. Apologize to your community for your continued lies, then we can talk without all this negativity. Though it's actually funny how out of whack you are with even your own technology as you are with my life and HTN project.  

Are you even able to answer what `validate_and_insert_transaction_batch()` does? The Kaspa function which your HF_A calls when new fast intents are submitted to node through RPC or P2P.

[HoosatNetwork]

You need to learn to read code, then you'll understand. And our seed nodes don't have a 50ms configuration; it's currently set to 1ms. As I said, for a first release, I can't set such values ​​for everyone, so it's 50ms by default, but with an extra start argument to allow users to choose freely. Can you still follow that, or are you already overwhelmed? This is called zero risk for the mainnet and also eliminates the centralization risk for weak nodes/hardware. That's how it's done: you start on a secure footing, run benchmarks and stress tests, and then use stronger values. But you're not a developer; you don't know that. But tell me a system where you see a transaction from wallet to wallet in 50ms? Then show me the system so I can test it. Even with the configuration, it's the fastest transaction visibility system for end users. I don't know of any faster one. And the next step, step 1 of 3, is that we will now also work on finding a Fastpath finalization method. We programmed it modularly; we can connect directly to HFA with HFB and HFC. I've told you this several times. But even here, you don't know what step 1 of 3 means, but I'll explain. It means there are two more releases and upgrades coming. 1 of 3 means there are two more to come. I hope you're still following and that I haven't overwhelmed you. And visibility doesn't mean finality; that's been clearly stated in all the documents, multiple times. But again, you don't understand the difference. You could ask Grok about that.

Sorry, but you're just making me angry with your questions and getting on my nerves. And I'm an impulsive person. I'm wasting my time, writing unnecessarily angry things, and letting myself be triggered by a toxic clown. That's why I'm ignoring you again. Develop something already! How about the marketplace? And maybe without copy-pasting and other people's work. Develop it yourself; you finally got your distance learning bachelor's degree after 10 years. I'm sure you could create an HTML page like that in about a year. With a lot of effort, you could even write CSS for it. Good luck!

The insult does not matter, neither that your seed nodes have set the HF_A delay at 1ms. If you can not read your own code that you are propagating mempool transactions through HF_A and through the kaspa gossip protocol simultenously, then I have to say you are nowhere to say that I should learn to write code. As `receive_transactions` nor it's starter does not check if HF_A is enabled or not. That means Kaspa mempool propagation is working at the same time as you HF_A mempool propagation.

- You are confusing transaction visibility of mempool transaction over transaction visible on a block and being confirmed and finalized.
- You can't finalize transaction before it has settled on a block.

I don't care if i'm making you angry as i'm having fun when you can't comprehend something. Apologize to your community for your continued lies, then we can talk without all this negativity. Though it's actually funny how out of whack you are with even your own technology as you are with my life and HTN project.  

Are you even able to answer what `validate_and_insert_transaction_batch()` does? The Kaspa function which your HF_A calls when new fast intents are submitted to node through RPC or P2P.

Can Cryptis answer what  `validate_and_insert_transaction_batch()` does? The Kaspa function which your HF_A calls when new fast intents are submitted to node through RPC or P2P.

I'll give you a tip, the function name is kind of misleading.

[HoosatNetwork]

About an hour and I can post next medium article as negative truthful marketing about Cryptix Network. Let the flame war continue until Cryptis you will answer these programming questions i'm asking and apologize to your community for your lies.

1. Can Cryptis answer what  `validate_and_insert_transaction_batch()` does? The Kaspa function which your HF_A calls when new fast intents are submitted to node through RPC or P2P.
2. Why did you Cryptis change practically instantenous mempool transaction propagation which are only affected by real world latency into microblocks and intents which contain those mempool transactions and delay their propagation to timeable batches?
3. Why Cryptis did you keep both kaspa gossip mempool propagation on when you wrote your HF_A which also does mempool propagation and little bit of extra validation on the transactions, which is done also when transactions are added to a block?
4. Which ones visibility speed you actually have tested as both mempool propagations are used concurrently if HF_A is enabled?  

[HoosatNetwork]

🦉Why network wide “ Terms of Use” Are Fundamentally Bad for Miners 🦉

Here a blog post about topic of network wide Terms of Use and how they are bad for miners and cryptix network used as an example what kind of person is in lead of the project and can shut down miners who are just mining supposedly decentralized cryptocurrency project.

https://medium.com/@toni.lukkaroinen/why-network-wide-terms-of-use-are-fundamentally-bad-for-miners-848ee70a21e6

Have fun Cryptis. Answer my questions about HF_A code and apologize to your community for your lies and I'm finished with my negative truthful marketing. More coming, over 20 topics to go through and several web projects you've created. Then maybe afterwards a curated list of reading material for those who are thinking of investing in the cryptocurrencies you've touched. More like, this blogger just got an idea, make a book of "Cryptis, the misleading lies of an anonymous wannabe that forked Kaspa." 

[ptaank]

🦉Why network wide “ Terms of Use” Are Fundamentally Bad for Miners 🦉

Here a blog post about topic of network wide Terms of Use and how they are bad for miners and cryptix network used as an example what kind of person is in lead of the project and can shut down miners who are just mining supposedly decentralized cryptocurrency project.

https://medium.com/@toni.lukkaroinen/why-network-wide-terms-of-use-are-fundamentally-bad-for-miners-848ee70a21e6

Have fun Cryptis. Answer my questions about HF_A code and apologize to your community for your lies and I'm finished with my negative truthful marketing. More coming, over 20 topics to go through and several web projects you've created. Then maybe afterwards a curated list of reading material for those who are thinking of investing in the cryptocurrencies you've touched. More like, this blogger just got an idea, make a book of "Cryptis, the misleading lies of an anonymous wannabe that forked Kaspa." 

Actually thanks for this. We will enjoy every bit. You're helping in pumping CPAY 🚀🚀

[HoosatNetwork]

🦉Why network wide “ Terms of Use” Are Fundamentally Bad for Miners 🦉

Here a blog post about topic of network wide Terms of Use and how they are bad for miners and cryptix network used as an example what kind of person is in lead of the project and can shut down miners who are just mining supposedly decentralized cryptocurrency project.

https://medium.com/@toni.lukkaroinen/why-network-wide-terms-of-use-are-fundamentally-bad-for-miners-848ee70a21e6

Have fun Cryptis. Answer my questions about HF_A code and apologize to your community for your lies and I'm finished with my negative truthful marketing. More coming, over 20 topics to go through and several web projects you've created. Then maybe afterwards a curated list of reading material for those who are thinking of investing in the cryptocurrencies you've touched. More like, this blogger just got an idea, make a book of "Cryptis, the misleading lies of an anonymous wannabe that forked Kaspa." 

Actually thanks for this. We will enjoy every bit. You're helping in pumping CPAY 🚀🚀

Great that you appreciate well written text on a topic that touches more than the negative issues in Cryptix Network. It's not just the tech, it's also the fundamental governance model of Cryptix Network that drives miners out. 

[HoosatNetwork]

🦉What is Cryptix Quantum Mining Protection 🦉

Let's go back to the roots. Cryptix Network (CYTX) was launched with single mission, to copy Hoosat Network vision. Until Cryptis realized that he needs to reiterate to many different things as he could not keep up with Hoosat Nocturne nor Kaspa Crescendo hard forks, which is why he invented FastChain. But what did Cryptis try to copy from Hoosat Network in the begginning? That is the evolution of quantum safe mining. Which has been enabled in Hoosat Networks 5 BPS main network since January 2025, just few weeks before Cryptis decided to try better than Hoosat Network.

That is Cryptis first research -> Quantum Mining Protection through midstate hashing and his false claim, without increasing computational cost. Why Cryptis has not implemented it in a year?

https://medium.com/@toni.lukkaroinen/what-is-quantum-mining-protection-68215cb32730