Rancho Sante Fe
Joined June 2020
patuxent.kas 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
127
8
435
9,703
patuxent.kas retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending github.com/kaspanet/kips/blo…
38
184
17
512
23,374
🐢 Full shell. Full speed. Real Bitcoin on $KAS
“Like a turtle, we carry all of our protection measures on our back, but that doesn’t prevent us from doing 10 or 100 blocks per second.” @hashdag on Bitcoin Takeover S17 E36
1
8
31
379
you don’t need them for an initial stablecoin. nothing prevents a smaller issuer from jumping in, at least as a warm-up/“poc” phase
1
12
92
1,518
Replying to @frank_r2d2
KCC-20 makes stablecoins a practical reality on Kaspa, yes
24
206
25
695
20,209
everything you mentioned is possible. burn and mint are easy; freeze can be implemented in various ways, with different tradeoffs. dexs and lending platforms are possible as well, though good designs require real effort and expertise. the main ingredient enabling the more compositional apps like dexs and lending is single-transaction atomicity, which allows onchain composability. these are exactly the kinds of design patterns Argent is trying to establish, and that the various KCCs are being designed with in mind
5
78
311
3,974
patuxent.kas retweeted
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.
31
145
29
423
29,144
patuxent.kas retweeted
shitcoin.watch uses sophisticated rating methodology to rank tokens based on merits and red flags. Check where $KAS is.
16
110
5
434
14,865
patuxent.kas retweeted
I’ve now launched the Kaspa Privacy Initiative. It’s an independent, community-led effort to explore optional privacy for native KAS. And judging by the response to my previous post, there’s clearly a lot of interest in making this happen. I’m not a cryptographer or Kaspa core developer. My role is initiator / project steward: to get the ball moving, organize the research, bring the right people together and keep pushing toward something concrete. I also use AI extensively for research, documentation and prototyping. I think that can dramatically accelerate the work, but security-critical architecture and code will still need review from people with deep Kaspa, ZK and privacy expertise. What I felt was missing was an open place where the community could work together toward a privacy protocol for native KAS that is not built around a new token, a company or personal gain. No new token. No custodian. No predetermined architecture. We’re starting by figuring out what can already be built with Toccata, what may require vProgs, and what architecture can eventually give native KAS strong optional privacy with permissionless exits. Everything is open from day one. If you understand Kaspa, ZK, privacy systems, wallets, security or simply see flaws in our assumptions, I want you involved. GitHub 👇 github.com/olafweller/kaspa-…
I may have found my next rabbit hole: Optional privacy for native KAS. No new token. No custodian. Just exploring whether a trustless shielded KAS protocol can be built on Kaspa. More soon. 👀
26
122
11
424
23,024
patuxent.kas retweeted
Replying to @GabrielNico21
I DO
2
2
2
18
2,900
patuxent.kas retweeted
gm
it's a gm to have a gm in the @Gemini discord
171
180
44
693
190,608
patuxent.kas retweeted
📣 Calling all $NACHO whales! Are you holding +500M NACHO (or close to it) and/or a large holder of Nacho Kats NFTs? Please DM @ScapeSquad to support the growth and success of our nation! 🐾 Join our dedicated #whales-chat in Discord to: - Collaborate on strategies to secure and optimize listings & partnerships. - Discuss ways to enhance liquidity and strengthen the market. - Stay informed about key project milestones and opportunities to contribute. Destiny is equally in your paws as a community member. By navigating together, we can shape an even brighter future for our beloved Kat! 🐈‍⬛ The community is our greatest strength. Together, let’s help the #NachoNation soar and drive progress in the Kaspa ecosystem.
5
27
107
3,178
After endless audits, reviews and refinement cycles, it’s finally here, ladies and gentlemen: silverscript 🩶📜
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa. This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript. I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
74
439
34
1,249
39,676
patuxent.kas retweeted
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa. This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript. I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
122
450
76
1,190
143,054
Tbh, now the Kaspians don’t look so crazy
LIQUID NETWORK DASHBOARD CONFIRMS 4000 BTC DRAIN @btcinsider__ reports hackers appear to have tricked Liquid’s functionaries into approving a transaction that looked valid to their systems but authorized a peg-out of roughly 3,998 BTC to the Bitcoin network. In other words, the hackers created a transaction that passed Liquid’s checks, causing the functionaries’ security hardware to sign off on the withdrawal. The hackers claim to be whitehats.
17
60
6
253
16,179
should we add $KAS to our wallet? trying to see if there's demand from the Kaspa community
482
271
25
1,868
68,228
patuxent.kas retweeted
Why the $NACHO pump? • Consistent raiding • Strong Discord + TG engagement • Eyes on NACHO across socials • Chads showing up every day • Momentum feeding momentum Salute the crew driving it. 🐈‍⬛ Imagine the move when more NACHO Fam joins the front lines. They are coming...
7
11
48
619
patuxent.kas retweeted
Just got some kaspa.
261
373
46
1,363
80,156
patuxent.kas retweeted
GEMINI × KASPA SILVER Join us live with @KaspaSilver for a conversation about Kaspa, the technology behind the project, and the community around it. Tomorrow @ 9am ET Be there or be square🟧
504
1,093
158
2,473
262,380
patuxent.kas retweeted
WSX News: Kaspa (@kaspaunchained) has taken a major step toward programmable Layer 1 applications following the activation of its Toccata hard fork in June 2026. The upgrade introduced native covenant programming, transaction v1, expanded introspection opcodes, and infrastructure for based ZK applications, allowing application state to be enforced directly on Kaspa’s UTXO layer. One of the more interesting pieces is the ability to run computation off-chain and return a cryptographic proof to Kaspa for verification, rather than forcing the entire computation onto the base layer. Partitioned sequencing lanes further allow ZK applications to prove activity related to their own lane instead of processing the network’s entire transaction flow. That gives Kaspa a new programming model without abandoning its UTXO architecture, opening the door to stateful applications and proof-based systems while keeping the base layer focused on verification and settlement.
55
231
14
658
25,100