Maro ꓘ retweeted
So what's next for KPI?
We're moving beyond our current test model toward actual private KAS payments.
The next experiment:
🔒 Alice has 10 KAS.
🔒 She privately sends 4 KAS to Bob, keeping 6 KAS in change.
🔒 Bob independently discovers his funds and proves he can withdraw 4 KAS.
All without trusting a custodian or revealing the private payment details.
We'll build and test the cryptographic privacy logic locally first, then take the complete new proof system back to the GPU.
There's still serious engineering ahead, but today genuinely feels like a milestone.
Optional privacy for native KAS. No new token. No custodians.
This is an open-source, community-driven effort. If you're excited about where this is heading, you can follow the progress or support the research at 💚 kpi.cash
Let's see how far we can take this together! 🚀
Maro ꓘ retweeted
Major breakthrough for the Kaspa Privacy Initiative! 💚🚀
Yesterday, we hit a serious bottleneck: generating our full zero-knowledge execution proof on CPU was taking far too long.
So we rented an NVIDIA L40S GPU.
And it worked!
✅ Full cryptographic proof in just 4 minutes and 16 seconds
✅ Independently verified on CPU
✅ Invalid operations correctly rejected
✅ Estimated GPU rental cost: just $0.12
For the first time, we've demonstrated that our complete test-model execution can be cryptographically proven in minutes, at a surprisingly low cost.
And that opens up some exciting possibilities. 👇
Maro ꓘ retweeted
Kaspa's network produced 8,641,144 blocks in the 10 days to Oct 12, or 863,991 a day. At that pace it would match all 971,082 blocks Bitcoin has produced since 2009 in under 27 hours.
@kaspaunchained
Maro ꓘ retweeted
Kaspa breaks 2.4 BILLION total transactions.
According to its explorer tool, the Kaspa L1 network has now processed a cumulative 2.418 billion transactions, now moving fast toward the 2.5 billion milestone.
Its Toccata Hardfork went live just a few months ago and is already having a tangible impact...
Maro ꓘ retweeted
Kaspa hashrate is up because of $KAS pumping up from bear market lows along with development and adoption on the L1.
Nothing to do with a 1 BPS vibe-coded forked coin. Even if merged mining is a temporary crutch, it is not built to compete long-term.
Privacy is always someone's choice. I will always choose to support +10 BPS KAS privacy on vProgs than inferior technology.
Build and invest in #Kaspa, long-term.
🚨 $KAS ≠ ZKAS.
Protect your Kaspa assets.
I am breaking down why you should ignore this forked coin despite its merged mining with Kaspa ASICs.
We should not waste resources on a path that fails to support our actual network. It is important to stay informed so you can distinguish legitimate developments from potential traps that could harm your holdings.
We are here to focus on the real #Kaspa ecosystem and its proven technology which only continues to upgrade. It's equally important to understand the significance of copykat coins in the crypto market. Don't trust, verify.
Full video: youtu.be/iJcEkKtedRY
*Since recording, there may be new small exchange listings rather than just OTC trading. NFA. DYOR.
Maro ꓘ retweeted
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
github.com/kaspanet/rusty-ka…
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
xitter.cf/Max143672/status/21034…
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
github.com/kaspanet/kaspa-py…
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
xitter.cf/KasperoLabs/status/210…
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
xitter.cf/manyfest_/status/21030…
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
github.com/kaspanet/kccs/pul… github.com/kaspanet/kccs/pul…
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
github.com/supertypo/simply-…
thanks to everyone building. see you next week.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined.
On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state.
On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant).
This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it.
A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information.
The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity.
After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself.
Read more on Kas-Smiths:
kas-smiths.org/t/kcc-23-conv…
Or read the KCC draft:
github.com/kaspanet/kccs/pul…
Maro ꓘ retweeted
IMO, $KAS is going to hit all time highs sooner than most people anticipate.
Don't be sidelined.
Study. Gain conviction. Allocate accordingly.
Maro ꓘ retweeted
$KAS | @kaspaunchained is making a strong push toward $0.05000.
Once $0.05 is reclaimed, $0.0700 becomes the next key level to watch.
$KAS is the most significant opportunities in crypto since $BTC and $ETH.
A next-generation PoW blockchain designed to address the scalability and decentralisation limitations of traditional PoW systems.
Behind the technology is Yonatan Sompolinsky (@hashdag), founder of DAGLabs and a key figure behind Kaspa.
Yonatan co-created the GHOST protocol with his PhD advisor, Professor Aviv Zohar, in 2013.
His research has also been referenced across numerous major crypto projects, including $ETH, $DOT, $AVAX, $MATIC, $ADA and $XMR.
The fundamentals, technology and pedigree make $KAS a project worth watching closely.
$0.05 → $0.07 → beyond ATH $0.2000
The market is preparing $KAS to break its ATH of $0.2000
$KAS | @kaspaunchained continues to push higher.
$KAS at $0.05 is coming quickly
Currently sitting around 80% below its $0.207 ATH.
$KAS is only 5x away from reclaiming those levels and I believe a new ATH is well within reach.
The ultimate PoW Layer 1.
$KAS is showing what PoW can really become:
➡️Near-instant transaction confirmation,
➡️High scalability
➡️A network architecture capable of supporting real L1 adoption.
$KAS is proving to be fast, scalable, and built for mass adoption.
The journey back to ATH is just the beginning.
