Kaspa

nakamoto consensus unchained. digital money traveling at internet speed. non-representative community account.

[Kaspa @kaspaunchained]

$KAS The Toccata Hard Fork is now live! Update your nodes well before June 30th so that you can remain in consensus!

https://t.co/cNKPF0esfg

[Michael Sutton @michaelsuttonil]

Kaspa Toccata mainnet process update:

Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing.

Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today

[Kaspa @kaspaunchained]

$KAS Toccata hardfork test on testnet-10 was a succuss. Onwards towards mainnet! Official date details coming soon!

[Luke Dunshea @elldeeone]

toccata live on testnet 10

[Kaspa @kaspaunchained]

$KAS is approaching closer to Toccata going live on mainnet. One final hardfork test is being done on testnet-10 happening today!

Testnet-10 source: https://t.co/Q5hNGqGkYY

CPU miner for testnet-10: https://t.co/DHYNVipRtC

[Ori Newman @OriNewman]

The Toccata hardfork stack is now ready, and we’re entering the final stage before mainnet activation: a full hardfork activation on Testnet-10. The scheduled activation point is: May 18, 2026, 16:00 UTC DAA Score: 467_579_632

Everyone is welcome to join and mine on testnet, so we can verify the transition works fine before mainnet activation.

I wrote detailed instructions for joining as a testnet miner (Link in reply)

[Luke Dunshea @elldeeone]

https://t.co/n1qOT2qd7m has been refreshed.

Kaspa has a lot going on, but the main site does not need to put it all at the front door. Its first job is simple: help someone arrive, understand what Kaspa is, and know where to go next.

The previous site accumulated more over time. Pages, explanations, resources, and audiences were added. This version starts smaller, so it can grow with Kaspa from here.

The refresh is not just visual. The wording, structure, and narrative direction all needed attention IMO.

The content traces back to @hashdag’s writing, simplified for a first read. Kaspa is already deep enough. The first read should not make people work harder than necessary.

There are many true ways to talk about Kaspa, but https://t.co/n1qOT2qd7m cannot carry twenty narratives at once. For this version, the strongest one to unify around is real-time decentralisation.

Part of the refresh was also about making the builder path easier to follow. https://t.co/n1qOT2qd7m gives people the overview of what exists, why it matters, and where to go next. https://t.co/FrgQZdNMey gives builders the deeper material, with room for examples, detail, and ongoing improvement.

https://t.co/FrgQZdNMey starts with @IzioDev's work and has the broader goal of bringing important Kaspa L1 builder documentation into one place.

Both repos are public. Pages will be added, wording will change, gaps will be filled, and the work can happen in the open.

Big shoutout to @kasmediadotcom for their support in helping bring this refresh together.

Have a look around. If you see something that can be better, please open an issue or PR.

[Kaspa @kaspaunchained]

Feature freeze is here for Toccata! This means that no further consensus rule changes will be made as preparations are being made for the Toccata hard fork.

Toccata is going to bring loads of features to Kaspa such as ZK proofs, Programmable UTXOs, and more!

[Michael Sutton @michaelsuttonil]

Toccata consensus feature freeze is finally here after a heroic last-mile push by kas core devs.

Aiming to reset TN12 tonight, or tomorrow at the latest.

Genesis update:

+ 0x6b617370612d746573746e6574 // kaspa-testnet
- 12, 2 // TN12, Launch 2
+ 0x544f4343415441 // TOCCATA
+ 12, 3 // TN12, Launch 3

[Kaspa @kaspaunchained]

Watch Yonatan Sompolinsky speak at @OxfordUnion $KAS

https://t.co/FZVtZJlL8N

[Kaspa @kaspaunchained]

Michael Sutton from Kaspa Core delivered an article giving an outlook for the upcoming "Toccata" hard fork which includes covenants, based zk apps, and why the start date was moved.

"Kaspa Covenants++ “Toccata” Hard-Fork Outlook"
https://t.co/SwBymJ8QsE

[Kaspa @kaspaunchained]

Kaspa stays true to Nakamoto's vision: pure decentralized scaling through blockDAG innovation, not hype or shortcuts.

[Evaldas. Code first @lunfardo314]

I’m following #Kaspa because it truly follows the Nakamoto path. Its blend of visionary research and solid engineering is a rare find in the crypto space. Godspeed.

[Kaspa @kaspaunchained]

Keystone has announced their efforts to integrate Kaspa to their wallet.

Keystone is a fully open source air gapped wallet. Software and hardware can be verified by the public.

[Keystone Hardware Wallet @KeystoneWallet]

📢 Big News for Kaspians 𐤊

Our integration work with Kaspa has been accelerating.

So far, we have completed the dev work:
+ address generation,
+ public key export, and
+ transaction parsing design.

Moving forward, we're partnering with Kaspium Wallet to enable true self-custody and cold storage of your Kaspa assets through PSKT protocol support 🤝

The long-awaited transaction parsing feature has been set as one of our key milestones. With Keystone’s 4-inch screen, blind signing becomes a thing of the past!

Exciting developments and challenges lie ahead, and we'll keep you posted every step of the way.

Share this with your Kaspa friends and let them know that Keystone support is coming 🙌

[Kaspa @kaspaunchained]

FrostCard is a new open source NFC cold storage device is being developed.

Its goals are as follows:

Kaspa only
Security chip programming being open source
Covenants compatibility
Sovereign auditing

[FrostCard @FrostCardKaspa]

“Tangem if it was fully open source”

Built with Covenants — enabling:
• Spending limits
• Whitelists
• Time locks
• Recovery
• And more

Security shouldn’t be complicated.

Frost Card
Cold storage, re-engineered. ❄️

