KASPA OG / TIBBIR OG
Joined September 2026
- Tweets468
- Following55
- Followers512
- Likes927
We need KYA.
$TIBBIR
You might just want to stay offline for the next few days, BTW.
These newly discovered PHP vulnerabilities are no joke.
PHP powers about 70% of the global internet, and these are 'critical vulnerabilities'.
Expect massive data breaches, website outages, malware, and remote hacks of 'smart appliances'. Your passwords, personal info, credit card details, and emails are vulnerable.
Credit where credit is due.
@Altcoinist will go in the #crypto history books on his $TIBBIR conviction call.
Well done sir. Well fkin done!
MSJ 2.0 retweeted
Kaspa's KCC-20 token standard, built on the layer 1 covenants added by the Toccata hard fork, has entered last call, its final public review stage. Its reference implementation is merged and open for developers to test.
@kaspaunchained
Had a really interesting conversation with Kaspa core developer @michaelsuttonil about the Kaspa Privacy Initiative today.
We discussed our candidate architecture for a scalable shielded native KAS protocol, using covenants, ZK proofs, permissionless relayers and batchers.
One of the biggest takeaways was how much of the infrastructure we're looking for may already be available through Kaspa's Based Apps and KIP-21.
In our original design, one of the challenges was ensuring that batchers couldn't selectively omit user operations while claiming to have processed a complete batch.
With Based Apps, user operations can be ordered directly on Kaspa L1 in an application-specific lane. KIP-21 provides cryptographic sequencing commitments, allowing a properly designed settlement proof to demonstrate that the relevant operations were processed correctly.
That could remove a substantial amount of custom infrastructure we'd otherwise have to build ourselves.
We also discussed canonical bridges, recursive proving and why sharding may introduce unnecessary complexity at this stage.
Our next step is a small Based App feasibility PoC on TN10.
We'll test lane ordering, execution, proof-based settlement, deliberate transaction omission and independent reconstruction before adding the actual shielded privacy logic.
No architecture has been finalized. The goal remains to find the safest, most scalable and most decentralized solution, not to defend an earlier design.
Really appreciate Michael taking the time to share his insights. Conversations like these are incredibly valuable.
Technical feedback, criticism and contributions are very welcome!
github.com/olafweller/kaspa-…
$ZEC $STRK $BTC yall best start paying attention to the Proof-of -Work $KAS before it’s too late!
#Kaspa #10bps #PoW #Privacy #Crypto
Major milestone for the Kaspa Privacy Initiative! 🎉
We just demonstrated autonomous recovery of native test KAS on Kaspa L1.
After physically switching off the original computer, a second machine independently found the remaining reserve, generated a fresh ZK proof and successfully withdrew the KAS on TN10.
No intervention from the original machine. No privileged withdrawal key.
This is a major step toward something essential for private KAS: being able to recover your funds even when the original infrastructure disappears.
Not a shielded pool yet, not audited, and more A1 tests remain. But a critical piece of the foundation now works!
Built in the open:
github.com/olafweller/kaspa-…
