Pavel Emdin

Co-founder and busy bee @ Igra Labs | emdin.eth | Assorted cartoon character

[Pavel Emdin @emdin]

@p4bpj @michaelsuttonil We're working with Kastle, Kasware, Kasperia, Zelcore, Kurncy, and made sure they aware of changes upcoming.

[Pavel Emdin @emdin]

@Denzel781140 You don't need native stables, you need BD who has access to these kind of deals + arguments for using your infra. Not sure what "AI agents contender" means.

[Pavel Emdin @emdin]

This. Incentives, fair sequencing, MEV resilience, alignment over raw throughput is exactly what EF just codified with CROPS. "Maximizing throughput is a mistake that leads to mediocrity". Better infra is both pragmatic and future-proof. Kaspa core is building the perfect base layer, and shipping it at the speed of their own finality. Looking forward to June 9, marked my calendar.

[Hans Moog @hus_qy]

That's a really good question, but it's hard to answer in a single tweet because our mission is quite extensive, and it requires a lot of background knowledge to really understand what sets Kaspa apart.

Currently, a lot of people see Kaspa as “Bitcoin’s crazy little brother” that improves time-to-finality by leveraging the benefits of DAG-based consensus protocols without accepting their traditional drawbacks, such as decreased decentralization or a limited validator set.

This perception is somewhat accurate, but it falls short of conveying the full picture, because Kaspa’s vision extends far beyond just trying to be a better Bitcoin.

Anyone willing to study Kaspa and its broader vision will discover similarities to nearly all major existing DLT designs: from Bitcoin, to Ethereum, to Solana, Sui, Celestia, and beyond.

My personal view is that “research” in the DLT space is approaching a point of convergence. We increasingly understand how to push distributed systems close to the limits of what physics permits. The frontier is no longer only about raw throughput or faster finality. The attention is shifting toward game theory, incentives, sequencing, MEV, alignment, and how to build systems where the economic incentives of users, builders, miners, validators, applications, and infrastructure providers do not work against each other.

That is why debates like based rollups versus arbitrary sequencing, shared sequencing, MEV mitigation, proposer-builder separation, and execution-layer incentives matter so much. These are not niche technical details. They determine whether a network can remain neutral, decentralized, and aligned while scaling to global usage.

And this is where I think Kaspa is pushing the boundaries in a very important way.

Kaspa is not merely trying to be “fast.” The goal is to build an L1 where speed, decentralization, security, and incentives are aligned at the base layer. A system that does not scale by hiding complexity behind trusted committees, privileged sequencers, centralized validator sets, or opaque coordination mechanisms, but instead tries to preserve the spirit of proof-of-work while extending what an L1 can realistically do.

Because Kaspa arrived later than many other major projects, it does not carry the same degree of technological debt. It can absorb lessons from Bitcoin, Ethereum, rollups, modular blockchains, high-throughput monolithic chains, DAG research, MEV research, and the broader history of decentralized systems, and combine those lessons into something more optimal.

To me, that is what Kaspa is building: not just a faster blockchain, but a more incentive-aligned decentralized infrastructure layer.

But this also creates a different challenge.

Kaspa’s biggest problem today is not its technology. It is the lack of centralized coordination around communicating the vision. And because Kaspa is a grass-roots movement, that responsibility does not belong to a marketing department, or a single leadership team. It belongs to the community.

That also means the community has a different role to play.

There will always be holders who are mainly interested in price, and that is completely fine. But there also need to be people who are here because they want to use the technology to build a different future. People who care about the architecture, the incentives, the open questions, the trade-offs, and the long-term trajectory of decentralized infrastructure.

I am one of those people.

I am not interested in DLTs merely as a way to generate wealth. I am interested in them because I believe they can change the trajectory of humanity as a whole.

For that reason, I want to use this opportunity to announce a regular community hangout where we discuss the current state of development, the open questions, and where we can align our vision together.

The first session will be on Tuesday, June 9th, 2026.

We will talk about the vProgs framework, how the codebase works, what sets Kaspa apart, where we improve on existing solutions, and what still needs to be done. The goal is for this to become a regular, possibly bi-weekly, event where we as a community come together to discuss the future and understand the technology.

Eventually, we can invite people from other projects as well, but the main focus at the beginning will be explaining and communicating how things work under the hood.

There is still a lot of work to be done, and I do not want to waste precious time. So the first sessions may feel a little improvised, but we can improve as we go.

The important thing is that we start.

