ashton.kas on @kasiamessaging on discord/tg I'm @argonmining volunteering at @kaspa_kat developing @enclavefi $KAS Don't Trust, Verify.

Joined January 2014
Ashton retweeted
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.
14
133
8
454
10,461
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.
My boss told me not to post this. Roast him.
1
5
366
🚀 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
1
16
1
102
2,563
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-…
9
87
8
288
21,453
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! 👇 xitter.cf/TedPillows/status/2110…
Want me to analyse a chart? Send me the ticker, and I’ll chart the 2 most-liked tickers.
1
8
47
662
We’re excited to see this! Great work, @kaspagrowth
UPDATE: 🇫🇷 Kaspa Hackathon at EPITA Paris - minimum funding reached. We’re moving forward! 🎉 Thanks to our generous contributors thus far! 💚 Help us fund the next generation of Kaspa builders. More builders → more adoption. Support & repost👇 kasmap.org
14
122
1,649
Ashton retweeted
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.
5
40
1
279
4,248
Ashton retweeted
Tks @NachotheKat 🫶 big hug @argonmining 🏁
5
22
3
113
3,563
Ashton retweeted
Replying to @AvgJoesCrypto
Check us up 🙂 New lending platform - kaskad:native token to be deployed soon, currently available on another chain (Igra) and tradable on @MEXC
1
9
1
47
1,239
Ashton retweeted
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.
28
114
12
351
15,451
👀
23
183
13
616
22,637
we have a whole new class of entrepreneurs nowadays. ppl who are passionate about technology but until now did not have enough technical intuition and understanding for actual entrepreneurship. llms on the other hand are brilliant when guided correctly, but without proper guidance lose the plot it is critical to bridge this gap and give more and more passionate ppl enough knowledge for guiding llms correctly
i’ve written about it in the past but i feel like now it would hit more ears so to speak. there are basically two categories of covenants, those that are all about the Kaspa they protect (eg vaults, timelocks, escrow etc) and those that are about the state they carry which essentially forms another mini social consensus (eg name services, native kcc20 tokens, and whatnot). one might typically call these stateful covenants but that’s not the full story instead of diving straight in, i’d like to hear from you. how do you understand the difference between the two categories, conceptually as well as what are the technical implications resulting from the differences
18
80
1
332
6,792
i’ve written about it in the past but i feel like now it would hit more ears so to speak. there are basically two categories of covenants, those that are all about the Kaspa they protect (eg vaults, timelocks, escrow etc) and those that are about the state they carry which essentially forms another mini social consensus (eg name services, native kcc20 tokens, and whatnot). one might typically call these stateful covenants but that’s not the full story instead of diving straight in, i’d like to hear from you. how do you understand the difference between the two categories, conceptually as well as what are the technical implications resulting from the differences
27
133
6
481
22,292
The clash between 4 most ruthlessly active crypto community. which one will dominate?? $kas $qubic $dog $snek
32%$kas
9%$qubic
16%$dog
43%$snek
2,577 votes • Final results
134
167
25
272
20,320
this is amazing 👏 Build on kaspa:native
Kaspa covenant 'DoorDash' demo: order food, the payment locks at checkout, and the dasher's scan at the door pays restaurant, dasher, and taxes in one transaction. No middleman.
1
5
48
733
Quick KPI update: Today we got our first live TN10 result. In simple terms: we locked native test KAS under protocol rules, and the KAS was only released after a real cryptographic proof showed that the required conditions were met. Once that reserve was spent, it could not simply be spent again. That may sound basic, but it’s an important building block for a future shielded KAS system: Kaspa L1 itself can enforce when native KAS is allowed to leave the private system. Still a very small step. No privacy protocol yet, no notes/nullifiers, no production claims. Next we’re working toward A1: authenticated state, value conservation and an independently executable exit. Everything is being built and documented in public. Have a look, challenge the assumptions, point out weak spots, or contribute if you want to help shape it 👇 github.com/olafweller/kaspa-…
5
46
3
164
2,823
Ashton retweeted
KCC-20 is progressing together with KCC-1 and KCC-2, since it builds on top of them. In addition, KCC-20 requires a published reference implementation before it can be finalized. The Argent reference implementation is being audited and tested, and we are pushing to get it ready for Last Call as well.
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.
3
44
3
144
3,056