just want to make cool shit and talk about kaspa
Australia
Joined January 2010
- Tweets12.3K
- Following2.7K
- Followers5K
- Likes31.7K
Luke Dunshea retweeted
Saturday's session is now on YT youtube.com/watch?v=vZUS45fY…
I'll continue the session today at 2 PM UTC, fixing errors and performing a valid KCC20 token borrow transaction.
Luke Dunshea retweeted
🚨BitGo quietly built $KAS custody.
TSS + TSS_COLD signing, and seven custody flags: BitGo Trust, India, MENA FZE, Germany, Frankfurt.
Registered as a production coin in BitGo's own statics. Commit message: "feat: kaspa support."
Marketing gets announced. Plumbing gets shipped
Luke Dunshea retweeted
*now* is the time to build on kas. I prefer to hold the mindset that assuming no further updates were to happen ever (not saying this is the case, just the mindset), what can be built now with what we have?
Luke Dunshea retweeted
A bit of trivia: the dagknight devnet is running on this and it looks to be working fine. Luke’s looking for testers on mainnet. If you’re up for it, try it out
hello, i'm looking for kaspa node testers to assist me in testing this - much progress has been made since my post in 2025 and i'm ready for mainnet testing.
if you're technical enough to do this (or have AI to assist you - it's not hard), have a spare computer (or spare compute on your vps) to run an additional kaspa node pls join me here 🙏
t.me/kasparnd/5090/15610
thanks
Luke Dunshea retweeted
As DeFi starts to take shape on Kaspa, it might be a good time to repeat the basics:
Just as you should refuse to sign a paper contract you are not allowed to read, you should not pay into smart contracts with hidden rules. DYOR and know what you buy.
There is still an active and meaningful effort to define standards for covenant scripts and fungible tokens. These important decisions will ensure tokens are recognized, supported, and composed with other ecosystem projects. Otherwise what would be the value of an asset that can only be recognized and used within a specific app?
Let’s continue building great things and do DeFi the right way.
Luke Dunshea retweeted
@michaelsuttonil 's Argent is a beautiful experiment.
Argent extends SilverScript with higher-level concepts, which makes it easy to develop entire covenant applications that express complex relations with each other ones (aka "composability").
In the image, you can see the definition of a League actor which is one of the covenants of a Rock/Paper/Scissors tournament game.
League defines a Register entrypoint which emits a new player, and mints them R/P/S tokens with which they can duel.
Those few lines of code express a very complex TX shape which includes two applications and 4 different actors(seen in this shitty ai-gened-img)
From Kaspa's prespective, applications are nothing but scripts, and scripts can be written in many ways.
For us to be able to create applications that can work with each other, we must agree and develop conventions which applications must implement.
The new "kccs" github repo is the place where those conventions will be finalized after discussing them on Kas-Smiths.
Luke Dunshea retweeted
to avoid AI psychosis it's very important that you do not converse 'with' the LLM in the indefinite & unscripted way you would with another human being
you can ask it do things, perform multivariant tasks & work through complex problems with it, but the second you start asking it open-ended questions on broad topics, you dip into a dangerous game of confirmation bias looping on unknown unknowns
ai is a tool. it is not a friend
you will suffer consequences if you treat it as such
Luke Dunshea retweeted
SwiftyKaspa - github.com/pichukov/swifty-k…
For anyone building native iOS or macOS apps on Kaspa (wallets, analytics tools, etc.) - I’ve just released an open-source Swift package 🚀. It includes all you need to work with wallets, transactions, script engine, covenants, and more - all written in pure Swift. No more Rust runtime or WASM required in your iOS/MacOS native projects.
I hope this will accelerate products and experiments on Apple platforms. It dramatically lowers the barrier: anyone can now vibe-code their own native iOS Kaspa wallet in ~10 minutes 😉.
It can also help bring Kaspa support to existing multicurrency wallets (where adding Rust or WASM is often not an option) and let wallets that already support Kaspa (e.g. @Tangem) integrate new Kaspa related features much faster.
The package closely mirrors the Rusty Kaspa implementation in detail. I use it in my personal wallet, but please do your own research before using it in production.
Luke Dunshea retweeted
To the dev who left Ethereum because a single failed tx cost more than lunch:
To the Solana builder who watched a handful of validators decide what "decentralized" means:
To the Bitcoin maxi who wanted programmability without touching immutability:
Kaspa's Toccata hard fork just activated.
Native covenants. On-chain ZK proof verification. Partitioned execution lanes so one app's congestion can't touch another's. Still 10 blocks/sec. Still pure PoW Layer1
No countdown clock needed. It's already running.
Study kaspa:native #Kaspa
Luke Dunshea retweeted
Now that we have programmability paths on Kaspa, the need to converge on ecosystem standards in the right way becomes paramount.
It appears we lack a fitting forum for such discussions.
A primary and timely example would be a standard specification for native assets. We need a place for technical discussions where wallet devs, explorer devs, community thinkers, and core devs can brainstorm and rapidly converge on ideas without communication gaps, and without important ideas and messages getting lost to oblivion.
As a start, here is a call for community discussion on native assets.
An initial discussion on kas pub rnd is linked below, but again, to me this feels like an echo chamber, with probably the most important voices missing.
>>
Luke Dunshea retweeted
tn10.kaspa.stream/transactio…
U know what is that? first post-quantum signature on kaspa just landed. XMSS^MT
The script is huge (~84KB) because it has to unroll a loop of ~1,650 hashings on-chain but it verifies. and it works.
isn't that cool?
toccata to everyone
Luke Dunshea retweeted
for anyone not on Kaspa telegram:
Kaspa Python SDK releases 2.0.0 and 2.0.1 are now available.
Built wheels are available on the corresponding GitHub & PyPi releases.
v2.0.0
Built from rusty-kaspa 2.0.0. Includes full compatibility with Toccata Hardfork features, new Wallet API (via wrappers over rusty-kaspa Wallet), other small changes & supporting components.
Release (with full change log): github.com/kaspanet/kaspa-py…
v2.0.1
Built from rusty-kaspa 2.0.1 and includes all pertinent changes.
Release: github.com/kaspanet/kaspa-py…
PyPi: pypi.org/project/kaspa/2.0.1…
Docs: kaspanet.github.io/kaspa-pyt…
While 2.0.1 is the latest, 2.0.0 changelog includes important notes.
Please file issues here: github.com/kaspanet/kaspa-py…
Luke Dunshea retweeted
**Official Toccata Release — Mainnet Hardfork Activation Included** (Links in reply)
We’re excited to announce the official Kaspa release containing the **Toccata Hardfork** activation logic.
Toccata is scheduled to activate on mainnet at DAA score `474,165,565`, expected around **June 30, 2026, 16:15 UTC**.
This is a consensus-changing upgrade. All node operators, miners, pools, exchanges, indexers, wallets, and infrastructure providers must upgrade before activation to remain compatible with the network.
Toccata introduces a major expansion of Kaspa L1 capabilities, including:
• **Native L1 covenant support** through transaction introspection, allowing for more expressive contracts, including stateful contracts
• **Covenant IDs**, providing stable covenant lineage across UTXO transitions, so covenant instances can preserve continuity as their state moves from one UTXO to the next
• **ZK proof verification on L1** via `OpZkPrecompile`, enabling to trustlessly offload computation off-chain.
• **Partitioned sequencing commitments**, improving support for based ZK applications by making lane-local proving scale with relevant activity rather than global throughput
Please upgrade as soon as possible and verify your nodes are running the new release well before the activation DAA score.
Thank you to everyone who contributed to designing, implementing, reviewing, and testing Toccata.
Luke Dunshea retweeted
why I’m personally excited about Kaspa’s upcoming Toccata covenants
- for the first time, I can build creative, complex apps directly over infrastructure I helped design and build
- we designed under architectural constraints, but the result came out surprisingly expressive and powerful
- Silverscript is cool as hell
- I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1
- (nottoself: create a 10-minute video showing the building of such an app e2e)
- I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet
- covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover
- sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking)
- complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it
- as I’ve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves
- I didn’t even mention based apps yet. That’s a whole vertical that isn’t ready for exploration yet, but will be very soon
Luke Dunshea retweeted
Introducing 𝙋𝙧𝙤𝙤𝙛 𝙤𝙛 𝙍𝙤𝙡𝙡: a verifiable slot machine on Kaspa.
Send a payment, watch the network pick it up and confirm it, then see future Kaspa blocks turn into a slot result.
A game, and also a hands-on network demo
proof-of-roll.net
$KAS #Kaspa
>>>
