Pinned Tweet
Website: kasware.xyz
X/Twitter: x.com/kasware_wallet
Discord: discord.gg/8FSkXrjhGT
Telegram: t.me/KasWare_Wallet
Webstore: chromewebstore.google.com/detail/kasware…
X/Twitter: x.com/kasware_wallet
Discord: discord.gg/8FSkXrjhGT
Telegram: t.me/KasWare_Wallet
Webstore: chromewebstore.google.com/detail/kasware…
46
20
113
38,870
KasWare Wallet retweeted
this week in Kaspa dev. the devs were busy. i took notes.
1 / covenant indexing
@Max143672's covenant indexing, covered last week, is now merged. @michaelsuttonil also added a new query for inspecting the transactions behind those coins. both are awaiting a node release.
github.com/kaspanet/rusty…
github.com/kaspanet/rusty…
2 / KaspaDollar
@KaspaDollar released a working whitepaper for its proposed KAS-backed stablecoin, with vaults and a price feed using miners' votes.
x.com/KaspaDollar/st…
3 / Argent
Argent now lets devs add checks when connecting contracts. for example, making sure a new trading pool is set up for the correct token contract.
github.com/argent-lang/ar…
4 / security reporters
@IzioDev shared a community funding round to reward the security reporters whose findings helped harden Rusty Kaspa v2.1.0.
x.com/IzioDev/status…
5 / kaspa-redteam
@KasperoLabs continued work on kaspa-redteam, adding tests based on real transactions and analysis of deployed contracts without the original source.
github.com/kasperolabs/ka…
1 / covenant indexing
@Max143672's covenant indexing, covered last week, is now merged. @michaelsuttonil also added a new query for inspecting the transactions behind those coins. both are awaiting a node release.
github.com/kaspanet/rusty…
github.com/kaspanet/rusty…
2 / KaspaDollar
@KaspaDollar released a working whitepaper for its proposed KAS-backed stablecoin, with vaults and a price feed using miners' votes.
x.com/KaspaDollar/st…
3 / Argent
Argent now lets devs add checks when connecting contracts. for example, making sure a new trading pool is set up for the correct token contract.
github.com/argent-lang/ar…
4 / security reporters
@IzioDev shared a community funding round to reward the security reporters whose findings helped harden Rusty Kaspa v2.1.0.
x.com/IzioDev/status…
5 / kaspa-redteam
@KasperoLabs continued work on kaspa-redteam, adding tests based on real transactions and analysis of deployed contracts without the original source.
github.com/kasperolabs/ka…
a community funding wallet has been opened to reward security reporters who contributed in the software hardening, something that should be encouraged further.
here are all the details: discord.com/channels/59915…
7
83
329
14,691
KasWare Wallet 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.
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.
52
288
740
26,807
KasWare Wallet retweeted
@KasWare_Wallet now correctly displays KCC20 token names and values. Tokens launched on @KaspaRocket and @KronTechnology can be swapped directly in the wallet!
1
6
64
1,335
KasWare Wallet retweeted
Kasseal tokens are now live in your KasWare wallet 🦭
Every KCC20 launched on Kasseal shows up by name, right next to your $KAS, and you can send them wallet-to-wallet in a few taps. @KasWare_Wallet
Every KCC20 launched on Kasseal shows up by name, right next to your $KAS, and you can send them wallet-to-wallet in a few taps. @KasWare_Wallet
5
15
52
966
KasWare Wallet retweeted
@KasWare_Wallet v0.11.2 is released! Here's how to manually update KasWare extension: nachothekat.xyz/nacho/migratio…
$NACHO KCC-20 ticker name, logo, and decimals are now fixed along with the ability to compound token UTXOs if you'd like.
More updates to come. 🐾
$NACHO KCC-20 ticker name, logo, and decimals are now fixed along with the ability to compound token UTXOs if you'd like.
More updates to come. 🐾
1
22
80
2,944
Native support for all three Kaspa naming registries in KasWare.
• .kas (app.knsdomains.org) @knsdomain
• .kaspa (kaspaname.com) @KronTechnology
• .k (dotk.name) @supertypo_kas
Resolve a name to send, and track the names you own — across Chrome extension & Telegram. #Kasware #Kaspa
• .kas (app.knsdomains.org) @knsdomain
• .kaspa (kaspaname.com) @KronTechnology
• .k (dotk.name) @supertypo_kas
Resolve a name to send, and track the names you own — across Chrome extension & Telegram. #Kasware #Kaspa
5
10
65
3,545
KasWare Wallet retweeted
🚀 KaspaRocket is LIVE on Mainnet!
Launch and trade your KCC20 tokens, built directly on Kaspa L1.
The next chapter of Kaspa starts now. 🔥
Spread the word across the Kaspa community! 🐉
Launch and trade your KCC20 tokens, built directly on Kaspa L1.
The next chapter of Kaspa starts now. 🔥
Spread the word across the Kaspa community! 🐉
21
73
257
13,989
KasWare Wallet 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.
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.
25
277
736
74,039
KasWare Wallet retweeted
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.
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
7
57
187
15,809
KasWare Wallet retweeted
Update on the KRC20 incident:
The full revert and verification processes are proceeding smoothly; based on current progress, completion will still take several days.
Once finished, the public API will be reopened, and further investigations will be conducted into the chains of transactions linked to the exploit.
The full revert and verification processes are proceeding smoothly; based on current progress, completion will still take several days.
Once finished, the public API will be reopened, and further investigations will be conducted into the chains of transactions linked to the exploit.
32
29
118
9,399
KasWare Wallet retweeted
KRC20 Incident Update:
A vulnerability in the underlying protocol has been confirmed. Code-level fixes are complete, and a hard fork will follow. A full-state revert verification must be completed prior to the hard fork; this process is expected to take 3–5 days.
Public node APIs will be disabled during this period; please do not perform any KRC20 token operations (such as transfers).
For self-hosted nodes, please wait for the release of the new "go-krc20d" version before upgrading.
A vulnerability in the underlying protocol has been confirmed. Code-level fixes are complete, and a hard fork will follow. A full-state revert verification must be completed prior to the hard fork; this process is expected to take 3–5 days.
Public node APIs will be disabled during this period; please do not perform any KRC20 token operations (such as transfers).
For self-hosted nodes, please wait for the release of the new "go-krc20d" version before upgrading.
25
21
122
16,020
KasWare Wallet retweeted
Regarding the recently discovered attacks on the KRC20 underlying protocol, we are conducting a detailed technical analysis and expect to provide further conclusions within 24 hours at the earliest.
The public API will be temporarily disabled. During this period, please suspend all KRC20-related operations (such as transfers).
The public API will be temporarily disabled. During this period, please suspend all KRC20-related operations (such as transfers).
28
27
117
18,581
KasWare Wallet retweeted
Kaspa's first native-L1 DEX has passed an independent security audit.
@krontechnology × @Hashlock_ 0 critical. 0 high. Every finding resolved.
They didn't just read the source, the compiled Kaspa script was verified byte-for-byte against the pinned compiler.
No admin keys. No bridges. Now independently verified. 🧵
kaspa:native
@krontechnology × @Hashlock_ 0 critical. 0 high. Every finding resolved.
They didn't just read the source, the compiled Kaspa script was verified byte-for-byte against the pinned compiler.
No admin keys. No bridges. Now independently verified. 🧵
kaspa:native
11
46
192
4,272
KasWare Wallet retweeted
The KRON covenant audit has begun. @Hashlock_ has the repo.
Four covenants, every entrypoint, no sampling and a reproducible build check so the audited source provably matches the deployed bytes.
#kaspa
#kcc20
Four covenants, every entrypoint, no sampling and a reproducible build check so the audited source provably matches the deployed bytes.
#kaspa
#kcc20
3
15
59
2,281
KasWare Wallet retweeted
started to record a short 10-min live-coding argent episode: a basic multi-actor ticketing app.
one hour later, episode 01 exists 😅
start here:
github.com/argent-lang/ar…
written code:
github.com/argent-lang/ar…
one hour later, episode 01 exists 😅
start here:
github.com/argent-lang/ar…
written code:
github.com/argent-lang/ar…
49
310
869
46,806
We hear you! Some users recently reported that the scroll bar disappeared when holding multiple sub-accounts. Our team has resolved this in the latest v0.9.2 release.
Thank you for your patience! Please follow this guide to update your wallet and restore full access:docs.kasware.xyz/wallet/knowled…
Thank you for your patience! Please follow this guide to update your wallet and restore full access:docs.kasware.xyz/wallet/knowled…
9
3
20
1,885
KasWare Wallet retweeted
Released Vue Kaspa v0.1.10
Cleaned up docs, fixed some bugs and introduced a new, completely optional, ConnectWallet component for you to use.
@KasWare_Wallet and @KastleWallet supported.
Cleaned up docs, fixed some bugs and introduced a new, completely optional, ConnectWallet component for you to use.
@KasWare_Wallet and @KastleWallet supported.
2
8
38
1,419
Dive into L2 network management, master the art of bridging L1 & L2, and explore the dynamic Kaspa ecosystem firsthand! 🚀
12
22
123
4,718