The Elephant in the Room – and this time, it’s a good thing
You can interpret “the elephant in the room” as having a negative connotation, something that must be addressed urgently. You can also interpret it as the absolute truth – something obviously existing and having a positive impact.
The impact:
Kasplex delivered working products. Some can argue that it was a disaster for Kaspa (as per my presentation in Berlin) it depends on what hat you’re wearing or through which lens you’re viewing the KRC20 launch.
It brought more visibility, acknowledgment, and awareness to Kaspa. It stress-tested the entire network. It helped developers observe, analyze, and act on issues that didn’t exist before or on parts that needed improvement.
It allowed random/unknown teams to start building on top of Kaspa. It enabled the environments needed and created new communities. It opened the doors for people outside the KAS ecosystem to ask, “What is Kaspa?”
KRC20 (as you can see in the slides) enabled millions of transactions on Kaspa – actual transactions. It brought hype, hope, and people. Users and teams benefited greatly from it.
Some of those people/teams are now saying KRC20 was a disaster, while knowingly hiding or omitting the fact that they made millions – yes, millions. They claim we would have been better off without it.
KRC20 could have been easily cannibalized by its creators with wallets, bots, or tools. It didn’t happen. Instead, it made it possible for builders to appear and develop.
Was it a disaster?
Layer 2 – the elephant in the room
Kasplex’s Layer 2 is the next working product that has been tested for quite a few months. It enables 100% EVM compatibility on top of Kaspa. This will allow both existing teams and new ones to bring value to Kaspa via the L2.
Kasplex has proven itself before (one can argue it didn’t) and it will prove itself again, soon enough.
Kasplex raised zero money as a non-profit organization (because of funding from KEF) to deliver the L2 and offer it for free to the entire community. It owes nothing to anyone. It is another endeavor to push Kaspa further – an engine that makes the wheels spin.
Is it perfect? Of course not. But then, why use it? Because you can choose to. And if you don’t want to, you don’t have to.
Could Kasplex cannibalize the tools needed around the Layer 2? Of course they could. Will they do it? Of course not.
It will allow the same teams that are fudding, soft-fudding, or directly attacking Kasplex to deploy their products and benefit financially. This is not about goodwill; this is simply how things work. It’s permissionless, and no one keeps the gates closed.
“There is no documentation, it’s closed source, the audit is insufficient, there’s no clarity.”
There is no perfect man/woman/product out there. You cannot be handsome, smart, healthy, rich, have a happy family, and be a successful person all at once. You need balance. You make trade-offs. You cut from the left so that the right can be improved. You balance quantity versus quality.
You need manpower, money, and time.
Are these excuses? That depends on the angle you’re looking from.
“You are biased.”
Of course I’m biased. But my biases are not what some people think. They come from working directly with Kasplex, meeting the people behind it, and seeing their actions, focus, and dedication.
I’ve always said I will be the first to raise a red flag if I see something suspicious. Like you, I am part of the community and my heart belongs to Kaspa as a whole. Believe it or not, there has been zero situation, moment, or message that has made me think “hmmm.”
“You represent Kasplex, you are full of…”
This message – like ALL of my personal messages – wasn’t “reviewed” by anyone and I didn’t ask for “permission” from anyone.
Zoom out
You need to zoom out, give yourself time, and analyze all the pieces of the puzzle. Then make your own intelligent analysis of how Kasplex has helped the ecosystem. You may come to the conclusion that it didn’t – and that’s fine.
I’ve collaborated with two projects before and terminated them the exact moment I felt things were wrong.
“Why this tweet? No one asked.”
Because you need to think. Think, think, think. Take off the horse glasses, analyze everything from every angle, and then make your own judgment.
Will the Layer 2 be a flop?
In my opinion, there are three scenarios:
A major flop – no one cares about Layer 2 or Kaspa.
A major success – everyone jumps in, third-party teams join and build.
Something in between – nothing crazy, nothing lazy.
I guess we’ll soon enough find out how things will play out.
Closing thoughts
This space is volatile. You see people leading others. You see people being led. You are bombarded with information, and you cannot trust anyone.
No one asked me to share these thoughts, just a brain dump for the hours i've spent thinking about it.
(Don’t trust me either – trust only your judgment, heart, and gut.)
Time will tell.
Long live
$KAS.