watching the timeline with awe. human beings in a world of ai superintelligence. how humbling. @hashdag, crypto and defi need fundamental redesigns, i think you should be leading with more determination / visibility.

@mcuban @kevinolearytv @elonmusk @jackmallers @garyvee @GaryCardone @GrantCardone @cameron @tyler @winklevosscap @cypherpunk @Gemini Check this out! 👀

We’re investing up to $1,000,000 in Kaspa startups.

Join us, we're a bit early today. nitter.siddz.com/i/spaces/1pJdRDpZARLKW

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 the coin can also be 'tokenized' as a kcc-20. the need may not be very clear to everyone, but basically: my L1 app may want to uniformly manage kcc-20 and Kas the coin, without extra 'custom code'. @manyfest_ details one of the direct use-case. i have been convinced that designing kas-20 correctly only gives benefit with no tradeoff. is it possible to have such an atomic covenant transaction that: 1. convert Kas to kas-20 2. trade it for the Many kcc-20 token (=without adding one extra conversion step)

I like! This is a really simple and inexpensive way to significantly reduce the quantum threat to Kaspa users. Traditional addresses expose the public key controlling the funds. A sufficiently powerful quantum computer could derive the private key from that public key and steal the funds. KIP-22 proposes a simple change: instead of exposing the public key, an address commits to a cryptographic hash (a fingerprint) of the spending conditions. The public key stays hidden, and unlike elliptic-curve cryptography, strong cryptographic hashes remain highly resistant to quantum attacks. Only when we spend the funds do we reveal the necessary information for the network to verify the transaction. There is still a theoretical attack vector where an attacker could intercept a spending transaction, derive the private key, and attempt to front-run the original transaction. But since PoW relies on hashing, which is far more resistant to quantum attacks, the network should remain operational and continue confirming transactions, leaving an attacker with only a very narrow window to act. Exploiting this would require not just a quantum computer capable of breaking public-key cryptography, but one powerful enough to do this faster than the network converges. On Kaspa, that means just a few seconds. That's a much stronger "theoretical adversary," and it's unclear whether such a machine will ever exist. Personally, I doubt quantum computers will ever be able to break public-key cryptography at realistic key sizes (I suspect that Hilbert space itself is discrete and has a much coarser resolution than commonly assumed, but that's a different topic). So TL;DR: KIP-22 isn't a "complete" post-quantum solution, but it's an elegant, relatively low-cost way to significantly reduce the attack surface for quantum adversaries.

Check out @UseArtisan 👇 I was lucky enough to get in as an early beta tester and it is amazing! Visa Card, Bill Pay, 6%+ Yield, and Send Payments straight to Venmo, Paypal, CashApp, your Landlord, and even the Pool and Landscaping guys. All from a self-custodial wallet! If you're in the US, you can now live your financial life sovereignly and onchain.

🚀 Kaspa Miners Are Staying Kaspa miners earn about a third less than three weeks ago, and they have not switched off. The hash rate sits at about 379 petahash. A mining machine pays off over many… $KAS #kaspa #cryptomining Try Premium for 7 days: mybtcguy.com/CUGQLqcj

Kaspa Privacy Initiative — Development Update Following my conversation with @michaelsuttonil, we set out to test whether Kaspa's Based Apps and KIP-21 could provide the foundation for a shielded native KAS protocol. The feasibility PoC on TN10 is now complete! Across PRs #31–33, we've demonstrated: ✅ Real Kaspa L1 lane ordering ✅ Execution with cryptographic ZK proofs ✅ Proof-based settlement accepted by Kaspa ✅ Rejection of deliberately omitted operations ✅ State reconstruction and successful native KAS withdrawal after executor downtime This is a significant step forward. Rather than building our own transaction-ordering infrastructure, we can potentially build on capabilities already available in Kaspa. We've also added a new design principle in PR #34: future protocol upgrades should preserve users' access to their funds and aim to enable privacy-preserving migration between versions. Now comes the part we've been working towards: actual financial privacy. Our next milestone is a shielded payment cycle: Alice deposits native test-KAS, privately pays Bob, and Bob withdraws native test-KAS. We'll begin by designing the private notes, commitments, nullifiers and ZK proof rules needed to make that possible. The Based App PoC demonstrates technical feasibility within its tested scope. It is not yet a privacy protocol, an independently audited system or a final architecture decision. But we're moving from proving the infrastructure to building the privacy layer itself. All research remains open source. Technical feedback and contributions are welcome! github.com/olafweller/kaspa-…

Let's get Ted to chart Kaspa, $KAS! 💚 Reply to his post with the ticker and let's get his attention for some free exposure! 👇

We’re excited to see this! Great work, @kaspagrowth

Whales are loading kaspa:native like never before. It’s now or never in my opinion anon. I am degenerately bullish. The $BTC / $ZEC rotation into #KASPA has started.

Tks @NachotheKat 🫶 big hug @argonmining 🏁

Check us up 🙂 New lending platform - kaskad:native token to be deployed soon, currently available on another chain (Igra) and tradable on @MEXC

KCC-20 has officially moved to Last Call status. Developing software and developing standards are very different. Software aims to solve a specific problem. A standard aims to define a general foundation for a wide class of solutions. A special thanks to @michaelsuttonil , who was there from the start to finish , guided me in how to approach this complex craft.

👀