Kwik𐤊 retweeted
Sad thing: The normal crypto investor is too impatient to understand what Kii does and is not capable of following a 18-minute video.
Good thing: All other people should get really bullish. If companies adopt this product (and the chances are high because they have to find a solution for new regulations), then Kaspa is on a whole new level and the first layer outside of the "casino crypto bubble". Also**,** Kaspa will get the first-mover advantage as a public permissionless layer 1.
Kwik𐤊 retweeted
Bitcoin had Miami.
Ethereum had DEVCON.
Now it’s Kaspa’s turn.
Introducing the Kaspa Conference: a 4-day experience bringing together builders, investors, and the $KAS community.
And we’re investing up to $1,000,000 in Kaspa startups.
Here’s what we’re building. 🧵
Kwik𐤊 retweeted
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
Kwik𐤊 retweeted
For more details, please visit kaspadollar.com
A lot of people think what makes Kaspa unique is the technology.
But the technology is really the consequence of a deeper philosophical difference.
Most crypto projects ask: How can we maximize performance without sacrificing decentralization?
Kaspa asks: How can we maximize decentralization without sacrificing performance?
That slight inversion of priorities changes everything.
It changes what the system optimizes for, which tradeoffs are acceptable, and ultimately what kind of threat model matters.
Kaspa and in particular the upcoming DAGKnight fork are built around the idea that a decentralized monetary network should remain resilient even under extreme failure scenarios like global infrastructure disruption, war, or other large-scale breakdowns.
Because fast digital coordination should not force people to choose between trusting a small group of node operators over a small group of banks.
For many applications, that distinction may not matter.
But for the applications where credible neutrality, censorship resistance, and resilience matter most, that ideological edge is the product.
Kaspa does not merely compete at the technological level.
It competes at the philosophical level and the technology is just the downstream consequence of following that philosophy to the end.
Kwik𐤊 retweeted
I’m finally ready. After six months of hard work and coding, all my companies will have fully transitioned to kaspa:native for their day-to-day transactions by December.
The decision has been made, and the work is almost complete.
Starting no later than January 1, 2027, €20 million in financial flows will be routed through kaspa:native .
A big thank you to $ESSECBusinessSchool $ESSEC and $GS $GoldmanSachs for their support.
kaspa:native $KASPA $KASPAARMY $KASPARMY $KASPIAN $CRYPTO
Kwik𐤊 retweeted
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.
Kwik𐤊 retweeted
a lot is hiding underneath the simple sentence “doing covenants in the right way”
reading around lately, i still feel like many might not fully grasp the potential of covenants done right on a high frequency network
i’d be happy to discuss the details and the possible strategic meanings in depth on the pod sometime
Kwik𐤊 retweeted
3 KCCs by @iziodev (1, 2) & @manyfest_ (20) were finalized today as DRAFT calls for convention: github.com/kaspanet/kccs
Now would be a great time to really challenge these specs and find their possible limitations and tradeoffs
Kwik𐤊 retweeted
I decided to publish a v0 of the toccata dev book nonetheless. The writing style is a bit too AI-ish for my taste, but the content, emphasis, and ideas are by yours truly.
Made a big effort to keep it 100% accurate despite the writing speed, but you (or your llm) should read it with a grain of salt and a critical eye.
Any feedback is welcome. Happy Kaspa Toccata day, and may it all go well and smoothly 🤞
docs.kaspa.org/toccata
Kwik𐤊 retweeted
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.
Kwik𐤊 retweeted
Kaspa is real-time bitcoin, solving scalability is great but not the core value prop.
Real-time bitcoin means achieving in a few seconds the same security guarantees that nakamoto consensus / bitcoin achieves after an hour; decentralizing each consensus round rather than chain quality achieved through a coarse aggregate of rounds.
A clean definition anchor for real-time decentralization (RTD): The ability to sample the honest majority in real-time.
(Note that even fast leaderless VRF-based proof-of-stake cant sample honestly bc the selected nodes get to choose the content of their blocks after they've been selected; pos=select then write, pow=write then select)
--
RTD affects: txn confirmation, censorship resistance, secure oracle finality, MEV resistance.
Eg censorship resistance, bitcoin is the most censorship resistant chain, but if 60% of the miners are censoring you (point in reference: OFAC abiding tornado censoring eth miners), your txn will pend for 30-40 minutes. For shady business payments that's not prohibitive, but for a real economy, for an asset aspiring to be at least a king of collateral even if not an MoE, this is unacceptable, esp under economic stress.
Beyond censorship, all things finance benefit tremendously from pow density, from sampling the majority in real-time in a secure and honest manner.
I wont get into MEV resistance now, but having a "conscious" stream of oracle attestations (not price oracles) finalized in real-time qualitatively upgrades the ability to encode informed risk, collateral, liquidity management, which is the lifeblood of defi.
In context of conf times, increasing from 1 to 10bps saturates the latency optimization. But for pow density we need dozens of blocks per second, with the endgame of 100 bps: Under 10bps a 37% attacker can fake the majority signal with probability 12%. With 100bps this drops to 0.3%. Today Kaspa can't accelerate to >10bps w/o harming conf times, but DAGKNIGHT will be implemented hopefully by Q3 at least on testnet, by which we will push for 25-40bps.
The cherry on top: RTD also implies netsplit resistance, as per the partial synchrony framework.
WWIII cyberwar resistance. Hypothetically speaking ofc.
(elaborated- hashdag.medium.com/in-which-…)
Zcash is private Bitcoin
Litecoin is faster Bitcoin
Kaspa is scalable Bitcoin
Decred is governance Bitcoin
Bitcoin Cash is big block Bitcoin
Ethereum is smart contract Bitcoin
Quantus is quantum resistant Bitcoin
Monero is reactionary fungible Bitcoin
“Bitcoin” is not just a ticker.
“Bitcoin” is not just one network.
Bitcoin is the name of a movement, the symbol of a revolution, and the ecash that actually changed the world.
Kwik𐤊 retweeted
instead-of-summary of new blogpost:
a few months ago I became conscious that I've been double-speaking about kaspa for a long time now: when I talk with regular people I show off kas' speed, but when I meet crypto informed folks I instinctively shift to its unique security, to dagknight's resilience under netsplits come 2026. I am talking out of both sides of my mouth and I'm barely aware of it.
if forced to choose one north star, what would that be?
then later it occurred to me that this doublespeak actually represents two sides of the same coin- partial synchrony, a consensus category describing just that- protocols that are parameterless hence fast in peace times hence slow-yet-secure when the network/internet breaks. so now I think I can go back to speaking out of both sides of my mouth, as this represents two prongs of real-timeness.
hardcore crypto recognizes defensive values- security, censorship resistance, privacy. I argue we need a new category or metric for how long it takes a chain to achieve these defensive traits. eg bitcoin achieves censorship resistance in about an hour, kaspa achieves the same level in 1-3 seconds. doesn't make sense to flatten the two traits under the same umbrella term "censorship resistance".
the limit of this metric is real-time decentralization- the ability to sample the consensus network in real time with very high granularity, and achieve all the good properties that proof-of-work gives us just in real-time. started diving into this in the post.
kaspa's north star is real-time decentralization, but did you know the north star is actually a triple? now you do
Kaspathon looking good.
200 participants+ and already a few BUIDL (in progress submissions).
There are a some stating on their Github pages they are open to welcome new teammates.
If you don't know where to start and still want to be part of the adventure, go contact them :)
Kwik𐤊 retweeted
It took some time, but it’s finally here 👀🚀
We’ve just launched $KAS rankings across 24 exchanges!
A few exchanges are still missing due to incomplete or unreliable data, but we’re actively monitoring them and will add support as soon as accurate stats are available.
Even now, this is a major step forward in data quality giving you a clear view of where $KAS really stands across different exchanges!
Explore it now: kaspa-lens.com
And yes, all KRC20 tokens now have the same detailed view 👀🔥
Kwik𐤊 retweeted
I heard that @Kaspa_KEF and @kasmediadotcom have a question for #Kaspa community: do we like @BitGo?























