saefstroem retweeted
KaspaDollar whitepaper is now live! Please find it under the /whitepaper page on our website. Do note, that this is a working document that is subject to both internal and external review!
As part of this release we also want to talk about why KaspaDollar is not just a stablecoin and why $KAS is the only collateral possible. That is, in this post we want to go through some of the decisions that have been taken so far and the thinking behind them, because a few of them look strange from the outside until you see what they protect.
KaspaDollar is not a business. There is no planned revenue that will be extracted from the community and there is neither any developer fee. The deployed contracts will not have an admin key and no central form of control at all. Our goal is to design it into a self-sustaining system that inherits the properties of the base layer itself. Therefore, it should be considered a product designed for the people of $KAS, owned by $KAS miners, if anything.
Let’s backtrack a little bit to understand the motivations behind this.
Why do we want decentralization and why do we resist censorship? Because there are countless examples of centralized entities abusing their power in their own favor. When it comes to stablecoins we can see this concretely with freezes. A concrete example is when Circle blacklisted the Tornado Cash contracts in 2022, every depositor in those pools had their USDC frozen with them. In addition, Tether blacklisted more than a billion dollars of USDT in 2025 alone. One can argue that most of the cases are in line with a criminal investigation but what prevents a centralized issuer from freezing without proper cause? What is the point of a decentralized PoW if a centralized stablecoin captures the majority of the TVL. Some might argue that this is why we should just stick to $KAS. But $KAS comes with a volatility not every holder can accept. Many people want to offload profits or losses into a stable asset knowing that the value of $KSD will with near certainty equal the same value tomorrow.
Everyone in the Kaspa movement has their own reasons for being here, but we believe and hope that all of them are rooted in the core crypto ethos.
Kaspa is a PoW-backed L1 with capabilities that exceed any other PoW network, and it is PoW for a reason, because this is the consensus mechanism that has proven to be the most decentralized way of agreeing on chain.
Some people point out that mining hashrate on Kaspa, and on Bitcoin, is too concentrated in a handful of pools or miners. That is true, but the same is true of staking on PoS networks like Ethereum with one major difference. The difference is that PoW is actual hardware, an ASIC machine that took years and a tremendous amount of capital to develop that can do exactly one thing, mine $KAS.
Attacking a PoW network with hardware you bought means attacking the only income your hardware will ever have. A PoS attacker’s stake can be slashed only for misbehavior the protocol can prove, and voting a false price or censoring a transaction is not one of them. Therefore in a PoS system, the stake could simply be retargeted.
Now the reason why $KSD only uses $KAS for its collateral is to bind it to the success and health of the network. The price that $KSD runs on is voted by the miners themselves. So the only party that can attack $KSD is a large miner, and that miner would be doing it in public, against the asset that pays for its hardware. Therefore, the more of Kaspa’s economy settles in $KSD, the more an attack on $KSD is an attack on $KAS itself, and the reward would be in the very asset the attack is destroying.
Some have suggested that we should use gold or $ETH as collateral. If we did this, $KSD would actually become more likely to be attacked and exploited. With $ETH or gold the reward would be paid in an asset the attack does not impact. It would also mean that the collateral is no longer on Kaspa at all. Gold on Kaspa is only a claim on gold that is held by a custodian, and $ETH on Kaspa is a claim on $ETH secured by PoS.
$KAS is the only asset that exists natively on the base layer, with no issuer and no bridge in front of it. So ironically, through less diversification we get a stronger system, one that is closer to the security properties of $KAS itself.
However, we can also not ignore the fact that centralized issuance is needed for adoption. That is why KaspaDollar also creates the infrastructure that any future issuer on Kaspa will need, including centralized ones like @circle or @tether if they ever come. The biggest piece is the oracle itself, a price feed voted by the miners that any Kaspa protocol can read, whether it is a lending market or a DEX. Simply put, providing technical rails that are built and verified by the core team can have a very beneficial stamp of approval, which could make issuance and building on Kaspa less daunting.
Consider what Kaspa DeFi would look like if it were built on bridged stablecoins or on stablecoins that originate on an L2. A covenant on the base layer can have flawless security and still hold nothing more than a claim on money that lives somewhere else, with completely different security properties.
If the dollar inside it is bridged, its value depends on the bridge’s multisig. If the dollar comes from an L2, its value depends on that L2’s sequencer and the L2’s security. If the L2 has any form of centralized control, then the security of Kaspa’s DeFi inherits the security of an external system, that can be completely disjoint from the original sought properties.
Therefore, an important statement is that: the base layer implementation is only as secure as the weakest asset within the protocol. $KSD is the only dollar on Kaspa where both the collateral and the price are secured by the same miners that secure $KAS, and that is what makes it the foundation for Kaspa DeFi.
Replying to @KaspaDollar
@KaspaDollar’s oracle will power so much more than just $KSD. Think bigger.
I eagerly await people’s opinion and criticism!
Website update! So many questions and so many unknowns yet we are completely blown away by how well the fundraiser has progressed so far, and we hope that the pace will keep increasing!
A lot of feedback has been gathered, and the website now describes the proposed idea for how KaspaDollar will function as easy as possible. Most importantly, we would like to introduce our decentralized oracle design which with the help of $KAS miners, will secure the KaspaDollar stablecoin through KIP-21 sequencing commitments.
We hope that other projects will follow along and utilize miner payloads as a means of improving miner economics.
Let's build the first native PoW-backed stablecoin together!
saefstroem retweeted
Website update! So many questions and so many unknowns yet we are completely blown away by how well the fundraiser has progressed so far, and we hope that the pace will keep increasing!
A lot of feedback has been gathered, and the website now describes the proposed idea for how KaspaDollar will function as easy as possible. Most importantly, we would like to introduce our decentralized oracle design which with the help of $KAS miners, will secure the KaspaDollar stablecoin through KIP-21 sequencing commitments.
We hope that other projects will follow along and utilize miner payloads as a means of improving miner economics.
Let's build the first native PoW-backed stablecoin together!
Thank you for this tweet, @KaspaSilver. I am going to address your concerns, piece by piece.
Concern 1 & 2: "Missing whitepaper, and no R&D"
I understand your point about the missing whitepaper. This is still in progress as it needs to be written in a certain way and have the necessary proofs, statements in order to bring the value that a whitepaper does. It is totally acceptable to be wary of donating before you see a concrete spec. The reasoning behind opening the fundraiser before those are finished is primarily for brand awareness, the fundraiser progress so far has exceeded my expectations.
It is not the case that no R&D has been done earlier, in fact I have been working on the stablecoin initiative for the last 6 months already, where primarily focus has been on communicating with centralized issuers. Unfortunately, centralized issuers are resistant to deploying on Kaspa for primarily two reasons:
1. because of the lack of anticipated volume.
2. because the needed infrastructure is missing.
I, of course disagree with this statement as there can be no volume without DeFi, hence it is a chicken and egg problem. The implementation of @KaspaDollar, would therefore not be "just a stablecoin from scratch" but a:
1. fully decentralized stablecoin
2. build the needed infrastructure that centralized issuers need in order to operate
3. bring the first needed volume in order to validate Kaspa's DeFi potential that is needed for issuers to bring their assets.
Therefore, @KaspaDollar is indirectly an effort to bring USDC/USDT onchain.
Concern 3: "Decentralized stablecoins are problematic."
Decentralized stablecoins utilize a decentralized asset as collateral, this means they are backed by whatever the collateral is most usually traded against, which for now is the U.S dollar.
When it comes to regulation the situation is complex, however we can break it down:
1. Looking at EU, MiCA (Regulation (EU) 2023/1114), Recital 22 it is stated that: "where crypto-asset services are provided in a fully decentralised manner without any intermediary, they should not fall within the scope of this Regulation" and "where crypto-assets have no identifiable issuer, they should not fall within the scope of Title II, III or IV".
2. Looking at, US, GENIUS Act (signed July 18 2025), Sec. 2 defines a "payment stablecoin" as a digital asset whose issuer is obligated to convert or redeem it for a fixed amount of monetary value. In our case, @KaspaDollar has no identifiable issuer.
3. The freeze/blacklist requirement you are referring to is Sec. 4(a)(6) of the same act, and it applies to "permitted payment stablecoin issuers", i.e. centralized issuers like USDT and USDC.
4. Freeze and blacklist functions exist because a company holds USD in a bank and is a regulated entity. There is neither a bank account behind @KaspaDollar nor a company behind it. There will be no developer fees and no upgradability. This will also apply to the oracle itself.
Concern 4: "Decentralized stablecoins are hard to list on exchanges"
The current market situation says the contrary:
1. DAI/USDS is listed on Binance, Coinbase, OKX, Bybit, MEXC, Kraken etc. and has no freeze functionality. Now it is true that they have the possibility to enable this, but at its current stage it is still unfreezable yet listed on most major CEX's.
But more importantly, a CEX listing is not the goal for @KaspaDollar and having this expectation, misses the point what it is for.
DAI was not built to be traded on Binance, it existed so that Ethereum DeFi had a stable value of account that lived onchain. Following its creation, everything else was built on top of it.
On Kaspa, we have the same gap today:
1. there is no dollar on L1,
2. no stable pair for a DEX,
3. no stable asset to lend or borrow against,
4. no way to take profit without leaving the chain,
5. no reason for anyone to build any of that.
Every DeFi primitive starts with a stable unit of account, and there is not going to be one from a centralized issuer without having seen some kind of evidence that sufficient volume is to be expected. Therefore, @KaspaDollar is the first one to take on that risk.
So the order that I believe in is not: "get USDT, then DeFi". It is "create a decentralized native stablecoin, build the DeFi, show the volume, and then the issuers come".
$KAS I just want to share why I personally have not donated to KaspaDollar yet and hoping I can get some more information.
First off I think its not good to ask for funding without a whitepaper or much more guidance on how things will work. To me it appears as give us the money and then we will research and figure out how achievable the goals we want.
Secondly, I truly believe we do not have time to be spending our resources on a brand new from scratch stablecoin. To me all efforts should be spent on getting native L1 support for already established USDT and USDC stablecoins.
Third, from what I can tell the goal is to make this stablecoin trustless. This means there is no way to freeze or blacklist addresses. This is a problem. Stablecoins are backed by the dollar and typically require those features in order to prevent money laundering and follow regulation. This means that if development moves forward for this we will not see this come to life without a few years of wait time. The reason for this is because this stablecoin would not be easily listed on popular exchanges. The only way to obtain it will be via DEXs which for Kaspa as far as I am aware we do not have proper DEXs if they do exist they lack accessibility.
These are my thoughts. Please if you have more information surrounding this leave them below.
$KAS miners I have designed something very cool, for you. Soon, block rewards won’t be the only thing you will be mining.
When dealing with funds or onchain finance, the safest code is the one that was never written. Systems need to be kept as simple as humanly possible in order to understand the attack surface.
Imagine a true PoW-backed dollar. Imagine settling billions of USD in just a few seconds worldwide. Fully trustless. That’s $KAS, that’s @KaspaDollar.
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.
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. 🧵
is that a $KAS logo??










