Embsio 𐤊 retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
Embsio 𐤊 retweeted
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
github.com/kaspanet/rusty-ka…
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
xitter.cf/Max143672/status/21034…
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
github.com/kaspanet/kaspa-py…
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
xitter.cf/KasperoLabs/status/210…
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
xitter.cf/manyfest_/status/21030…
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
github.com/kaspanet/kccs/pul… github.com/kaspanet/kccs/pul…
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
github.com/supertypo/simply-…
thanks to everyone building. see you next week.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined.
On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state.
On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant).
This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it.
A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information.
The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity.
After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself.
Read more on Kas-Smiths:
kas-smiths.org/t/kcc-23-conv…
Or read the KCC draft:
github.com/kaspanet/kccs/pul…
Embsio 𐤊 retweeted
After endless audits, reviews and refinement cycles, it’s finally here, ladies and gentlemen: silverscript 🩶📜
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
kaspa:native Update
Lows taken on the important charts, strong reaction. Got a bullish shift of mid timeframe structure while breaking above another MTF trendline and now at the first heavy resistance.
There are no changes to the HTF outlook until closures above the 4c S/R + swings of the previous rejections there. Then, long-term pullback entries will become high priority and much more viable, and the odds that the bottom is in will drastically improve.
However, a monthly swing failure is substantial. Under normal conditions, I would expect an eventual visit to range highs (5.3 swing), but this would be immediately derailed if BTC turns from here.
Will depend on how the closures look over the next day or two for either pullback targets or confirmation of lower. As of now, 3.5 -3.2 would be healthy, below that risks falling back into trend and starts to look like a rejection. Back below 2.7, consider this another failed rally.
It doesn't need to be said just yet, but I'll remind that HTF structure won't actually change until closures above the 6.3 swing. So, in theory, price could rally all the way to 7c, close below 6.3 and fall all the way back for new lows. Would be absolutely brutal, and I wouldn't consider it very high probability but... it is actually possible. (where have I heard this before)
For now, the optimistic view is this still looks like long-term accumulation. Depending on the discipline, these patterns can have natural targets (at least for taking profits). In this case, they line up fairly well with the 4c S/R, the 5.3 swing and 7c, so do with this info what you will.
Will update when necessary.
$KAS Update
Even though it isn't really necessary as the low still hasn't been tested, I've seen your comments/messages so here's a little update on how I'm seeing things currently.
Firstly, the main bias remains targeting the 2.5c HTF swing low after the dual rejections from the 4c S/R and subsequent breaking of the MTF structure. This will only be invalidated by a break above the S/R.
Despite the time spent building a base in these monthly demand zones seeming healthy, it still doesn't negate my leaning toward an eventual trip to the 1.7c key level as the most probable outcome.
That said, this is a textbook weakening trend. The boldened trendline is the second (and more definitive) MTF TL that KAS has flipped now. See the peaks of the prior half of all price action in this chart rejecting from this line, while the latter half lows are bouncing from it.
My guess is price could bounce around in this blue triangle zone for a while, possibly until the end of the year. Riding it all the way down to the mid 1c area, where it coincides with the expected macro low date for BTC, wouldn't surprise me.
This gives a sort of built-in warning system, in that, a break above or below this zone before around that date should be a sign of things to come.
And with the market near extreme lows in volatility, one last violent move from here to negate everything I just said also wouldn't surprise me (in fact, this may be even more probable). Preferably straight to 1.7c and we're done with it.
However, if that's not the case, it needs to be said that regardless of how accurate I've been charting this asset, and regardless of how uniform crypto cycles have been, the possibility of chaos still needs to be considered.
From the beginning I've argued against the likelihood of a macro bottom forming above 3.6c and plainly said even that would be mild from a historical standpoint. Again, I'll reference these two posts as sources: xitter.cf/J3Charts/status/189696… & xitter.cf/J3Charts/status/189738….
For the record, this was when the majority were telling me we wouldn't go below 10c... then it was 5c and now here we are.
I won't sit here and claim I thought sub 1c was necessarily probable, but I absolutely made it clear that it was MORE probable than bottoming at 5c or higher - and not just a little more, much more.
Dropping almost all historical bias, my brain sees two very natural targets from where price sits now. It doesn't make sense within the context of the crypto cycle, but it makes sense on the chart.
Poetically, they are 7-9c above and .007-.009c below.
I'll get out ahead of this and reiterate that I don't think a trip sub 1c is probable atm, but it will be if for some reason price doesn't react the way I expect it to from the 1.7c level.
Alternatively, with price spending so much time in what I considered the first reasonable area for a macro bottom to form, it wouldn't surprise me to maybe sweep the low and push all the way toward 7-9c from here.
In either scenario, this would ultimately be me being wrong -- which was the purpose of this late-post warning. Just making it known I could certainly get blindsided here.
ALL that said, I'm still just over here waiting to see if we touch these lows...
Until next time. 👋
Embsio 𐤊 retweeted
Kaspa. KAS Mining. KuMining.
We’re live on Telegram! Join the KuMining KAS Mining AMA to discover what makes Kaspa unique, learn how KAS mining works, and see how easy it is to get started with KuMining.
🎁 Explore USDT, KAS & More rewards during the campaign.
👉 Join KuMining on Telegram and tune in now:
t.me/kumining_en?utm_source=…
Embsio 𐤊 retweeted
Yonatan Sompolinsky’s Staghunt: Massive Bullish Signal for the Kaspa Ecosystem! 🚀
Kaspa founder @hashdag is launching Staghunt — a bold new infrastructure venture building coordination markets.
Quick overview: Crypto nailed individual sovereignty. Staghunt tackles the next frontier — group sovereignty with “Intendo” primitives (conditional, atomic commitments that fire only when the pack forms). Perfect for solving coordination failures in liquidity, launches, migrations & AI agent swarms.
Built leveraging Kaspa’s real-time speed & finality — this elevates $KAS as foundational tech for the machine economy. Huge validation for the ecosystem!
#Kaspa #Staghunt #YonatanSompolinsky #AIAgents #CoordinationMarkets #Crypto
Full article here: [ARTICLE LINK]
Crypto gave individuals sovereignty. Staghunt is betting the next frontier is the group version: coordination markets.
Read more at our latest thought leadership in partnership with @hashdag
coindesk.com/sponsored-conte…
Embsio 𐤊 retweeted
Crypto gave individuals sovereignty. Staghunt is betting the next frontier is the group version: coordination markets.
Read more at our latest thought leadership in partnership with @hashdag
coindesk.com/sponsored-conte…
🤝 Paid partnership
Embsio 𐤊 retweeted
Wow this is amazing. I just joined. Have you?
I spun up Kas-Smiths, a space for Kaspa ecosystem coordination.
Ethereum-Magicians is the website for that on Ethereum.
We build with Silver, on top of proof-of-work. This feels very physical to me, so I see us more as hardworking smiths.
Kas-Smiths is meant to be the workshop where we gather to forge standards and protocols on top of Kaspa, supporting the development of tools, wallets, and applications.
I posted the first thread there, a draft of fungible-token-covenant specification, continuing the discussion from the R&D TG group.
I invite everyone to join, discuss, ask questions, criticize, and help shape the metals.
Embsio 𐤊 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.
>>


























