Henry Ramirez 𐤊 🇩🇴

Software Developer. God is in control of my life. He will not abandon me. His right hand will sustain me throughout my days.

[BaN𐤊ℚuOτE @BankQuote]

AI can now operate on Kaspa as an economic actor, not as an on-chain brain. The model does not need to live inside consensus. That would be wasteful. The intelligence runs at the edge, Kaspa settles the consequences.

Agents can hold and spend KAS, manage covenant-controlled wallets, enter enforceable contracts, post and fulfill bounties, submit lane-based operations, pay for compute, verify work, and settle proofs back to L1. The computation happens off-chain, but the value transfer, ordering, state enforcement, and proof settlement anchor into proof-of-work.

That is the real unlock. Kaspa gives autonomous software a monetary substrate that does not require banks, payment processors, stablecoin issuers, or centralized rails. AI does the work elsewhere. Kaspa makes the work economically final.

[Kaspa Silver @KaspaSilver]

If Kaspa is gonna be adopted its not going to be free to use BUT with $KAS advancing to 100bps this gives users the ability to mine their own transactions with a reasonable wait time at whatever fee rate they choose!

I really don't think people comprehend this advancement because everyone is so used to the traditional slow block times/high fee is the only way to be included life.

$KAS is built different. Study it.

[IzioDev @IzioDev]

Did you miss Kaspa Under the Hood: Setting the Stage for vProgs by @hus_qy?

Watch the recording.

[IzioDev @IzioDev]

https://t.co/qVT48JwQty

[Henry Ramirez 𐤊 🇩🇴 @henryhre]

@davidgokhshtein kaspa:native

[₿RT 𐤊 🐈📈 @brt2412]

@InvestorJordan Ethereum exists today because of the GHOST protocol, which is a creation of the $KAS founder dating back to 2012. https://t.co/EtuTgv1wAm

[Travladd 𐤊 @OfficialTravlad]

$SUI back to back down.
$SOL down multiple times in recent history.
$KAS down 0 times, POW record set and big developments to come.

Food for thought.

[Henry Ramirez 𐤊 🇩🇴 @henryhre]

@LauraenSociedad Su’santisimo! Que abuso!

[Michael Sutton @michaelsuttonil]

Here we go again: rehearsing a major hardfork on testnet 10, this time crescendoing into Toccata

Activation is scheduled for tomorrow May 18, 16:00 UTC.

Existing TN10 miners/operators should upgrade now. In a few hours upgraded p2p nodes will stop connecting to non-upgraded nodes as we enter the 24h pre-activation window.

Let’s make the mainnet activation boring by making the TN10 rehearsal as mainnet-real-world as possible

[Henry Ramirez 𐤊 🇩🇴 @henryhre]

@davidgokhshtein $KAS

[BaN𐤊ℚuOτE @BankQuote]

"The early Internet did not win because it was a prettier network. It won because it introduced a neutral protocol layer that let independent systems interoperate without asking a central operator for permission. That was the breakthrough. Open architecture networking turned fragmented machines and networks into a shared communications substrate. TCP/IP was not just “faster telecom.” It was a new base layer for information transfer.

That is the right frame for Kaspa.

Kaspa is not interesting because it is “another fast chain.” That misses the point. The deeper similarity is architectural. It is trying to do for value transfer what the Internet did for information transfer: create an open, high-speed, permissionless protocol layer that others can build on top of, without rebuilding trust every time.

That is why the BlockDAG matters. Instead of forcing economic activity through a single serialized lane, Kaspa’s GHOSTDAG orders parallel block creation in consensus. The result is not just more speed. It is a different kind of base-layer design, one built for open settlement under real network conditions.

And this is where the comparison gets stronger.

The Internet did not stop at packet delivery. Higher layers emerged on top of the common base and unlocked entirely new classes of applications. Kaspa’s research direction points toward a similar expansion. Verifiable programs push computation offchain, then prove correctness back to the base layer. That preserves speed without turning the foundation into bloated global state.