So mark the date: Tuesday, June 9th, 2026.

[Pavel Emdin @emdin]

@FrelekPawe68949 @Igra_Labs @KasanovaWallet Not sure it sully support EVM networks. Tested for support: Metamask, Rabby, Kastle, Kasperia, Kasware, Zelcore, Kurncy.

[Pavel Emdin @emdin]

@costgallo 🫡

[Pavel Emdin @emdin]

@2zM00N @Elichai2 For Kaspa I have my own agent trained on all the recent source code and research, so not a problem. It is more about legal and content work.

[Pavel Emdin @emdin]

We're on! Join, ask questions, hear alpha.

[Kaskad @AppKaskad]

https://t.co/iuPXaRSOf1

[Pavel Emdin @emdin]

@IzioDev @Aluminer_ Both. Public discussions reflect priorities, and priorities are shaped by context. Responding to real constraints as market situation is rational engineering. Every serious protocol does this.

[Pavel Emdin @emdin]

I've participated in several org transitions from 10 to 100 to 1000; what's happening at the EF is textbook. Ambitious, self-governing people leave when the org ossifies. They're intrapreneurs who need speed and freedom. $300B can't operate like a research lab anymore. The visionaries who built it aren't the operators who scale it. Eth becoming the JPMorgan of crypto sounds boring, but this is normal evolution.
Ossification creates space for upstarts.

[Pavel Emdin @emdin]

@IzioDev @Aluminer_ Hardly falsifiable. Internal motivations aren't observable from outside.

[Pavel Emdin @emdin]

@Aluminer_ EF and Ethereum ecosystem devs are super smart. Kaspa would do the same with $300B marcap.

[Pavel Emdin @emdin]

@5apere4ude My take is there is no fragmentation problem, there is UX problem. Solvers and agents will fix 95% of it. Rollup is UX, no right and wrong, diff demographic and use cases. You have hundreds of banks even if they use same SWIFT for a reason.

[Pavel Emdin @emdin]

Hey @5apere4ude, several things I'd push back on.

- Re "interim". Every infrastructure choice is interim until the market says otherwise. vProgs are interim until they ship and developers and users adopt them. Igra is interim until either based rollup architecture proves out at scale, or it doesn't. No founder can declare their solution permanent or interim ahead of the market.
- Re builder allocation -- I keep saying talent pools don't overlap. Kaspa core needs Rust systems engineers and cryptographers comfortable with UTXO and consensus protocols. Even with SDK abstractions, building on vProgs will require working knowledge of Rust and ZK proof systems. Igra needs Solidity developers comfortable with EVM and DeFi primitives. EVM developers don't migrate to UTXO scripting at the loss of Kaspa-native opportunities, and vice versa.
- Re business-vs-infra dichotomy. These are separate axes. Linux is open infrastructure. Red Hat is a focused commercial business on top of it. Igra is open architecturally (permissionless deployment with no gatekeeping) and focused commercially (EVM battle-tested execution and primitives for KAS and IGRA holders and developers who want PoW special guarantees). So yeah, infra is our business.

We won't get endorsement, and that's fine. The architectural conversation is still worth having.

[Sapere Aude @5apere4ude]

@hashdag @michaelsuttonil @KaspaSilver @emdin I would appreciate your thoughts on this matter.

[Pavel Emdin @emdin]

New version of https://t.co/XpFqKGNGLd:
- /stats now returns actual liquidity and network information
- New /bridges command monitors inflows and outflows across all Hyperlane routes
- Backup RPC failover via https://t.co/MC0cFTzGba by @asaefstroem
- Performance and stability fixes

[Pavel Emdin @emdin]

@otority111 @Seb28_7 @5apere4ude Here is the Discord: https://t.co/p4nzeCHCU9. Let know if all good.

[Pavel Emdin @emdin]

@otority111 @Seb28_7 @5apere4ude 30th of August. Please be in touch with your community -- was it 3SEARCH, Wolfie or Kaspacom?

[Pavel Emdin @emdin]

@KuniNhanDN We have our own monastery. :)

[Pavel Emdin @emdin]

Apply. CyberFund is based.

[cyber•Fund @cyberfund]

Introducing the Monastery for AI-native founders.

A single builder can now outperform a publicly traded company.

$2 million. 12 weeks. Do the impossible.

[Pavel Emdin @emdin]

@ronment3 Node was not synced. DAA transition happened while still syncing.

[Pavel Emdin @emdin]

My TN10 node reporting