Most people still think $KAS is “just a payment coin”
But after a long exchange with @hashdag, it’s clear that payments are only the surface layer.
The real vision of Kaspa is something much bigger:
→ a native monetary protocol for the Internet itself.
Let me explain.🧵
1/10
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:
https://t.co/Hjb9Tksypu
written code:
https://t.co/qdI40DaIoX
Just deployed a useful new feature to @kaspa_stream: Per miner hashrate histories (7d retention). Hint: One pool is particulary unstable. Will look into adding some #kaspa covenant stats next ;)
This type of post is not about reaching all readers, it’s about getting to the few right ppl through broad amplification. Attention will come through well-planned apps being built by serious engineers/teams. All in all I disagree with you at least as to where I personally should focus attention, but of course other people should play other roles
New #Kaspa indexer and api releases!
These build on v2.2, which brought them up to support Tocatta.
v2.3 is mainly a performance enhancement release, which have been running on the Kaspa api for a while already. Be sure to read RN when upgrading.
Links in comment.
Now that we have programmability paths on Kaspa, the need to converge on ecosystem standards in the right way becomes paramount.
It appears we lack a fitting forum for such discussions.
A primary and timely example would be a standard specification for native assets. We need a place for technical discussions where wallet devs, explorer devs, community thinkers, and core devs can brainstorm and rapidly converge on ideas without communication gaps, and without important ideas and messages getting lost to oblivion.
As a start, here is a call for community discussion on native assets.
An initial discussion on kas pub rnd is linked below, but again, to me this feels like an echo chamber, with probably the most important voices missing.
>>
@cryptogenerian KasVault will be ready for the hf, change here is minimal and in fees only. @lAmeR_1337 to comment on Ledger Live impl.
The hardware wallet doesn’t need to be updated since txs it signs are valid even after the hf.
@Free_data0 Toccata HF lets us verify PQ signatures. So it will be possible to be ready for quantum computers by end of this month, at least on consensus side
for anyone not on Kaspa telegram:
Kaspa Python SDK releases 2.0.0 and 2.0.1 are now available.
Built wheels are available on the corresponding GitHub & PyPi releases.
v2.0.0
Built from rusty-kaspa 2.0.0. Includes full compatibility with Toccata Hardfork features, new Wallet API (via wrappers over rusty-kaspa Wallet), other small changes & supporting components.
Release (with full change log): https://t.co/CKKtgAn1HR
v2.0.1
Built from rusty-kaspa 2.0.1 and includes all pertinent changes.
Release: https://t.co/MmXHiNS4xP
PyPi: https://t.co/CouUkVj3EV
Docs: https://t.co/NLQTpGjHyT
While 2.0.1 is the latest, 2.0.0 changelog includes important notes.
Please file issues here: https://t.co/FkiETn0XOE
Tomorrow it's finally time for the first community hangout!
Kaspa Under the Hood: Setting the Stage for vProgs
Grab a beer, coffee, tea, or whatever keeps you going, and join us for the first regular Kaspa community hangout.
We will start with a high-level presentation of the upcoming vProgs architecture and Kaspa’s next stages of development. Since the architecture is extensive, this first session is meant to set the stage for future deep dives.
The presentation is meant to be accessible to people with different technical backgrounds. We will take things step by step, build up the necessary context, and gradually develop a shared understanding of Kaspa’s architecture, trade-offs, and long-term vision.
After that, we will move into a relaxed open discussion where people can ask questions, share ideas, and talk about anything interesting: Kaspa, decentralized infrastructure, incentives, technology, philosophy, or the future of humanity.
Bring your ideas and questions, grab a drink, and join the conversation!
https://t.co/dDIudhbwCG
since many (~4) asked me about the zcash bug - - - earlier this year I had this convo with a zcash core dev:
zk: it's weird that kaspa is pruning past records
me: why does it need to keep 'em?
zk: the whole point of ledgers is to prove correctness of all state transitions
me: the whole point of ledgers is to provide focal points for the consensus state
zk: the whole point...
me: hmm then why did you come work in zcash? you know the Sprout->Sapling counterfeiting bug
zk: Turnstile guarantees that the counterfeit could have been very limited
me: true but you still cannot prove or even reason about correct state transitions besides the total supply cap
zk: that's actually a good point
----
the most hardcore cryptography coin is shifting away from correctness proofs to practical-enough proofs. I believe this is a step in the right+practical direction, yet the paradigm shift should not go unnoticed - -cryptography is giving way to consensus.
if you came to zcash for cryptographic integrity, reconsider. there are many good reasons to root for zcash prospering. zcash is serving a more important role than bitcoin, whose utility for the original mission is by now blurry. cryptographic integrity is/should not be one of those reasons.
----
BTW the bug should definitely have been exploited. I don't know the personal values of Taylor Hornby, and I shouldn't be required to make the effort to learn them. I only know that if I found such an exploit, it wouldn't take me more than a few minutes to tempt myself into printing a longint amount of ZEC and deciding later what to do with it.
I wouldn't necessarily use it to exit the pool immediately and corrupt the supply, I'd wait to see if some portion of the broken pool does not seem to migrate on time (probably lost funds), in which case I would not think twice before claiming the funds myself.
you could argue that no harm done, and you might be right, but then again you are here -- in zcash / in crypto -- for its consensus dynamics, the ability to coordinate interests and convictions across different trust zones around some shared asset; not for some pristine mathematical integrity.
Hayes is a pretty sharp cat, it would be neat to see him have a gigabrain chat with @hashdag on cam sometime . . perhaps he could gain insight into whats RIGHT in crypto . . kaspa:native
SELL $ADA, BUY $KAS ! 🚀
Why hold cardano while Charles Hoskinson takes a "break" as the ecosystem crumbles and hits a 5-year low? Cancelled summits and tech failures say enough.
Stop bagholding a dying coin. Move your capital into the future of tech. Switch to $KASPA now!
The DAA “Score” is more than a score…
474,165,565
An epic score for an epic fork!
BWV 565 is Bach’s famous Toccata and Fugue in D minor, probably the most recognizable “Toccata” reference in Western music. The Netherlands Bach Society lists it as BWV 565, titled Toccata and fugue in D minor, for organ.
https://t.co/1QukpKzakn