This one seems to have gone almost unnoticed.
Kii Foundation has just made the source for Portrait public.
It’s a high-level language for Kaspa covenants that compiles down to SilverScript, with a library of reusable patterns already covering things like vaults, escrow, auctions and registries.
There are 35 covenant sources in the repo. 10 are cross-layer/vProg patterns, and Kii documents 5 of those as already settled on TN10.
What caught my attention is the tooling around it.
Portrait includes Lens, which uses Z3 to check properties of the covenant model, and Composer, designed to catch problems when multiple covenants interact.
Basically, Toccata gave Kaspa the primitives. SilverScript gave developers a way to express them. Portrait is now trying to make them easier to build, check and reuse.
Still very early though.
It’s pre-production, unaudited and testnet-only. Nothing here is deployed on mainnet.
But this is another interesting piece of the post-Toccata stack quietly taking shape.
Source:
https://t.co/3HfWFCxSQy
https://t.co/Th2qIcq6HZ
🤯 How many new #Kaspa holders have NEVER seen all of these connections together?The Yonatan Sompolinsky / Satoshi Nakamoto rabbit hole goes much deeper than just the famous name coincidence. 👀• The strange name/anagram connection
• April 5 — the same date listed as Satoshi’s birthday
• Yonatan’s early work on Bitcoin consensus and scalability
• GHOST → GHOSTDAG, described as “A Scalable Generalization of Nakamoto Consensus”
• Kaspa carrying forward PoW, UTXO, fair-launch and decentralization principles — but built for dramatically higher speedAnd then there’s the “ONNY” / Hebrew “Ani” (אני) wordplay that some interpret as another layer of the puzzle. 🤯None of this proves Yonatan is Satoshi.But when you put everything on ONE page…That’s a LOT of coincidences. 👀Old-school Kaspians probably remember this rabbit https://t.co/xwrZtmAFj3 kaspa:native holders — did you know about it?$KAS #Kaspa #Bitcoin #SatoshiNakamoto
That final question is important. “New kaspa:native holders — did you know about it?”
Looks like @Bitwise have got $KAS on their radar family 👀🔥
Ryan Ramussen, Bitwise Head of Research, just confirmed that $KAS is on his radar thanks to @realvijayk (legend💪)
I wonder if Matt Hougan, Bitwise Chief Investment Officer, shares the same sentiment...
Study $KAS, before Bitwise present it to these 400 wealth managers and they get their first
@Avila66813Avila heavy wip. 6 milestones defined.
first 2 are:
- incremental algos (pseudo code and analysis showing incrementality also under worst-case scenarios)
- testnet (unlike devnets, this means no security relaxation)
both are progressing very well
The interest around $KAS is growing on the institutional front
We're talking names like GoPro deciding to move on chain
And they're talking about $KAS and ZEC among all tokens
2027 is going to be crazy
Got spare time? contact Solana teams, small and large alike, and get them interested in this kaspa:native on-chain programmability workshop.
You'll do yourself and Kaspa a **great** service by so doing--one which has effect on the long term health & prosperity of #Kaspa.
Just connected my first Kaspa miner, the KS0, and it’s officially running. ⛏️ $KAS
I’m not a technical person, but following the directions made the setup surprisingly simple.
I know this little KS0 isn’t going to make me rich, but I set it up myself, and now I’m doing my small part to support the Kaspa network.
That feels pretty damn good.
$KAS for the masses. 🧡
“Whether anyone actually builds on the rails.”
We built. The first covenant AMM on Kaspa - swap, LP, farms. Pure L1 script. Live on tn10.
16 hours since launch: 2 users.
Two. In the loudest community in crypto. Free testnet KAS, zero risk, five minutes to try - and nobody came.
That’s not what a strong community looks like. A strong community stress-tests its own rails before mainnet, breaks things, files bugs, builds the moat.
Prove the talk is real:
https://t.co/haQ1dFCIwx
#KAS #Kaspa #KaspaDefi
This is a pretty unusual use of what Toccata brought to Kaspa.
@aglovale0x has managed to verify SLH-DSA-SHA2-128s — the NIST FIPS 205 post-quantum signature standard — directly inside Kaspa Script.
And there are actual TN10 spends behind it. Four transactions have been published across SLH-DSA and LMS, with SLH-DSA successfully spent twice from the same key and address over different messages.
Kaspa didn’t need a new post-quantum opcode to do it. The implementation works with transaction introspection and compute budgeting already available after Toccata.
It’s nowhere near practical for everyday transactions yet. The SLH-DSA spend is about 97 KB, roughly 89 KB of which is the redeem script, and the whole experiment is unaudited and testnet-only.
So this doesn’t suddenly make Kaspa “quantum-proof”.
The part worth thinking about is what it says about Toccata itself: an upgrade built largely around programmability and covenants can already run a full FIPS 205 verifier without requiring a consensus feature specifically designed for post-quantum cryptography.
@Max143672 explored another route earlier with XMSS^MT directly in Kaspa Script.
Max, I’d be interested in your take on how the two approaches compare in practice.
Source:
https://t.co/tb0y7uozNe
#Kaspa $KAS