Kaspa's upcoming covenant-centric hard fork: What we know

Table of Contents

desk of contents

What’s Kaspa's covenant-centric onerous fork? What’s the Could 5, 2026 onerous fork timeline? How do native belongings and covenants work in Kaspa? What’s compute? $DAY (CDAG)? What are vProgs? How are they totally different from good contracts? What function does Zero Data (ZK) play? How does Sparkle relate to vProgs? Do onerous forks have an effect on safety, MEV, or node necessities? What does SilverScript add? Conclusion Supply: FAQ

What’s Kaspa's covenant-centric onerous fork?

In accordance with Terra's thread,when We’re making ready for the deliberate covenant-centered onerous fork. Mainnet activation Improve expands on Could 5, 2026 Layer 1 (L1) Programmability by the introduction of native belongings and expanded conference performance. It’s also Verifiable packages (vProgs) Zero information (ZK) integration.

Kaspa operates as a proof-of-work blockchain utilizing the blockDAG structure. the crescendo improve In Could 2025, throughput elevated to 10 blocks per second (BPS). Subsequently, future onerous forks will construct on that basis with out altering the node necessities or consensus fundamentals.

Core builders describe this launch as a scoped improve. It focuses on enabling native token issuance, programmable spending guidelines, and ZK validation at L1.

What’s the timeline for the onerous fork on Could 5, 2026?

Kaspa Convenant-centered onerous fork countdown (as of writing) | Kas Dwell

In accordance with Terah's thread, a number of milestones are deliberate previous to mainnet activation.

Testnet 12 (TN12) reset: Scheduled for early February 2026 to assist testing of covenant and native belongings.
Sequencer dedication KIP: Anticipated round February 12, 2026. This proposal introduces a miner payload dedication to reinforce real-time decentralization.
SilverScript launch: A high-level programming language for writing packages with Kaspa. Developed by Ori Newman and his contributors to simplify covenant growth.
Mainnet onerous fork: Could 5, 2026.

Put up-hard fork upgrades embody DAGKnight, which targets adaptive consensus and throughput above 100 BPS, and an entire deployment of vProgs.

How do native belongings and covenants work in Kaspa?

Layer 1 native belongings

The onerous fork introduces native belongings with assist for: KRC20 token. These belongings exist instantly on L1 and will be transferred atomically.

Atomic transfers apply to:

Regular inline conference
Enforcement of ZK and Non-ZK Phrases
KRC20 token switch

Inline phrases generate immediate proof inside your pockets. There isn’t any separation between transaction information and state transitions. This design helps atomicity and deterministic execution.

Prolonged Phrases (Conventions++)

Kaspa's phrases system is impressed by Bitcoin's analysis on programmable UTXO spending phrases. Covenants++ extends this method to allow extra expressive transaction guidelines.

Use instances embody:

Vault-style safety controls
escrow mechanism
conditional switch
structured token logic

The system maintains a UTXO mannequin relatively than a completely account-based good contract.

what’s calculation $DAY (CDAG)?

Onerous forks introduce computing. $DAY (CDAG). CDAG information all learn and write declarations made by a program.

This construction is:

Monitor useful resource utilization
Regulate dependencies between packages
implement fuel contracts

This design is corresponding to blockchain execution fashions equivalent to Solana and Sui, however is totally carried out inside Kaspa's blockDAG atmosphere.

CDAG performs a central function in realizing vProgs sovereignty.

What’s a vProg and the way is it totally different from a wise contract?

vProgs are sovereign packages that run outdoors of L1 whereas figuring out outcomes on L1 by proofs.

Principal properties:

Sovereign enforcement: Every vProg defines its personal throughput and dependency guidelines.
Fuel-based dependency management: A vProg can’t learn the state of one other vProg with out paying fuel for useful resource consumption.
Non-atomic switch: vProg, like native belongings, just isn’t clear to L1. Transfers are asynchronous and non-atomic.
wrapped $what Necessities: Non-inline covenants should be wrapped $what By means of a daily bridge. Native L1 $what It can’t be used instantly.

This design separates computation and state from L1 whereas sustaining shared sequencing and settlement.

Who ought to construct vProgs?

Based mostly on group dialogue, most common software builders might not want vProgs.

Nonetheless, vProgs might object within the following instances:

app chain architect
Group evaluating rollup fashion programs
Mission to construct AI brokers with large-scale on-chain state
System designers evaluating L1 contracts, L2 rollups, and hybrid fashions

vProgs combines built-in L1 sequences with externalized state and computation.

What function does Zero Data (ZK) play?

The onerous fork integrates ZK validation at L1 and extends earlier proposals equivalent to: KIP-16.

The supported options are:

Groth16 proof verification
Trustless bridging to L2 programs
Potential privacy-oriented purposes

The preliminary software is anticipated to run inline with the pockets producing proofs instantly. Even the covenant-based ZK implementations developed by contributors equivalent to Hans and Maxim are anticipated to run on commodity {hardware}. No particular attestation infrastructure is required for preliminary deployment.

A normal laptop computer can generate proofs primarily based on present assumptions.

Privateness-focused packages are technically potential even after a tough fork. Nonetheless, privateness just isn’t listed as a serious concentrate on the roadmap.

How do Sparkle and vProgs relate?

Sparkle is an structure proposed by Anton to mix computational DAGs and ZK proofs. Sparkle and vProgs each use CDAG and ZK elements, however deal with totally different design points.

A function of vProgs is dependency regulation. Every program controls throughput and avoids any exterior dependencies. This mannequin helps composability whereas sustaining isolation.

Does a tough fork have an effect on safety, MEV, or node necessities?

Safety funds: No direct affect is anticipated within the quick time period. Enhancements depend upon precise product adoption, not infrastructure adjustments.
Node necessities: No adjustments.
MEV Kickback Public sale: Contemplating the present stage of ecosystem growth, it’s thought of untimely.
STARK PoW Grinding: The dialogue references the historic conduct of early Ethereum, the place addresses with main zeros diminished fuel prices, ensuing within the creation of the proof-of-work grind market. This point out was situational, not present performance.

What does SilverScript add?

SilverScript is a high-level language designed for Kaspa packages. It’s meant to simplify contract and program growth.

Its design objectives embody:

Simple to learn syntax
Accessibility for brand new builders
Compatibility with automated instruments

SilverScript is anticipated to decrease the barrier to creating contract-based purposes as soon as native belongings are up and working.

conclusion

Kaspa's covenant-centric onerous fork extends layer 1 performance by native belongings, prolonged covenants, and ZK validation. CDAG is launched for structured dependency monitoring, laying the inspiration for sovereign vProgs. This improve allows programmable token issuance and atomic transfers whereas preserving present node necessities and proof-of-work consensus.

The Could 5, 2026 activation marks a technical step in Kaspa's roadmap. This provides structured programmability on the protocol stage and prepares the community for additional upgrades equivalent to DAGKnight or full vProgs deployment.