🇻🇳🇺🇸𐤊aspy 𐤊aspa

Im a feisty female and #Kaspa maxi. Also ❤️ cats and my American Eskimo. $NACHO $KASPY - check my Bio for more info.

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

[Duꓘe @ThatKaspaDude]

A lesson to all those who say $KAS is a scam or dismiss it. @LukeDashjr @saylor @dotkrueger @adam3us @Excellion @VitalikButerin

Critics long argued that #Kaspa could never compete with ecosystem chains like $ETH due to its lack of smart contracts. That argument is now obsolete. With the Toccata hard fork, Kaspa introduces native Layer 1 programmability, covenant structures via SilverScript, and KRC-20 token standards. All built directly onto its ultra-fast, high-throughput base layer.

Kaspa doesn’t merely inherit Bitcoin’s ideological DNA. It delivers the mechanical speed and utility that Bitcoin’s rigid architecture was never designed to allow.

To those so quick to point out #Kaspa flaws. Let’s present #Bitcoin flaws objectively (like the 184-billion coin exploit) disarms Bitcoin maxi’s because it is a verifiable part of blockchain history.

Ethics of the launch are highlighted by the lack of VCs, pre-mines, and ICOs instantly separating Kaspa from 99% of "altcoin scams" in the eyes of hardcore crypto purists. $KAS and $BTC are both PoW with a fixed supply. Except Kaspa mining is more environmentally friendly. And for the record, there’s no #Satoshi wallet with 1 million coins out in the wild.

The Power of Visual Contrast - Utilizing a structured markdown table to contrast traditional linear blockchains with a BlockDAG allows you to immediately grasp the technical superiority of Kaspa's parallel processing.  How about watch BlockDAGs music in motion so you can truly understand the difference: https://t.co/W7F5Jk1tbv

Toccata proves Kaspa isn't just theory, it is a live, functioning, programmable network on the base layer. A combination of the best of $BTC, $ETH, $SOL and $SUI. And its fundamentals are more pure than grand daddy Bitcoin.

[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).

[Kaspa Kii @KaspaKii]

WarpCore on Kaspa TESTING UPDATE:
The only and most comprehensive full stack banking / financial rails on an L1 PoW.
We have completed the following tests:
286 transaction type tests to run using various scenarios:

1. ✅ CBDC Full Issuance Workflow
Token registration → minting → reserve attestation → Islamic instruments
2. ✅ Multilateral Netting Cycle
Multi-participant obligations → gross/net calculations → settlement
3. ✅ Credit Facility Lifecycle
Draw → repay → exceed limits → full lifecycle management
4. ✅ Nostro/Vostro Account Operations
Multi-currency positions → payments → funding → position reporting
5. ✅ Liquidity Pool Participation
Contributions → withdrawals → returns → multi-participant pooling
6. ✅ FX Forward Trading
Quote → forward rates → netting → PvP settlement → T+2
7. ✅ Multi-Currency Netting
Parallel netting across EUR, USD, GBP currencies
8. ✅ Islamic Finance Instruments
Murabaha (cost-plus) → Ijara (lease) → Musharaka (profit-share) → Sukuk (bonds)
9. ✅ Herstatt Risk Exposure
Settlement risk monitoring → high/medium/low categorization
10. ✅ Concurrent Transactions
Parallel settlement operations → fund conservation
11. ✅ T+2 Settlement Workflow
Trade date → T+1 confirmation → T+2 execution
12. ✅ Batch Payment Processing
100-item batch → success rate tracking
13. ✅ Treasury Operations
Multi-currency positions → USD equivalency → revaluation
14. ✅ Settlement Failure Recovery
Failure → retry logic → recovery verification
15. ✅ End-to-End Cross-Layer Settlement
CBDC mint → liquidity allocation → FX trading → netting → nostro settlement