#Kaspa only.
Target release May 31/2026

[Kaspa @kaspaunchained]

Kaspa Eco Foundation concluded a grant that was given to a @eliottmea related to oracles. The grant was well spent and much research resulted from it!

Read more about it below!

[Kaspa Eco Foundation (KEF) @Kaspa_KEF]

Today we're concluding a research grant extended to @eliottmea, who picked up a very challenging topic to work on: how to build an effective oracle?

Over the course of the grant, our talented young researcher put his discoveries in two documents: the first, A Mathematically Rigorous Framework for Cross-Exchange Price Discovery, proposes a framework for aggregating prices across multiple exchanges into a single manipulation-resistant feed, anchored by a decentralized arbitrage network, and the second, Incentive Compatibility in a Discriminatory Limit-Order Auction, takes a mechanism design lens — asking whether it's possible to construct an auction where honest price reporting simply becomes the rational thing to do.

Read here: https://t.co/LV3pi5ZoH3

At @Kaspa_KEF, we believe investing in #Kaspa means investing in faithful talents who are dedicated in #Kaspa. We're proud to have supported @eliottmea in this work, and we look forward to seeing more promising research proposals!

[Kaspa @kaspaunchained]

Recently a few members from Kaspa Core held a discord meeting to discuss SilverScript, Covenants, and much more that is coming to Kaspa in the upcoming Covenants++ hard fork.

Tune in here: https://t.co/3AIVIftR7v

[Kaspa @kaspaunchained]

The anticipated covenants++ hard fork will not be May 5th but about a month later.

No dates given are ever absolute. Much testing and research is always involved which can always push things back.

Stay in tune with Kaspa Core developments via Telegram: https://t.co/lXsBs4Pwdg

[Kaspa @Kaspa_BlockDAG]

Rusty Kaspa v1.1.0 is out.

Faster syncing, less storage, and exchanges/wallets building on Kaspa just got a much easier time of it.

The big one for integrators is a new API call that returns chain updates and transaction data together in one go, instead of having to juggle multiple parallel requests. If you've ever tried to integrate Kaspa and cursed at the DAG complexity, this is the fix.

Node operators get up to 3x faster sync in the early header stage on some machines, plus lower disk usage.

The stratum bridge also shipped as beta if you're running mining infrastructure.

One heads-up - DB version bumped to 6. Upgrade is automatic, but you can't roll back to an older version without wiping the DB.

https://t.co/fJkvYX0eOS

[Nicholas @NicholasSproto]

All AI agents will require economic and physical defensive skin in the game systems as their mark of beast to maintain cybersecurity and combat hoaxes. This is definitely the future. However, I think Kaspa will do a better job at it than Bitcoin as real-time synchronicity will be necessary.

[Kaspa @kaspaunchained]

Kaspa is reentering the GPU era.

ZK proving is a method for proving that a computation or statement is true without revealing any private data or the actual computation itself.

[Michael Sutton @michaelsuttonil]

a few unrelated observations/notes

1. @manyfest_ recently made me realize that beyond the obvious point that covenants on Kaspa can serve as first class state machines, they also have 2 significant properties:

• they are lightweight: on chain we store commitments to rules/state, and txns provide the witnesses for changes (transient cost vs persistent contract storage/rent)

• they can be entered atomically (multiple parties can create and enter into the covenant in one txn)

the last two properties seem to have significant potential in the agentic era. agents can define custom rules and agreements between them without deploying a contract (compare this to eth/sol contract/program). covenants are a fast, lightweight tool for such agent-to-agent rule systems.

2. Kaspa is reentering the GPU era. Kaspa r&d is already experimenting with several GPU workstations for zk proving.

3. @coderofstuff_ is doing fantastic work advancing dk in parallel to covpp work (and making sure the content of my long-overdue, unshared post gets shared nonetheless) https://t.co/Ij6QSXKUIr

[Kaspa @kaspaunchained]

@SummerSon159 you might be interested in https://t.co/HOHfYNrynN

it's still wip though

[Kaspa @kaspaunchained]

dagknight v0 devnet progress doesn't stop

branch live on the rusty-kaspa repo - checkout the r&d telegram for more info

[coderofstuff @coderofstuff_]

Dagknight technical progress

As would be mentioned in a still unshared post by @michaelsuttonil, the dagknight effort is split into v0 devnet, v1 testnet and v2 mainnet candidate.

I’ve been testing the current v0-based implementation in a small devnet with the help of some testers who run nodes and miners with me.

The DK work can be thought of as split into two parts: (1) implementing the actual protocol and (2) wiring it up and using it. The testing and development over the last month has been focused on (2).

Obviously, DK is a consensus change for selecting parents. What’s not so obvious is that such a change affects DAA, coinbase, IBD, pruning and a lot more. Each of these areas is very sensitive and requires proper understanding to wire correctly. An important consideration and difference from GD is that DK does not focus on maximizing a property like blue work. So to maintain topological properties of blue work, an independent (free) GD implementation is kept running specifically for maintaining blue work. This allows us to keep using the property for topology. Coloring and blue score use the megachain induced by DK. The wiring around DK as of this posting is in a working state, but still needs to be reviewed.

Next efforts will be focused on protocol specific components, particularly Tie-Breaking and incremental UMC.

Attached are some captures from the internal devnet. The dense DAG image is what happens when things related to DAA or other similar consensus parameter causes a node to insist on their POV. The video is a recent snippet of the KGI running on the devnet showing (perhaps not obviously) DK at work.

The current “dagknight” branch is now posted on the main repo. A topic in the Public R&D has been opened for Dagknight development.

[Kaspa @kaspaunchained]

@Davincij15 @DominicTrades can't stop, won't stop