Kaspa Silver

A vulnerability (worse_query) affecting iOS 26.7.1, 27.0.1, and 27.2 allows malicious apps to read local files from other apps, putting seed phrases, private keys, and login credentials at risk across the entire ecosystem. This is an iOS-level issue, not unique to Binance. Immediate Action Required: - Delete any apps installed from untrusted sources (such as sideloaded or manually signed IPAs). - Update iOS and all apps to the latest official versions. - If you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions. Never install unauthorized packages, and keep your software up to date.

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.

We have received reports of unauthorized transactions on some Keplr accounts created with Google or Apple login. We flagged this to the @Web3Auth team and have been working with them on the investigation since. Based on our initial assessment: if you created your Keplr wallet with a recovery phrase or a hardware wallet, you are NOT affected. If you created your Keplr account with Google or Apple login, your account may be affected. While we investigate: – Do not send new funds to that account. – Do not re-import or recreate it anywhere. – Google/Apple login is paused for now. – Trust updates only from this account. Ignore DMs or links offering “recovery”. We will share verified details and next steps here as soon as we have them.

kaspa is 5 today. if you’ve written code, run a node, mined or helped someone understand kaspa, this is your birthday too. the intern may have underestimated the catering.

⚠️ Apple... iOS 27.3 : tout ce que tu partages en « Toute personne disposant du lien » est désormais scanné par Apple. Et ce n'est plus chiffré de bout en bout. Même si tu as activé la Protection avancée des données. C'est écrit noir sur blanc sur leur page d'aide Si leur scan trouve quelque chose : contenu supprimé, compte bloqué, ton mail et ton numéro interdits de recréer un compte... et la police "si nécessaire" Pour rappel... en 2022 Apple renonçait au scan de nos photos au nom de la vie privée En 2026 ils le réintroduisent par la petite porte, sans conférence, via une page support ! Pendant que Bruxelles se décide sur Chat Control la Silicon Valley l'applique déjà toute seule. Pas besoin de loi quand l'éditeur se porte volontaire ! Bref... Tu partages un lien, eux lisent ce qu'il y a derrière 👁️

A mobile comparison test On the left is the current Discord Android client, and on the right is the new version we’re developing in Rust

Not your keys, not your coins? Apparently, it's now: Your keys, our RPC. Your coins, our permission. A scammer sends 0.0001 dust to your wallet without your consent. You didn't approve anything. You didn't interact with the scammer. You simply received an unsolicited transaction on a public blockchain. Then Phantom's compliance filter kicks in: "Your address has interacted with a flagged malicious entity. Transactions disabled." Wait. WHAT? So a random scammer can poison my wallet address with dust, trigger your automated risk detection, and suddenly I can't use your wallet interface to move my own assets? Welcome to self-custody, where you own the keys but apparently need corporate permission to use them. The blockchain didn't freeze my account. The centralized frontend did. The irony is almost too good. We built crypto to escape banks freezing our money, only to end up with fintech apps wearing a decentralization costume. If a wallet can unilaterally disable your ability to transact because some random third party sent you dust, maybe it's time to rethink what "self-custody" actually means. Not your keys, not your coins? More like: Your keys. Their rules. Their permission. Peak Web3 UX. 🤡

I got to help orchestrate an appearance by @cz_binance at Oxford Union .. he spoke very well and did not shy away from explaining the recent incident. At the champagne reception I got to speak to him and his team in person and he is a very nice and approachable guy.. We touched on the early days of $KAS and @BinanceUS Nice work @kasmedia team and @oneforonehaha to make this happen meow :)

Non of it matters if all it does is dump in value and gets manipulated easily. This applies to any cryptocurrency.