Transaction Scenarios Covered
Payment Operations
✅ Single payments
✅ Batch payments (100+ items)
✅ Multi-currency payments
✅ Concurrent transactions
✅ Failed payments with recovery
Netting Operations
✅ Bilateral netting
✅ Multilateral netting (3+ parties)
✅ Multi-currency netting
✅ Gross/net calculations
✅ Netting settlement
Credit Operations
✅ Credit draw
✅ Credit repayment (partial, full)
✅ Exceeded limits
✅ Credit facility lifecycle
✅ Facility expiry
FX Operations
✅ FX quotes (bid/ask spreads)
✅ Forward rates
✅ NDF fixing
✅ PvP settlement
✅ Settlement risk (Herstatt)
✅ T+2 workflows
✅ Multi-currency trading
Liquidity Operations
✅ Pool contributions
✅ Pool withdrawals
✅ Share calculations
✅ Return distribution
✅ Multi-participant pooling
CBDC Operations
✅ Token issuance
✅ Supply minting
✅ Supply burning
✅ Reserve attestation
✅ Murabaha financing
✅ Ijara leasing
✅ Musharaka partnerships
✅ Sukuk instruments
Account Operations
✅ Nostro account management
✅ Vostro account tracking
✅ Multi-currency positions
✅ Balance updates
✅ Position reporting
Risk Operations
✅ Herstatt settlement risk
✅ Risk categorization
✅ Exposure monitoring
✅ Risk recovery
Cross-Layer Operations
✅ CBDC → Liquidity flow
✅ Liquidity → FX flow
✅ FX → Settlement flow
✅ End-to-end workflows

All 286 tests executed sequentially
Zero test failures
100% pass rate

#kaspa #warpcore #xrp #kii #poweredbyKaspa

[Duꓘe @ThatKaspaDude]

Every #Ethereum builder should be migrating to #Kaspa. Now the great $ETH to $KAS migration begins, as it’s easier now than ever before.

[Maksim Biriukov @Max143672]

DONE.

Just completed an initial working implementation of a based zk covenant/rollup with KAS canonical bridging (over TN12 capabilities).

