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-274513b7470dhttps://medium.com/@toni.lukkaroinen/cryptis-lies-about-hoohminer-6a44b7c46804You 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.
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.
