https://t.co/8XHMdww3uC, one of the most widely used Kaspa explorers, announced it is winding down operations, citing usability concerns.
In response, Yonatan Sompolinsky stated that funding can be arranged to keep https://t.co/hWiLJOQd3V operating if needed. He also noted that similar support could be considered for other community-used and well-loved Kaspa projects currently facing financial difficulties.
Additionally, Yonatan interest in Kaspa’s technology from teams within the Solana and NEAR ecosystems, as well as others, highlighting increasing external attention to Kaspa’s DAG architecture.
Regarding DAGKnight - the cascade voting isn’t implemented yet nor is the code here in any way mainnet or testnet ready yet, but I do have a vanilla static-DAG based impl that has core components of the protocol like hierarchic conflict resolution and incremental coloring in place.
I was working on this on a private repo, but what the heck, I pushed it out in my rusty-kaspa fork if anyone wants to see.
@michaelsuttonil I think it’s time to share that long overdue post soon.
The attached image shows a view of what the DK parent selection looks like from the pov of the next block to be mined (block 64). It correctly selects a parent from the supposed “honest” cluster. The blue line is the VSPC.
$KAS founder was an expert in Bitcoin security long before KASPA. He was one of the 1st to do a reasonable security audit of $btc
$avax & $eth founders talk about his research👇
He also invented GHOST that Vitalik based Ethereum on
A decade of improvements later, KASPA is born
I’ve have been thinking a lot about what happened with the Binance Top 100 contest. Yonatan Sompolinsky (@hashdag ) Kaspa founder, was voted the number one independent researcher. @michaelsuttonil was voted the number three industry advocate. Both results came straight from the community, not from an exchange or a marketing machine.
Then Yonatan publicly said he would not attend the Binance event where the awards were going to be handed out. It was mostly a protest against exchanges listing silly meme coins while ignoring this century’s greatest advancements in internet speed digital money. Calling them out from going wayward from the original version of cryptocurrency.
This weekend Binance gave the trophy to the second place winner and never mentioned Yonatan at all.
There is a lot wrapped up in that moment.
Right after Yonatan’s protestpost, @Kaspa_Commons used a simple phrase in a post as an acknowledgment to the potential for Kaspa to find greater use cases outside Cryptoland and as a small dig at the exchange.
Nov. 7
Can you imagine?!
"Tokens backed by real multibillion dollar assets that actually have utility and generate revenues for decades."
@Kaspa_Commons can.
@KaspaKii can.
👋🏼Bye-nance, enjoy Cryptoland and your millions.
That simple tag, “Bye-nance”, seemed to resonate and a small rebellion started. Bye-nance was a direct message, a goodbye to Binance that encouraged others to step away.
After the award ceremony failed to mention Yonatan’s name, the community responded in force. That little pebble dropped in the pond was becoming a tsunami. A huge wave of Kaspians have been dropping the tag and deleting their accounts and Binance is clearly not thrilled about it. We have yet to verify this, but I heard that Binance approached @Kaspa_KEF reps to ask them to encourage the community to stand down. 🤣
But the bigger story is what this whole episode reveals.
First, the Kaspa community is one of the most engaged and passionate groups in the entire blockchain space. The voting proved it. The unified response after the snub proved it. People showed up for Yonatan because he has shown up for the principles that matter.
Second, this was a chance for crypto to take a stand again. Yonatan did. It reminded me that Bitcoin began as a protest against captured institutions. It was a push for self sovereignty, economic freedom, and independence from the usual gatekeepers. Over time, the space drifted. Memes, speculation, and exchange driven hype drowned out the deeper purpose.
Seeing the reaction this week makes it clear that a new wave of cypherpunks is rising again. Builders who care about research, engineering, and integrity. Researchers like Yonatan. Developers like Michael Sutton. And communities like Kaspa. People who want crypto and blockchain tech to mean something again.
Third, the whole thing exposed the true nature of some of these L1 exchanges and classic crypto in general. The incentives. The politics. The greed. The selective celebration. The silence when the results do not serve their interests. Many people are looking at that and deciding they are done.
So let us not waste this moment. What we just saw is a big opportunity. An opportunity to show the strength of our community. It is obvious. An opportunity to reintroduce a modern cypherpunk spirit. It is happening. An opportunity to shine a light on the difference between real builders, real solutions, and the bad actors inside the Cryptoland circus.
The original Bitcoin movement of protest was against real world finance and government control. It is interesting and ironic that Kaspa’s latest protest is against the dark side of Cryptoland itself.
Let us not waste this moment. And even though we are focused on one exchange and their actions, we need to turn our backs on the entire Cryptoland mindset.
Let us start here. Everyone, say it with me. 👋🏼 Bye-nance
@cryptocom ~ @hashdag
https://t.co/0ioZwMxRd2
Objectively, the traits of digital silver require both moneyness and sound SoV as well as unmatched speed for MoE. In other words, attributes only a 10BPS PoW system can claim
I want, perhaps for the first time ever on this platform, to write a post from a personal perspective. This post isn’t going to address any other person, and as such, I would appreciate not receiving any sharp-tongued comments or personal remarks about any particular case. Read the post as it is, or ignore it. Please respect my personal request, at least in this one instance, even if every fiber of your being rebels against what you perceive as an injustice.
For the last three years, my entire sphere of activity, the one that consumes all my time and energy, has been Kaspa. The development of Kaspa. The research of Kaspa. Where the coin is today. And which line of code will run tomorrow. I don’t work on Kaspa to become a rich man. My life’s goal is not to make a lot of money and retire. I enjoy fundamental, deep research in computer science, and I am especially thrilled when I have the privilege of applying it at scale in the real world.
I believe I have the right to claim that I care about Kaspa as a collective. I care about the whole that is greater than the sum of its parts. As a person of faith, I believe I have been granted the privilege of being a conduit for some of the science that constitutes Kaspa. For the discovery of this science in the world. And for its complete implementation.
Along with this privilege comes great responsibility. In Kaspa’s first year, I was under constant stress. Returning from any weekend or period of disconnection was met with the feeling that anything could happen. All hell could break loose. The pounding of my heart at the crescendo moment didn’t subside for weeks.
At a certain point, as a lead developer and researcher, you discover that your responsibility extends beyond the technical domain. That as a creator and, in effect, a continuous founder of the technology, you have a growing responsibility for the proper communication of this thing you are an essential part of creating. We are, admittedly, in a decentralized open-source community, but the creation process ultimately comes from specific people, and no one else can authentically reflect the essence of the creation and its strengths more than those who continuously forge the path itself.
This responsibility is both a community and a project-level one. You find yourself in a situation for which your academic degrees did not prepare you. Luckily for me, if you were to tell people who know me in my personal life that I only understand zeros and ones, they would find it deeply amusing. Until a few years ago, I actively managed a social media community of thousands of people that led and was part of a social change. Anyone who knows me or has even worked closely with me will tell you that my emotional intelligence is no less than my intellectual one.
With great responsibility comes the capacity for error. I can be wrong. Like any human being. But I ask here for the right to a minimum of respect and appreciation for my integrity and the purity of my intentions. I have no ego when it comes to Kaspa and its creation. And I am happy (and actively working) to share in its future creation and to give credit for the past to all who deserve it. Every action I take within the Kaspa space stems from my belief that it is for the good of the project. And from my belief that although I am primarily a researcher and developer, I have an angle and a complete perspective on the project that is nearly unrivaled. Sometimes, you are deeply and intuitively convinced of something, but it takes time to clearly articulate the crux of the problem and the argument. And still, the urgency mounts, and so you are forced to act. And when you try to explain your reasoning to people without the full context, you only manage to reflect fragments of ideas that don’t always connect for the perplexed observer and sometimes even seem contradictory. If, for example, I wrote a line about Kaspa’s market value and you believe it could be interpreted in a personal, unfair manner, do not attack and sting me based on your wrong assumption. Ask honestly what I meant, and you might be surprised by the answer.
(In that specific case, I was speaking about my assessment, and that of others smarter than me, that a fundamental change in Kaspa’s social media presence is required for us to break through in the market cap rankings towards the top ten. I wasn’t referring to the price noise of the past year, nor am I influenced by it. I operate under the complete belief (a kind of knowing) that Kaspa will reach its rightful place in terms of market weight. I also didn’t blame any individual. I spoke of a perception and an approach that, in my view, have a glass ceiling. And I prioritized the common good, as I thought and felt that this truth needed to be heard, even if there are individuals for whom it could be interpreted as criticism.)
In the same vein, and as in the example above, so it is with every community and social action I’ve taken recently. You can, of course, argue and believe that I was mistaken; that is certainly a possibility. But I ask to be given the credit that I, at least, believe I am doing the right and critical thing for the Kaspa community and project as a whole. And that I have a basic social and philosophical analytical ability that grants me the right to my own opinion in these areas as well, even if I am mainly a developer and researcher who deals with abstract combinatorial ideas and code. I don’t have to be a marketing expert to express a crypto-philosophical opinion on the source and authority of core ideas for something that I am a continuous part of creating.
Thank you for reading this far. I sincerely appreciate it.
My next post will be out tomorrow, and it will discuss something cool and immediately relevant to Kaspa that myself and others have been working on these past few days. After that, or at least in the near future, Yonatan or I, or both of us, will try to outline Kaspa’s roadmap for the next one to two years, up to the achievement of zk/dk.
I want to return to the topic of Kaspa and MEXC. Some people accuse me of spreading FUD, so let’s take a look at the facts.
I’ve been a Kaspa investor since early 2022. I witnessed every listing and even lost some Kaspa when Exbitron was “hacked.” So I have a certain sense for how exchanges operate.
In my opinion, something about MEXC has been extremely noticeable since 2024. With Kaspa, there are “technical issues” two to three times a month. Just check Kaspa Telegram groups and search for the term "MEXC." You’ll find countless messages about MEXC once again suspending deposits or withdrawals. How is that possible? Other major exchanges like KuCoin, Bybit, or Bitget almost never have this problem — maybe only briefly during node updates. But with MEXC, it’s a constant issue. Almost every second week, withdrawals are suspended or slowed down, and it’s always due to “technical problems.” That’s a fact! Now everyone can think about why this might be the case. In my view, there are only three plausible explanations:
MEXC has the worst devs in the entire crypto space, if even small, irrelevant exchanges can integrate Kaspa without issues.
MEXC no longer has all the users’ Kaspa coins. It could be that MEXC doesn’t have enough Kaspa to cover all user withdrawals if everyone decided to withdraw. Supporting this theory: whenever larger amounts are withdrawn from the MEXC wallet, withdrawals are suspended or slowed down. Before the last suspension, about 10% of the coins were withdrawn from the MEXC wallet.
MEXC is manipulating the price. People often say: “But what would they gain from that?” The answer is: futures. They halt deposits and withdrawals so that holders can’t react to price fluctuations, and then the price is pushed either up or down — depending on whether they want to liquidate as many longs or shorts as possible. They could also take positions themselves and use the profits to buy back the Kaspa they dumped to crash the price. MEXC can do this because no other exchange has enough volume to counteract it. By closing deposits and withdrawals, arbitrage trading is also hindered.
In my opinion, it must be one of these three options. If it's point 1, then MEXC is simply technically poor and incompetent. But in my eyes, options 2 and 3 — or a combination of both — are more realistic.
What do you think? Please explain your reasoning instead of just shouting "FUD."