Roibe

[Benjamin Cowen @benjamincowen]

Crypto exchanges could make the industry seem more legitimate by not constantly listing dogshit memecoins on their platform to take advantage of short-term retail interest.

If we don’t respect ourselves, how can we expect others to respect us?

[Igra Labs @Igra_Labs]

It's official: Igra Association signs with Hyperlane alongside core Kaspa ecosystem partners: @AppKaskad @ZealousSwap @KaspaCom @Kaspa_KAT.
USDC.e, USDT.e, and wETH.e coming to Igra at launch via Hyperlane bridge.
Community poll to follow and you’ll help to decide what gets bridged next.

[Kaspa Bro 𐤊 @Kaspanero]

Uhm.. Kaspa? It costs you 0.00001 to transfer whatever amount. And it takes 1 sec for the confirmation and arrival.
Tuesday, Sunday? Always.

[Michael Sutton @michaelsuttonil]

proof-of-work DAG gets this whole new meaning

[Michael Sutton @michaelsuttonil]

@manyfest_ Nice summary. Tbh, the most exciting recent development is actually still in stealth mode. Soon^tm

[Roibe @Robullish]

@Whale_Guru Kaspa $kas

[Igra Labs @Igra_Labs]

Galleon closed mainnet on Node V2 is ready for community node operators!

Setup guide: https://t.co/MU0gePpNW7

Note: configured for Galleon testnet. Mainnet configuration coming soon.

What this means: decentralization and censorship resistance from day one. Igra state can be read, written, and verified on community hardware.

For questions, comments and support please join our Discord: https://t.co/Niz6k1p4Ix

For the technically curious, here's what's under the hood:

1. V2 Architecture
New Viaduct and Adapter components for L1-L2 bridging. Viaduct manages ATAN-to-Consensus data handover with async streaming. Adapter connects Kaspa (L1) to EVM execution layer (L2) via Engine API. Includes warm/cold start positioning and fallback mechanisms.

2. Engine Stability & Reorg Handling
Critical fixes for Fork Choice Updated (FCU) unwind operations, deep reorg safety, and disk consistency. Plain state rollback, synchronous block removal, crash prevention.

3. ATAN Synchronization
Complete ATAN system for blockchain state sync. Auto-import rewrite, importer service, finality period validation, consensus sync checks.

4. Transaction Pool Improvements
FIFO ordering, synchronous pool clearing after FCU success, discard reorged transactions. Ensures reliability during chain reorganizations.

5. gRPC Protocol MigrationComplete migration from WebSocket/borsh to gRPC/protobuf for wallet communication.

---

Test it, break it, let us know.

[Roibe @Robullish]

@cryptocom Kaspa $kas

[Kaspador @kaspador_]

works beautifully

[Lucky @LLuciano_BTC]

Market rotation will happen, and $KAS will be the front-runner. ✅

NFA.

[Dr Martin Hiesboeck @MHiesboeck]

Anybody have a hi res of this ?

[Hans Moog @hus_qy]

You want to reach agreement about your evolution - don't halt the world - choose from competing branches!

That's what Kaspa is about! Kaspa is the only DLT that mimics the very nature of reality itself.

[Bitmo｜Kaspa Pay®︎ (DNET®︎) @bitmo_kaspa]

https://t.co/WxhaTxLVZO

[Hans Moog @hus_qy]

Remember how I said yesterday that there are still a lot of rough edges as we don't even prune or clean up after ourselves? Today we do! 😅

We just merged two big PR's that enable eviction (https://t.co/UwwzHmi2Mv) and pruning (https://t.co/Hgxx6AkGAK) in the vprogs framework.

[Michael Sutton @michaelsuttonil]

A few words on the kaspanet/vprogs code repository.

Consider this as two efforts digging a mountain from both directions and seeking to meet.

Hans @hus_qy (and others will join) is building a based computation runtime, i.e., a runtime that is fed by a sequencer with transactions and executes them over a vm (or several vms) with maximum concurrency.

The covenants++ taskforce is digging from the L1 side, building the covenant infrastructure and zk opcodes that will allow this runtime to settle and bridge from/to L1.

We aim to reach each other first through a narrow tunnel, and only then widen the pathway together.

That’s the covenants++ goal: create based zk covenants on one side and a minimal standalone app-level runtime on the other, then have them connect and link with production-ready quality.