Same pattern. Keep the base layer lean. Keep it open. Let the protocol scale the civilization built on top of it."

[Yonatan Sompolinsky @hashdag]

@Grayscale @realvijayk arigato gozaimasu!
if Kaspa army showed up here, think how they'll show up when you provide a KAS digital asset..
by mid june Kaspa OP_CAT++ Bitcoin. worth the attention _/\_

[Henry Ramirez 𐤊 🇩🇴 @henryhre]

@Grayscale $KAS

[₿RT 𐤊 🐈📈 @brt2412]

The chairman of @KaspaKii , @pvson, is the founder and president of an international group of 120+ energy infrastructure and financial companies with a combined valuation of more than $5T based on my best estimates.
Five...trillion…dollars. And that’s probably on the low end of things…and they are going with #Kaspa.

This man is telling you that they specifically chose $KAS to “position Kaspa as the ultimate base layer for various applications…for industrial and enterprise applications in finance, supply chain, energy, and the public sector, while promoting sustainable and ethical development.”

They are now telling you that only $KAS can do what is needed to build their infrastructure for energy trading and other applications that I don’t even understand lol. They told you that Bitcoin and Ethereum cannot do what they need them to do to accomplish their tasks.

Anyone telling you AI agents are going to use $BTC is lying to your face. Anyone telling you Bitcoin’s slow speed is a feature is coping and doesn’t understand anything about the world.

Please read the attached article posted by KII to see the results of all the stress testing they did on Kaspa’s testnet-12.

[Paul van Son @pvson]

That is exactly the reason why @KaspaKii must not spend much time on marketing the new global sequencing network and applications based on $KAS. There are enough smart people around that are finding out and tell others! @KasMaporg @DiiDesertEnergy

[₿RT 𐤊 🐈📈 @brt2412]

Kaspa markets itself. Use it one time and you’ll never want to use anything else ever again. If you’re a young investor who grew up in the age of instant gratification and you don’t hold any $KAS, ask yourself why you aren’t interested a new decentralized currency that offers final settlement in the time that the Face ID scan UI completes

[Zealous Swap @ZealousSwap]

USDC pools Loading...

[Igra Labs @Igra_Labs]

Loading…

[Hans Moog @hus_qy]

Okay, it's time for a little update:

I just finished the work on the zero knowledge part of the vprogs framework, which introduces the ability to prove arbitrary computation.

It consists of the following 8 PRs that gradually introduce the necessary features:

