Pinned Tweet
🚨 Silverscript v1 is officially out! 🚨
This completes the 8 month journey that started with Toccata. We can finally write human and AI readable smart contracts on $KAS.
What used to take thousands of lines of raw opcodes for an early token mechanism can now be written in just 60 lines of code. It grew from just "CashScript with loops" into a full smart contract language handling complex, stateful contracts.
Massive step for UTXO programmability on Proof-of-Work. Silverscript is setting the foundation, and Argent is coming next to add higher layers of abstraction.
Link to the Github release: github.com/kaspanet/silversc…
L1𐤊aspa retweeted
Just messing with covenants on $KAS and I did not fully grasp that what is happening is an address is being created that is owned by no one. It simply an address that is created with hard coded rules of what occurs with the balance that exists in the address.
This address has no private key or seed phrase. (P2SH addresses) Really cool stuff that truly understanding doesn't come around until you start messing with it yourself!
L1𐤊aspa retweeted
Friendly reminder $20 $KAS is still a sub $1T market cap network...
With greater adoption, it's not THAT aggressive of a mid-long term target
The major risks I see are related to the network surviving its infancy
If #Kaspa continues shipping and attracting talent to the network, there's a reasonable chance to achieve $20 $KAS
L1𐤊aspa retweeted
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
L1𐤊aspa retweeted
I checked all 59 coins ahead of Kaspa on CoinMarketCap against shitcoin.watch.
KAS: 62 merit, 2/100 red flags. Goldcoin.
Meanwhile Kaspa is #60 by market cap on CoinMarketCap, with 9 of the 59 above it being rated as shitcoins!!
What's most interessting is that when ranked by merit minus red flags Kaspa lands at #2, behind only BTC!!! 🤯
$KAS is criminally underrated, and we are not bullish enough.
L1𐤊aspa 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.
L1𐤊aspa retweeted
Replying to @WellerOlaf
Love to hear it. A feature is nothing without an app. We should coordinate to fully get this running on KaChat so that once its complete users can instantly use it.
L1𐤊aspa retweeted
the kaspa dev roundup has reached the ‘people might notice if i skip it’ stage.
1 / Argent
@michaelsuttonil shared the first implementation of covenant genesis proofs. these let devs check a covenant’s original code and starting state against its on-chain ID.
xitter.cf/michaelsuttonil/status…
2 / KCC standards
KCC1 and KCC2 entered a 14-day last call review. they cover shared conventions for covenant data and who can authorize actions. KCC20 still needs its reference implementation reviewed before it can enter last call.
xitter.cf/kccforum/status/210599…
3 / dotK
@supertypo_kas released the dotK indexer and API as open source. devs can run their own service for looking up .k names and following registrations on Kaspa.
xitter.cf/supertypo_kas/status/2…
4 / research discussion
@WellerOlaf opened a public research repo to discuss what optional privacy for native KAS could look like.
xitter.cf/WellerOlaf/status/2106…
right. back to my other duties, whatever those are.
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-…
L1𐤊aspa 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.
Kaspa is becoming much more than just a PoW L1...
We dive into the Toccata Hardfork and examine its impact on the Kaspa ecosystem ⬇️
bsc.news/post/kaspa-toccata-…
L1𐤊aspa retweeted
JUST IN: Kaspa Network crosses 2.4 billion total transactions
The network has now processed 2.418 billion transactions just months after the Toccata hardfork went live.




























