saefstroem retweeted
i’ll do everything in my power on the technical side to help this initiative move forward and navigate any protocol-level obstacles along the way.
on a personal note, Alex has a rare mix of technical depth, bizdev talent and deep Kaspa knowledge. i honestly can’t think of anyone better suited to lead it, and i really appreciate him taking this on
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
I think in the next few months we will see the most crucial moment for $KAS, when it comes to adoption. Let's work together, for real utility.
$KAS, did I hear you want stablecoins?
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
saefstroem retweeted
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.
We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.
Come build with us.
PR #31 (KCC-20 Last Call advancement) was merged on October 7, 2026 at 20:38:09 UTC. 14 days from that is October 21.
KCC-20 is final on October 21.
Quick clarification on KCC-20 timing 👇
PR #31 moved KCC-20 to Last Call on 7 Oct, but the header has no Last-Call-Deadline. On a 14-day count that's ~21 Oct.
A few questions please:
1.Is 21 Oct the intended end of the review window, or is a deadline still to be set?
2.KCC-1 and KCC-2 went Last Call on 1 Oct — do all three move to Final together, or does KCC-20 wait on those two?
3.Is the argent-lang reference impl + merged vectors considered to satisfy the KCC-0 §4.2 "public implementation" requirement?
Asking so builders know when it's safe to ship against KCC-20 as Final rather than Last Call. Appreciate the work on this 🙏
@manyfest_ @michaelsuttonil
@IzioDev
@asaefstroem
If anyone is still trying to get into local AI inference, this is the time. V100’s are about to get much more expensive.
So many people complain about crypto changing into a gambling sector. Even I do. I’ve sometimes considered leaving industry because of how tiring the narratives are. Depressing to build extremely complex technology just for it to be used by a memecoin.
But then I remember the fundamentals.
And that is that knowing what I know, I could never trust a bank again.
Crypto is still the hardest money. It’s easy to get lost in the noise sometimes. So we have to remind each other, about why we are here, in the first place.
saefstroem retweeted
The biggest concern with agentic wallets is always the same: "what if it hallucinates?" or "how can you ensure it doesn't interact with malicious contracts?".
This is the wrong question.
The correct question is: what can the agent touch?
Our answer: almost nothing. 🧵
we out here grinding, what about you?
The KCC Coordination Forum has reached an important milestone in the standardization process. The foundational KCC-1 and KCC-2 standards have now entered Last Call.
This opens a final 14-day review period. If no major issues are identified, both standards will be finalized and considered ready for ecosystem adoption.
We encourage anyone working with these standards to review them carefully and raise any remaining concerns during this period.
Crazy to see two pools have more than 50% of the hashrate on $KAS. Miners should consider switching to other pools or go solo.
It is important to stay patient. Coming up with your own ways of doing things and disregarding the process of @kccforum contributes to nothing but ecosystem fragmentation. If you want to speed up the process, participate in the GitHub PR discussions.
The future of AI is local inference.
Today, we’re announcing Ternary Bonsai 2 27B.
Based on Qwen3.8 27B, Bonsai 2 27B is 9x smaller than its full-precision counterpart while retaining 98.2% of its aggregate benchmark performance.
Two months after the first Bonsai 27B release, the biggest change is quality. The footprint remains 5.9 GB, but the gap to full precision has narrowed materially, with particularly strong gains in agentic coding, multimodal reasoning, and long-horizon tool use.
Ternary Bonsai 2 27B is available today under Apache 2.0.
$KAS, we’re still early. I think the market was a bit ahead of its time last ATH. We are at a much more advanced stage now, and building so many things behind the scenes.
This is how we win, $KAS.
The Kaspa ecosystem has long seen fragmentation in how applications use the available primitives and interface with other ecosystem components.
Wallet connectivity is one visible example. KIP-12 attempted to establish a common approach, but did not gain broad adoption, potentially because there was no sustained coordination around its development and adoption.
The KCC Coordination Forum, initiated by @iziodev, @michaelsuttonil, @orinewman, @manyfest_, and @asaefstroem, is intended to provide that coordination. It brings together developers and stakeholders with substantial experience in the development of Kaspa and its ecosystem, and welcomes other experienced contributors who can broaden and strengthen the effort.
The forum will jointly evaluate, refine, and formalize KCC proposals submitted by the community.
Where coordination gaps exist, it will also take proactive initiative, help develop the conventions needed, and push the ecosystem toward convergence around shared standards.
Final adoption remains in the hands of the wallets, applications, and infrastructure providers responsible for implementing them, and where the KCC Coordination Forum will assist with support and implementation.
saefstroem retweeted
MORNING MOTION: GoPro is RUNNING, everything is going onchain, chatting KAS & ZEC xitter.cf/i/broadcasts/1nxeLMnme…
This is a big milestone.
Seven months since the first commit, and after an extensive review and standardization process (thanks to @manyfest_,@iziodev,@michaelsuttonil and @asaefstroem), I'm publishing a release candidate for Silverscript v1.
The last merged PR was written by @michaelsuttonil and numbered #235, which is a nice reminder to the fact that Silverscript started as my (someone235) project and is now becoming a project involving the entire Kaspa community.
You can find a link to the release candidate in the reply, and I'd love to hear the community's feedback. If we don't receive any substantial feedback, we'll release Silverscript v1 for mainnet use one week from now.
