Pavel 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.

@emdin @Aluminer_ What do you mean by internal motivations? Is it as personally interiorized but generalized or as in a closed group of people? For the later, main discussions happen publicly, there are small focus group here and there for practical reasons, always reported publicly afaik

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.

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

@emdin @Aluminer_ I doubt it, because I've never seen the core vision, decisions and development cycles being affected by market conditions in any ways.

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

@emdin Thank god we have smart people as yourself to build on kaspa

@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.

@emdin Thank you for your detailed answer. Very interesting read. What is your opinion on the risk of fragmentation and the problems that come with it?

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.

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

@otority111 @Seb28_7 @5apere4ude Here is the Discord: discord.gg/tA5JKkK9UM. Let know if all good.

@emdin @Seb28_7 @5apere4ude 3search

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

@emdin @Seb28_7 @5apere4ude Question; I took part in the igra presale last year. When will those tokens be distributed?

@KuniNhanDN We have our own monastery. :)

@emdin Igra?

Apply. CyberFund is based.

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

@emdin Excuse me—Toccata activates simultaneously for everyone. Therefore, the data displayed at the minute level should be consistent across the board, correct? In the screenshots provided, the timestamp is at the 31st minute, whereas yours shows the 11th minute.

My TN10 node reporting

@coderofstuff_ Not yet, we need to patch several things on our side first (major things being lane support and adding new consensus validation to ATAN).

@emdin Igra L2 all good on it as well?

@_DrLiberty @LyceumProtocol @Igra_Labs Let's do it sir!

@emdin Love to hear it! I'll be reaching out soon to get @LyceumProtocol up and running on @Igra_Labs

Igra is permissionless and open for anyone. if you have a project, DM and you will get exactly the same treatment as everybody else.

Great initiative for the whole EVM ecosystem. Blind signing is a horrible experience that we have taken for granted for years.

@Oliver_665 @Igra_Labs Welp. Hyperliquid: 30 validators. MegaETH: 1 sequencer. Base: 1 sequencer. Igra: 14 attesters on top of thousands of L1 PoW miners. Igra's execution is protected by L1 consensus, attesting is an additional layer on top, enabling light nodes in the future.

@Igra_Labs 14 active attesters the entire network's execution layer is being validated by 14 people. How is that decentralized?

On-chain assets, to be precise. TVL depends on methodology. Yet the organic trend is there, and more protocols are coming.

Trust me I can type "memorize this" all day.

@KaspaSilver @Themooseisloos5 Confirming. To rollback based rollup you need to roll back its sequencer.

@Themooseisloos5 "and they want a rollback" from my limited understanding Igra cannot do rollbacks ever. This design was on purpose. @emdin confirm?

"User-friendly and works now usually beats theoretical superiority until the superior thing actually works better." Took this quote from grok when trying to gather all my thoughts together on the future path for kaspa:native . I am going to just brain dump to see if someone can find what I am missing or just agree with my take on things. Lost focus on building one thing like vprogs was inevitable to happen. There is no way to stop the fragmentation of devs, funding, and efforts going all over. This is because the nature of this market is free and users want to operate for profit. No one wants to lose. All in focus on cores desires for smart contract like programability is high risk high reward when Kaspa does not have forever to just be on the sideline trying to attract users with "hey look whats coming." What is a bit unfortunate is seeing core shift away from trying to market Kaspa as being money to solely view Kaspa as this MoE powerhouse to allow you to do many things. I get the shift but the problem is the "many things" are simply not many. I could be wrong for this feeling but this is simply what I am getting. Kaspa has a narrative crisis that is for sure but I think the biggest mistake is to try and leave the money narrative all together. I simply point this out cause I fear I am seeing signs of abandonment of this all together. Giving humanity a better Money IS the biggest market. This is the biggest way I can onboard any noob into crypto with Kaspa. The % of people not in crypto is greater than the % of people in it and it seems efforts are being made to try and steal users from everywhere else that are already here and hope it happens. I think Kaspa main efforts should be focused on no coiners. This means developing to give these users a way to live on a Kaspa standard. This also means making apps to easily utilize Kaspa and especially bring native stablecoins to it. Kaspa for ultimate storage, stabecoins for living day to day while still living on the Kaspa network at all times. Hopefully Toccata ships and we get this moving along quickly. When it comes to L2s and bringing basically all ETH offers to a wonderful base layer like Kaspa I repeat what I stated above. User-friendly and works now usually beats theoretical superiority until the superior thing actually works better. Kaspa is money and its the first time money will be programmable to scale at internet speeds while keeping true to Bitcoin level properties of security and decentralization. This keeps users self-sovereign and truly rids the reliance of the middle man.