This work is part of the covenants++ hardfork milestone roadmap(https://t.co/r9ehZNZu1Y)

The work is scoped as PoC however all significant challenges related to canonical bridging have been thoroughly addressed and the implementation is already mature. The vm itself is a simplified account model supporting only 3 actions: entry/transfer/exit.

Notable changes and improvements over the described research spec:
- Uses the new covenant ids scheme for unforgeability
- Uses an additional covenant script for succinct claim-based outbox/exit ops
- Implements a clever shortcut between entry and exit ops without going through the state transition singleton UTXO for streamlined UTXO management

Branch: https://t.co/u7zJJtkI1e
Demo: https://t.co/LlHDp9A7pM
Book: https://t.co/f1lnfztl25

[Yonatan Sompolinsky @hashdag]

Kaspa is real-time bitcoin, solving scalability is great but not the core value prop.

Real-time bitcoin means achieving in a few seconds the same security guarantees that nakamoto consensus / bitcoin achieves after an hour; decentralizing each consensus round rather than chain quality achieved through a coarse aggregate of rounds.

A clean definition anchor for real-time decentralization (RTD): The ability to sample the honest majority in real-time.

(Note that even fast leaderless VRF-based proof-of-stake cant sample honestly bc the selected nodes get to choose the content of their blocks after they've been selected; pos=select then write, pow=write then select)

--

RTD affects: txn confirmation, censorship resistance, secure oracle finality, MEV resistance.

Eg censorship resistance, bitcoin is the most censorship resistant chain, but if 60% of the miners are censoring you (point in reference: OFAC abiding tornado censoring eth miners), your txn will pend for 30-40 minutes. For shady business payments that's not prohibitive, but for a real economy, for an asset aspiring to be at least a king of collateral even if not an MoE, this is unacceptable, esp under economic stress.

Beyond censorship, all things finance benefit tremendously from pow density, from sampling the majority in real-time in a secure and honest manner.

I wont get into MEV resistance now, but having a "conscious" stream of oracle attestations (not price oracles) finalized in real-time qualitatively upgrades the ability to encode informed risk, collateral, liquidity management, which is the lifeblood of defi.

In context of conf times, increasing from 1 to 10bps saturates the latency optimization. But for pow density we need dozens of blocks per second, with the endgame of 100 bps: Under 10bps a 37% attacker can fake the majority signal with probability 12%. With 100bps this drops to 0.3%. Today Kaspa can't accelerate to >10bps w/o harming conf times, but DAGKNIGHT will be implemented hopefully by Q3 at least on testnet, by which we will push for 25-40bps.

The cherry on top: RTD also implies netsplit resistance, as per the partial synchrony framework.
WWIII cyberwar resistance. Hypothetically speaking ofc.

(elaborated- https://t.co/o8vKa7gBwm)

[Duꓘe @ThatKaspaDude]

What OG #Kaspa meme will withstand the test of time?

[🇻🇳🇺🇸𐤊aspy 𐤊aspa @KaspyKaspa]

@ThatKaspaDude Nacho and Kaspy

[Duꓘe @ThatKaspaDude]

Most Kaspa maxis I know were Bitcoin maxis beforehand. Some were PoS believers, others precious metals stackers and even others recovering #crypto casino meme addicts. I’m genuinely curious: which of you still hold $BTC, or did you swap all your #Bitcoin for #Kaspa?

If you kept some Bitcoin, why? If you went all-in on $KAS, what drove that decision?

Thank you in advance for your insights my fellow Kaspians.

[🇻🇳🇺🇸𐤊aspy 𐤊aspa @KaspyKaspa]

@ThatKaspaDude I have around 40ish% Bitcoin and the rest is in the Kaspa ecosystem, mostly Kaspa. I’ve kept Bitcoin to diversify and consider it a safer investment cause it’s stood the test of time.

[Duꓘe @ThatKaspaDude]

I’ve DCA’d $KAS regularly for over 2 years now and my conviction has grown stronger everyday. #Kaspa is the most superior #crypto/sound money on earth. #Bitcoin is second best.

#PoW > #PoS
#fairlaunch
#blockDAG > #blockchain

@saylor @elonmusk @cz_binance @NickSzabo4

[Vijay 𐤊ailash, CFA, CFP® @realvijayk]

@hashdag @binance Your move @cz_binance @binance

In the meantime, this your chance @brian_armstrong @coinbase to take MASSIVE market share from your competitors.

List #Kaspa. Notice the engagement on this post. You're leaving SOOOO much money on the table.

[Yonatan Sompolinsky @hashdag]

@binance,

Thanks for including me in the top 100 blockchain people list, appreciate the signal!

I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out.

Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed.

There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <<Binance should hold a privilege policy for the latter.>> A TBTF CEX should know better and play a different game with hardcore crypto projects.

When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement.

You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog?

Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point.

@cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity.

Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto.

We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes.

Please fix this.

Thanks again,
hashdag

cc @michaelsuttonil

Exhibit A: Binance Innovation Zone
Exhibit B: 10 bps Nakamoto Consensus

[John 𐤊rypt ¶Ƥ @John_Cryypt]

Announcement to the entire #Kaspa #Kas @kaspaunchained community !

PLEASE VOTE for @hashdag and @michaelsuttonil using these two links 🔗

Yonatan : https://t.co/Ats0qiVJUg

Michael : https://t.co/CQ8tMTG8yg

You’ll need to create a @binance account if you don’t already have one!

This is really important with the strength of our community, we can genuinely push them to the top spot in each category, and it’s totally deserved!

You can vote once per day , so don’t hesitate to cast your two daily votes through these links 🔗

[🇻🇳🇺🇸𐤊aspy 𐤊aspa @KaspyKaspa]

@KaspaQueeen @KaspaExperience Fun times!

[🇻🇳🇺🇸𐤊aspy 𐤊aspa @KaspyKaspa]

@ThatKaspaDude @hashdag @binance Voted

[Duꓘe @ThatKaspaDude]

A reminder to the #kaspa community to officially place your vote for @hashdag.

Yonatan and $KAS deserve to be #1 in the @binance top 100.

[Duꓘe @ThatKaspaDude]

For all my fellow Kaspians that appreciates the scripture; it’s always a nice reminder what was inscribed on Kaspa’s Genesis block.

Kaspa has the verse Ezra 7:18 (in Hebrew) inscribed on its genesis block.

“Whatever seems good to you and your brothers to do with the rest of the silver and gold, you may do, according to the will of your God.”

#kaspa $KAS #bible #digitalsilver #MOE $BTC #bitcoin #digitalgold #SOV

[🇻🇳🇺🇸𐤊aspy 𐤊aspa @KaspyKaspa]

@ThatKaspaDude @thereallrach Cool story. $KAS ♾️.