Then we widen the tunnel together, integrating increased composability while still targeting maximum sovereignty (with the vprogs yellowpaper guiding the way). This pathway can also be gradual (see the gist I shared a few weeks ago).

The point is building the basic elements in production-ready quality, having them support massive based computational apps, and then continuing the journey

[Roibe @Robullish]

@IntroMax17 Welcome 🤗

[Kaspa Daily @DailyKaspa]

vProgs framework becomes public

[𝙏𝙧𝙪𝙚𝙆𝙖𝙨𝙥𝙖𝘽𝙚𝙡𝙞𝙚𝙫𝙚𝙧 𐤊 @TrueKaspaBeliev]

Hans Moog (@hus_qy) just dropped the biggest tech bombshell since the DAG launch.

The code for Vprogs (Kaspa's Smart Contract framework) has been open-sourced, and it redefines everything we thought we knew about decentralized computing.

​👶 "The Perfect Baby"
Hans said it best:
Kaspa arrived "late" to the DLT party, and that is our biggest advantage.

Instead of repeating the mistakes of Solana or Sui, the devs could skip the "archaeology," take only the most powerful ideas from every existing project, and combine them into one perfect solution.

​🚀 Breaking the Speed Limit (Post-Amdahl)
Until today, parallel processing had a glass ceiling ("Amdahl's Law").

Kaspa's new engine shatters this ceiling.

It enables true parallel execution, not just within a block, but inter-block.

The result:
Linear Scalability.

Add more hardware, get more speed.

No limits.

​🛠️ How does it work?
No Traffic Lights.

The system was built from scratch for extreme efficiency:
❌ No Mutexes/Locks:
No "jams" in the code forcing threads to wait.

❌ No Speculative Execution: No wasted CPU cycles on guessing.

✅ Genius Simplicity:
The system is orders of magnitude less complex than anything existing today.

​⚠️ Keep in mind:
This is an initial release for developers (WIP).

There are still "rough edges" to smooth out. But the message is clear:
The theory has become code.

The engine exists.

​The world doesn't need another slow "World Computer."

It needs Kaspa.

​#Kaspa #KAS #Vprogs #SmartContracts #L1 #CryptoTech #HansMoog

[Hans Moog @hus_qy]

Have you ever looked at different DLT projects and realized they're all converging on the same ideas, just with different terminology?

And have you ever wondered what would happen if you forced all DLT projects to have a baby, where each could only contribute their most powerful ideas?

You'd be surprised by the overlap - how non-unique many projects actually are - and how few genuinely good ideas exist. Often they sound almost trivial once you strip away the noise.

The problem is that fundamental breakthroughs get buried under layers of unnecessary complexity - the inevitable result of gradually expanding a protocol's capabilities as research progresses.

With Kaspa, we have the benefit of being late. In fact, we're so late that we arrive at the party when almost all the research has already been done. We can skip the archaeology and just make that perfect baby - making the final breakthrough on our quest for perfection.

Today we are open-sourcing our vprogs framework: https://t.co/eCvvSAyt1n

A post-Amdahl execution engine that enables inter-block parallelism and linear scaling beyond boundaries traditionally assumed to be possible in the context of DLT execution.

By deeply understanding causal actors and domains, we eliminate almost all logic and instead encode behavior in dependencies and relational properties of a generic type framework.

This allows us to transparently map hardware resources to workload - achieving linear scalability.

The design principles:

- No fsync / WAL flush boundaries
- No mutexes / locks
- Versioned append-only data with efficient rollbacks
- Maximal parallelism - even inter-block - breaking through Amdahl's law
- No wasted CPU cycles on speculative execution

This repo is still heavily WIP with rough edges (we don't even prune state yet). But the goal of this repository is to create a concrete instantiation of all existing research directions condensed into a singular, maximally performant type framework that gets away with almost no logic.

There's still room for improvements (zero-copy deserialization, NUMA affinity, etc.) but we're converging toward a system that can eventually no longer be optimized or simplified.

The holy grail of blockchain execution isn't more complex but orders of magnitude less complex than anything that exists today!

I am really looking forward to tell you more about this in the coming weeks (I just ordered a new microphone pre-amp to be able to host regular hangouts where we can discuss and explain how everything works under the hood - let's pray for a fast delivery 😅).

[Michael Sutton @michaelsuttonil]

kaspanet/vprogs

It’s about time

(still a long way to go, but this is how meaningful journeys begin)