1. ZK-framework preparations (https://t.co/H0X9278oWK):

This PR cleans up the scheduler and storage layers, extends the build tooling with workspace-wide dependency checking, adds the ability to publish artifacts for transactions and batches (which will later hold the proofs), renames some core types for clarity, and introduces lifecycle events on the Processor trait that allow a VM to hook into key scheduler events like batch creation, commit, shutdown, and rollback.

2. Core Codec (https://t.co/ZbFEsNd7zF):

This PR introduces a lightweight encoding library for ZK wire formats.

In a zkVM guest, every byte operation contributes to the proof cost, so the codec is designed to reinterpret data in-place rather than copying it.

It includes zero-copy binary decoding (Reader, Bits) and sorted-unique encoding for deterministic key ordering. It is built for no_std so it runs inside zkVM guests.

3. Core SMT (https://t.co/wCcRTCXg8x):

To prove state transitions, we need cryptographic state commitments. This PR adds a versioned Sparse Merkle Tree that produces a single root hash representing the entire state.

It includes all state-of-the-art optimizations: shortcut leaves at higher tree levels to avoid full-depth paths for sparse regions, multi-proof compression that shares sibling hashes across multiple keys, and compact topology bit-packing to minimize proof size.

It integrates into the existing storage and scheduler layers so that every batch commit updates the authenticated state root, while rollback and pruning maintain tree consistency.

4. ZK ABI (https://t.co/1THUvCK1Xq):

Defines the wire format for communication between the host and zkVM guest programs, establishing a universal language for proof composition. It specifies how inputs, outputs, and journals are structured for two levels of proving: the transaction processor, which proves individual transaction execution against a set of resources, and the batch processor, which aggregates transaction proofs and proves the resulting state root transition.

Because the ABI is backend-agnostic and no_std compatible, any zkVM backend can directly use it (non-Rust zkVMs would need to reimplement the ABI in their language).

5. ZK Transaction Prover (https://t.co/TtvoYZaazz):

Introduces the transaction proving worker, which receives serialized execution contexts via the ABI wire format and submits them to a backend-specific prover on a dedicated thread. The Backend trait abstracts the actual proof generation, so different zkVM backends can be swapped without changing the pipeline.

6. ZK Batch Prover (https://t.co/WPRd1UmvGW):

Introduces the batch proving worker, which collects the individual transaction proof artifacts, pairs them with an SMT proof covering the batch's resources, and submits the combined input to a backend-specific batch prover. The result is a single proof attesting to the entire batch's state root transition.

Like the transaction prover, the Backend trait abstracts proof generation so different zkVM backends can be swapped without changing the pipeline.

7. ZK VM (https://t.co/3xMF17DKUq):

Wires everything together by implementing the scheduler's Processor trait with ZK proving support. The VM hooks into the lifecycle events introduced in PR 1 to feed executed transactions into the transaction prover and batches into the batch prover.

Proving is optional and configurable - it can be disabled entirely, run at the transaction level only, or run the full batch proving pipeline.

8. ZK Backend RISC0 (https://t.co/HJ0Payxfl0):

Provides the first concrete zkVM backend using risc0. It implements the transaction and batch Backend traits, includes two pre-compiled guest programs (one for transaction processing, one for batch aggregation), and ships with an integration test suite that verifies the full pipeline end-to-end - from transaction execution through batch proof generation to state root verification.

TL;DR:

While the early version of the framework focused on maximizing the parallelizability of execution, this feature focuses on extending this capability to maximizing the parallelizability of proof production.

If you're a builder: this is the first version of the framework that lets you write guest programs with a Solana-like API (resources, instructions, program contexts) and have them proven in a zkVM.

The current milestone uses a single hardcoded guest program - composability across multiple programs and bridging assets in and out of the L1 are part of the upcoming milestones, but if you're eager to start tinkering, the execution and proving pipeline is fully functional and provides a minimal environment to build and test guest logic today.

Once we add user-deployed guests, they will move one logical layer down: the current transaction processor will become a hardcoded-circuit that handles invocation and access delegation to user programs, similar to how SUI handles programmable transactions (including linear type safety at the program boundary).

In practice, this means guest programs will be invoked with a very similar API but scoped to a subset of resources, so the basic programming model won't change. Note that guests currently handle their own access authentication (e.g. signature checks) - the framework will eventually manage this automatically.

If you want to contribute, two areas where community involvement would be especially impactful:

- An Anchor-like DSL for writing guest programs -- the ABI is stable enough to build on, and a good developer experience layer would make this accessible to a much wider audience.
- A second zkVM backend (e.g. SP1) - the Backend traits are designed for this, and a second implementation would prove out the abstraction.

One thing I find particularly interesting in the context of PoW: the block hash provides an unpredictable, unbiasable random input that is revealed after transaction sequencing.

This gives guest programs native access to on-chain randomness without oracles or additional infrastructure - something traditionally hard to achieve in smart contract platforms.

PS: I am also planning to start with the promised regular hangouts but since I will visit my family over easter and want to get a better understanding of the open questions next week (it's good to have some problems to wrestle during that slower time 😅), I decided to start with that once I am back (12th of April).

Generally speaking, is there a day that people would prefer for these hangouts? I guess monday would be bad as there is already another community event (write your preferences in the comments if you have a strong opinion).

[BSCN @BSCNews]

🚨BIG: KASPA HITS 1.3 BILLION CUMULATIVE TRANSACTIONS

@kaspaunchained transactions have surged in recent weeks, recently breaking past the 1.3 billion transaction milestone.

The L1's native $KAS coin has a market cap of more than $940 million at time of writing.