Today is the day the internet can collectively wave goodbye to the “everybody grieves differently” storyline.
There is no sane widow who could suffer her husband’s public assasination and then agree to handover his final private moments captured with his children to Andrew Wilson so that he can troll the internet while raising money.
It is such a disturbing development that there is no other rational determination other than Erika is a deeply disturbed individual. She shouldn’t be able to look at footage that precious without swelling with tears. To instead choose to publicly dishonor your late husband by allowing his last private moments captured on earth with his kids to be chopped and screwed and handed over to Andrew Wilson for no objective reason outside of internet trolling demonstrates, yet again, that something is emotionally and spiritually amiss with Erika Kirk.
This not a regular PR blunder. It registers to the public as psychotic. Full stop.
Young Oregon Patriots have arrived at the ICE Building in Portland to support ICE and the incoming troops!
These guys are in HIGH SCHOOL. Charlie would be proud.
Let’s go!!
$kas
When I made the last post about @kasplex's huge screw-up, I was just like "yeah, I knew they will screw it up".
But as I read the details, I'm kinda amazed to see how this is exactly what I was warning about.
Recall: the shitstorm between me and KEF started when I raised a flag about their trust model. I claimed that without resolving the trust issues, it would be reckless to launch the mainnet.
Before making the public announcement, I insisted in closed conversations that they resolve it and even offered my help for free!
After months of them ignoring me, I told them that I would go public with this, and the next thing I knew: KEF cut my funding and started a mass slander campaign against me. Which a lot of people in the Kaspa fanbase followed without hesitation, sweeping along "upstanding community members" like Christian Ludwig and Christopher "Wolfie" Wolf, and of course, Michael Sutton and Yonatan Sompolinsky, who gladly participated in libeling me to make the community complacent about KEF's recklessness (though I reckon only Ludwig and Sompolinsky were willfully in on it, and the other two were manipulated).
So instead of the professional discussion about security I tried to hold, each time I tried to be critical of KEF, I found most of my energy wasted defending my integrity to people who didn't even bother to read the details. Naturally, I just gave up at some point. I was tired of trying to help and only getting abused in return.
About a year and a half later, my warnings materialized exactly as I warned in my initial post. We've seen an initial trickle in the form of KEF/Kurve robbing Kaspa users with exorbitant fees that weren't sufficiently disclosed. And now, lo and behold, just as I warned, a rogue indexer drained wallets.
Junni Ho from KEF kept downplaying my warnings and tried to soothe the community by convincing them I'm latching onto non-issues out of personal pettiness. Well, if you want evidence that what I insisted on actually matters, here it is. Unfortunately, in the form of real money stolen from real people.
I don't expect any apologies from people who thought my insistence on facing constant abuse was out of spite, and not out of concern. It is what it is.
Below is the initial post, the alleged "declaration of war". (Notice, in particular, Michael Sutton rushing to Kasplex's defense.) Reading it today, the only thing I regret is the apologetic tone. I was trying to be diplomatic. What a fool I have been.
@JoelKlattShow@joelklatt@WSJ@DRWoodin If you'd like to support my work, here's my substack - with multiple stories, photos/analysis on this exact topic. Thank you!
https://t.co/r3WwV9Tcrb
I’ve respected and admired @joelklatt for years. Fantastic analyst.
This is wildly disappointing.
Working with @DRWoodin, we broke this news first - and stood firm when it was initially dismissed.
I’m an independent journalist trying to get my substack going
WATCH: Devon Jackson hit 22.9 MPH on this chase down! The fastest max speed for a linebacker on record for us. #ReelSpeed
100 IGA Score™ - Elite In-Game Athleticism™
Hey guys,
It's been a while since my last post, and I feel almost bad for not posting anything for such a long time 🙈
Unfortunately, I caught a really nasty infection on my way home from the KAS meetup and have been stuck in bed with a high fever and brain fog for the last few weeks.
I'm still not completely back to normal, but since I'm finally starting to have a bit more energy, I wanted to use the opportunity to share some thoughts about the meetup, because I think it will turn out to have been extremely influential for the future of Kaspa.
For anybody who doesn't know what I'm talking about: about 3.5 weeks ago, KAS organized an internal meetup between core contributors (and some additional community developers) at an undisclosed location in Europe.
When I first learned about the plans for this meetup, I didn't really know what to expect.
I've been to developer meetups before, but those were traditionally very narrow and task-focused. E.g. you got a team together to work on a specific problem that was difficult enough to deserve the shared attention of everyone involved.
In the case of Kaspa, however, we have relatively small and independent teams working on a number of different topics in parallel, such as vprogs, covenants, SilverScript, Argent, etc.
There are, of course, interfaces between these topics, but they all have their own independent designs and problem spaces.
This independence of developers is one of Kaspa's biggest strengths, but it also creates a situation where not everybody is always fully up to speed with what is happening elsewhere in the project.
For me personally, this is probably the biggest obstacle to becoming an effective communicator.
To feel confident discussing things publicly, I need to develop a deeper understanding and intuition for the subject. And that requires knowing not only the final design or code, but also the roads that weren't taken and the mountains that had to be climbed along the way.
What Kaspa really needed, wasn't a narrow, task-focused meetup, but a broad, vision-building one: something that connected the dots and allowed the different teams to develop a deeper understanding of each other's work, and ultimately see how all of it fits together as a coherent whole.
And the reason I'm telling you all of this is that this is exactly what the meetup turned into.
A week of open sessions and discussions covering the different development efforts, giving everyone the opportunity to build that deeper shared understanding.
I think it was a huge success!
I'll write a little more over the coming days about specific topics like Argent (which I really like), but I also have quite a lot to catch up on after being sick for so long.
@Max143672 did a really good job working through a lot of the open tasks around vprogs, and I now have a lot of code to review :'P
A lot of people think what makes Kaspa unique is the technology.
But the technology is really the consequence of a deeper philosophical difference.
Most crypto projects ask: How can we maximize performance without sacrificing decentralization?
Kaspa asks: How can we maximize decentralization without sacrificing performance?
That slight inversion of priorities changes everything.
It changes what the system optimizes for, which tradeoffs are acceptable, and ultimately what kind of threat model matters.
Kaspa and in particular the upcoming DAGKnight fork are built around the idea that a decentralized monetary network should remain resilient even under extreme failure scenarios like global infrastructure disruption, war, or other large-scale breakdowns.
Because fast digital coordination should not force people to choose between trusting a small group of node operators over a small group of banks.
For many applications, that distinction may not matter.
But for the applications where credible neutrality, censorship resistance, and resilience matter most, that ideological edge is the product.
Kaspa does not merely compete at the technological level.
It competes at the philosophical level and the technology is just the downstream consequence of following that philosophy to the end.