We hear the Kaspa community and understand why dynamic address support is important. kaspa:native is technically different from Bitcoin-like UTXO networks such as BTC, LTC, DOGE, etc. Its architecture requires a separate implementation approach, so this feature cannot be added in the same way as for other UTXO-based networks.
That’s why dynamic address support is being rolled out step by step. We started with networks where the implementation of this feature is the same, while Kaspa requires additional dedicated work and validation before it can be delivered properly.
Kaspa is a priority and the team is actively working through the technical scope right now. We’re not putting a firm date on it yet because we want to deliver it right, but the Kaspa community hasn’t been forgotten and we’ll come back with concrete timing once it’s confirmed.
Forget everything you thought you knew about UTXO limitations. Kaspa is proving you can run complex applications and state machines entirely within local, transient block data. Check out the full breakdown video! 🧵🔥
@michaelsuttonil
Kaspa Q&A Kaka_001:
What are KASPA’s core breakthroughs? $KAS
After reading the project’s academic paper, KIP documents, and codebase, I found that what KASPA’s founder @hashdag and core team @michaelsuttonil@OriNewman@IzioDev@Max143672@coderofstuff_@FreshAir08@hus_qy have done is simply a great revolution and breakthrough for the entire blockchain industry.(There are many more contributors who weren't mentioned individually.)
KASPA’s core innovation lies in using BlockDAG combined with GHOSTDAG to upgrade Proof-of-Work from a linear, low-throughput ledger into a high-frequency parallel ordering network. Building on this foundation, it advances toward a high-speed, programmable PoW settlement layer through Rusty Kaspa, the 10 BPS mainnet, UTXO state commitments, covenants, ZK integration, Toccata, and the future DAG KNIGHT and VPROGS roadmaps.
The mainnet has now completed the Crescendo hard fork and maintains a stable block production rate of 10 BPS (10 blocks per second). In full DAG mode, the engineering target throughput is approximately 3,000 TPS, a level that is already achievable in live mainnet operation.
Consensus Structure Innovation
Kaspa replaces the traditional linear single-chain structure with a BlockDAG. Each new block can reference multiple parent blocks simultaneously. As a result, blocks produced in parallel by honest miners are no longer discarded as orphans. Instead, they are incorporated into the DAG and participate in subsequent ordering and consensus, significantly reducing wasted computational work.
Core Protocol Breakthrough
GHOSTDAG extends Nakamoto consensus from a linear chain to a DAG environment. Through blue/red block classification, k-cluster rules, and a greedy algorithm, it achieves deterministic total ordering of parallel blocks while preserving a security threshold comparable to Bitcoin even under high block production rates.
Throughput and Security Decoupling
The mainnet currently operates stably at 10 BPS. Combined with the parallel nature of BlockDAG, this delivers an engineering-measured throughput of approximately 3,000 TPS. The traditional PoW limitation—“the faster the block rate, the more orphans, and the weaker the security”—has been broken. Security no longer depends on artificially suppressing block speed.
Rapid Confirmation Capability
Thanks to high-frequency block production and GHOSTDAG’s ordering mechanism, transactions receive their first confirmation within seconds. Subsequent blue blocks then rapidly strengthen finality. This makes the network particularly suitable for payments, settlements, L2 data anchoring, and other high-frequency ordering use cases.
Node Implementation Upgrade
Rusty Kaspa is a complete rewrite of the original Go full node in Rust. It significantly improves concurrency, memory safety, and DAG graph processing efficiency, forming the technical foundation that enables stable 10 BPS operation on mainnet.
State Bloat Governance
Through proposals such as KIP-9 and KIP-13, Kaspa implements systematic management of long-term state growth. This effectively reduces storage and synchronization pressure on full nodes and helps preserve the network’s decentralized node operability.
Pruning Protocol and Scalability
Kaspa’s pruning protocol reduces long-term storage requirements by allowing old, deeply confirmed BlockDAG data to be safely discarded while preserving what is needed to verify the current ledger state and continue consensus. This improves synchronization efficiency and helps keep full-node operation practical under high block production rates.
Scripting and Fee Optimization
Transaction script fees are now calculated based on the actual execution path’s sigops. Users only pay for resources they truly consume, which substantially lowers invalid mass and reduces transaction costs for ordinary users.
Covenants and Script Expansion
KIP-10 introduces covenants that grant UTXO introspection capabilities, enabling more complex conditional fund flows, additive addresses, and micropayment logic. The upcoming Toccata upgrade, scheduled for activation around June 30, 2026, will further increase script computational capacity, providing greater headroom for complex scripts and L1 programming.
ZK Integration Roadmap
The mainnet plans to integrate Groth16/BN254 and RISC Zero STARK precompiles to support on-chain zero-knowledge proof verification. This will natively enable privacy transactions, Rollup data availability, and verifiable computation. These features are also scheduled to go live around June 30, 2026, alongside the broader upgrade.
Future Consensus Upgrade: DAG KNIGHT
DAG KNIGHT is Kaspa’s planned next-generation consensus protocol and the successor to GHOSTDAG. The full research paper has already been published. It is designed to deliver major improvements, including significantly faster confirmation times, greater tolerance for network latency and propagation delays, more efficient block ordering under extreme parallelism, and stronger security and liveness guarantees. The protocol is currently under active development, with implementation work ongoing. It is expected to be deployed on mainnet through a future upgrade.
Future Verifible Computation: VPROGS
VPROGS (Verifiable Programs) is another future capability currently in active development based on its published yellow paper. It will introduce native support for verifiable off-chain computation, allowing complex logic to be executed off-chain while providing cryptographic proofs that can be verified directly on-chain. This will significantly expand Kaspa’s programmability and smart-contract-like functionality in the future without compromising its core Proof-of-Work security model.
UTXO Commitments and Data Capabilities
Kaspa uses MuHash combined with SMT to implement incremental UTXO commitments, supporting lightweight verification, proof compression, and state consistency checks. In addition, the transaction Payload field can carry application data that is included in the transaction hash, facilitating L2 ordering, data commitments, and early smart-contract data layers.
Issuance and Governance Model
Kaspa uses a completely fair Proof-of-Work mining distribution with no premine and no VC private allocations, closely mirroring Bitcoin’s credible issuance model and reducing risks of centralized governance. Protocol upgrades are conducted transparently through the KIP proposal process and open discussions on Kaspa Research, fostering research-driven, community-consensus-based development.
Coordination markets on $KAS be perfect for the fundraising of the upcoming London College event.
It would work like this, if 1000 people donate ‘$10’, I will also donate ‘$10’.
Key reasons people don’t donate is they feel it’s not worth it unless everyone else does. $KASPA
Coordination markets on $KAS be perfect for the fundraising of the upcoming London College event.
It would work like this, if 1000 people donate ‘$10’, I will also donate ‘$10’.
Key reasons people don’t donate is they feel it’s not worth it unless everyone else does. $KASPA
Tomorrow it's finally time for the first community hangout!
Kaspa Under the Hood: Setting the Stage for vProgs
Grab a beer, coffee, tea, or whatever keeps you going, and join us for the first regular Kaspa community hangout.
We will start with a high-level presentation of the upcoming vProgs architecture and Kaspa’s next stages of development. Since the architecture is extensive, this first session is meant to set the stage for future deep dives.
The presentation is meant to be accessible to people with different technical backgrounds. We will take things step by step, build up the necessary context, and gradually develop a shared understanding of Kaspa’s architecture, trade-offs, and long-term vision.
After that, we will move into a relaxed open discussion where people can ask questions, share ideas, and talk about anything interesting: Kaspa, decentralized infrastructure, incentives, technology, philosophy, or the future of humanity.
Bring your ideas and questions, grab a drink, and join the conversation!
https://t.co/dDIudhbwCG
@Kasdaghopesfwo@KaspaSilver Meh, I could care less about red weeks, we don’t have any proper funding which means building takes time. My only concern is we don’t get the protocols which bring the builders in time, price doesn’t phase me whatsoever until we have a proper ecosystem.
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.
We have listed Falcon Finance (FF)!
Repost for the chance to win $100 of FF 💸
https://t.co/Po8i7xZGsz
Happy Trading 🚀
*Must have a verified CoinSpot account.