
This is a private account re the amazing Kaspa cryptocurrency and related stuff. Visit @kaspaunchained for what's as close to the "official" one as possible.
Joined December 2021
- Tweets1.6K
- Following53
- Followers3.7K
- Likes3.8K
Miralib Balamar 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.
teapawt.org/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.
teapawt.org/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.
teapawt.org/supertypo_kas/status/2…
4 / research discussion
@WellerOlaf opened a public research repo to discuss what optional privacy for native KAS could look like.
teapawt.org/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-…
Miralib Balamar retweeted
Another great one is kaspa:native.
This one signaled a bottom was happening at the low, as there was a strong bullish divergence in play.
Since then: continuation with higher highs, higher lows and constant flips of the levels.
I don't think that this will stop soon, especially if this takes out the recent high, the next target for me is $0.0743.
Miralib Balamar retweeted
I'm a software in a big tech company in Switzerland, and I've working on tech more than a decade. And I can tell when a tech is solid.
If I'd measure a project by the tech superiority, fairness, and spirit of the free money movement, then nothing beats $KAS or even comes closer.
Miralib Balamar retweeted
📢 NEW LISTING: kaspa:native is now live on SolCex Spot.
Kaspa is a fair-launched proof-of-work blockDAG running at 10 blocks per second, built for fast, permissionless settlement and real-time decentralization.
◾️ Pair: KAS/USDT
◾️ Trading: Live now
Trade kaspa:native ↓
solcex.cc/en_US/trade/KAS_US…
Miralib Balamar retweeted
Get ready: Liquidity Week starts tomorrow.
Five posts on the most underrated question in Kaspa L1 DeFi -
not how much liquidity is coming,
but whether it will actually compose when it arrives.
Covenant DEXes are live on L1.
Tokens are minting.
And a handful of design choices being made right now - mostly invisibly, at token genesis - will decide whether that liquidity compounds into one deep market… or fragments into islands that can never recombine.
The arc:
Day 1 - The fragmentation problem
Day 2 - State ≠ bytecode
Day 3 - What composability actually buys you
Day 4 - LP shares vs the asset
Day 5 - The fix
Every claim will be checkable on-chain.
Verify, don’t trust.
🧵 starts tomorrow.
@ZealousSwap @KronTechnology @KaspaCom @KASperiencexyz @OriNewman @michaelsuttonil @hashdag
kaspaKaha.com
$KAS #KAS #Kaspa #KaspaDeFi #KCC20
Miralib Balamar retweeted
imo ppl waiting now eagerly for the future roadmap have no idea what toccata enabled (not implying you are)
don’t get me wrong, the day DK comes to Kaspa mainnet will be thrilling and enormous, but what can be built *now* over kas is dramatic. very dramatic.
Hey @upbitglobal why not add $KAS yet? Unmatched speed and scalability on a pure Layer 1 that users want.
@Official_Upbit #ListKaspa #Cryptocurrency
Miralib Balamar retweeted
Only about a month left until the $KAS hardfork upgrade to Toccata
With Bitcoin holding around $80k, I'm feeling decently bullish, but who knows how it'll be in a month from now
Part of me hopes for lower prices until Mainnet upgrade to hoard as much cheap tokens as possible
Miralib Balamar retweeted
Hey Mom — I’m Trending. 😂
Seriously though, community is important. Communities always win.
Miralib Balamar retweeted
The time has come for me to share what I’ve been working on ...
Introducing #HASH.
A grassroots, guerrilla marketing engine for #Kaspa, built with one goal: break out of the echo chamber and push Kaspa into the real world where it can’t be ignored.
I've spent a lot of time the past couple years doing my part to spread the message, build awareness, and be a voice in the $Kas community.
But there is still a gap between what Kaspa is and what the world sees. And I'm tired of sitting on the internet sidelines. That ends here.
I want to take Kaspa to the streets.
Over the coming weeks I’ll break down everything: what HASH is, how it works, how I plan to fund it, and how you can get involved.
Stay tuned.
Miralib Balamar retweeted
fed the Google whitepaper to Claude with the prompt:
"take a look at the Google paper, pick out the key parameters, and give me your analysis of the relative strengths, weakness and adaptability for both Bitcoin and Kaspa in table form"
there's literally no parameter for which $KAS Kaspa is not superior, security wise
the narrative for the past few years, that somehow $BTC is more secure as a POW chain, has now gone out the window in face of the quantum threat
Miralib Balamar retweeted
Kaspa Toccata Hard Fork:
Kaspa is about to unlock native L1 programmability with covenants via extended opcodes + full support for based zk apps (Groth16 + RISC Zero) on its high-throughput blockDAG. Key upgrades:
• Partitioned sequencing
• Canonical bridging
• Stateful multi-contract flows
• Proving costs that scale per app (no network-wide tax)
Timeline: April 15, 2026 → Feature freeze
June 5–20, 2026 → Mainnet activation (delayed from May 5 for sequencing stability)
Testnet validation + node upgrades rolling out now. Kaspa just went from fast money to smart money. #Kaspa #Toccata #ZK #Crypto $KAS
share like fav comment👊
Miralib Balamar retweeted
@nikitabier love it — quality > spam.
Any chance $KAS (Kaspa) could be part of the new Smart Cashtags rollout? Top 100 coin w/ a huge organic community. Founder @hashdag even went viral turning down @binance “top 100” spot 😅
teapawt.org/hashdag/status/1986497…
Replying to @binance
@binance,
Thanks for including me in the top 100 blockchain people list, appreciate the signal!
I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out.
Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed.
There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <<Binance should hold a privilege policy for the latter.>> A TBTF CEX should know better and play a different game with hardcore crypto projects.
When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement.
You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog?
Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point.
@cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity.
Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto.
We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes.
Please fix this.
Thanks again,
hashdag
cc @michaelsuttonil
Exhibit A: Binance Innovation Zone
Exhibit B: 10 bps Nakamoto Consensus
Miralib Balamar retweeted
Make this post go viral.
Delete your Binance account. #CZBinance is anti crypto.
They are only listing crypto memes which they eventually rug.
They are ignoring real projects like $KAS
Like, Repost and comment.
Miralib Balamar retweeted
Only 20% of this list wasn't paid for by a corporation to get there .. see if you can guess who it is :)))))))
Miralib Balamar retweeted
The countdown has begun.
DagScan 2.0 is loading.
Full rebrand.
Exclusive support for Igra Labs L2.
Designed for the next era of Kaspa-based execution.
dagscan.xyz
Miralib Balamar retweeted
"This isn’t ideological. It’s economic. When the value of time explodes, the system optimizes around time."
This framing, @swicktalk is dead on: when time becomes the most expensive input, the market stops optimizing for cost and starts optimizing for speed.
But here’s the bigger signal hiding underneath it:
When an industry reaches “time is everything,” it always runs into the same bottleneck… coordination.
Not just power generation, but:
• contracting and procurement
• capacity reservation
• payment rails across jurisdictions
• machine-to-machine settlement
• audit trails and compliance
• uptime SLAs and penalty systems
• transparent accounting between dozens of parties
In other words, the AI boom is forcing the world toward real-time infrastructure, not just faster GPUs.
That’s where #Kaspa fits: real-time decentralization. When speed becomes the economy, the winners are the rails that can coordinate instantly without becoming a central choke point.
And this is exactly where #Kaspa matters:
a high-throughput, low-latency, decentralized proof-of-work settlement layer that can support real-time payments, trustless-by-design settlement, and infrastructure coordination at global scale.
AI compute is moving at machine speed.
The infrastructure stack underneath it needs to settle at machine speed too.
It is now more clear than ever, building for this future was the right play.
Well done, @hashdag , @michaelsuttonil and ¬team. And well done, @KaspaKii for pushing the long tail strategy of showing the real world Kaspa, as the needed decentralized settlement grid for data and finance.
#PoweredbyKaspa
There’s an uncomfortable truth emerging in AI infrastructure.
When a single MW of AI compute can generate eight figures of annual revenue, traditional constraints stop binding. Cost matters less. Efficiency matters less. Even emissions matter less in the short term.
What dominates is speed.
That reality is forcing decisions that would have been unthinkable a decade ago. Higher-cost power. Temporary solutions. Redundant systems. Self-generation instead of waiting for shared infrastructure.
This isn’t ideological. It’s economic. When the value of time explodes, the system optimizes around time.
AI isn’t just changing what we build. It’s changing what tradeoffs we’re willing to accept.
Miralib Balamar retweeted
there are currently 9 active scam sites targeting the $kas community (that i'm aware of)
i need your help to take them down (it's not hard - just need 10 minutes of your time)
1. go to seedbuster.xyz
2. click report on one of the entries
3. in the help take down this scam section, click on 'view instructions' and follow the steps
4. click 'i reported this' once complete
5. share this post
you don't need to complete all reports but would be amazing if you did
if you think of any way to improve this/ seedbuster please let me know!
together we can take down these scammers
Miralib Balamar retweeted
Please tag me on any quality questions re vprogs and I’ll do my best to eventually answer and disseminate quality information
The vision is that a vprogs node (call it L2, L1.5, or an L1-node plugin) chooses which vprogs to be stateful on. You launch the software and tell it “I want to follow the state of vprogs A and B”. It then communicates via P2P to sync that state (verified against L1 commitments). Once synced, you can track its execution using only L1 data (the sovereign liveness guarantee in the yellowpaper).
That’s the technical description.
On a conceptual level, this creates an economic incentive environment. If App A depends on App B, strong stakeholders of A will naturally choose to be stateful on B as well. They don’t do this because the protocol forces them to execution-wise, but to ensure B remains live and available for composition.
This aligns with the yellowpaper’s definition of sovereignty, effectively distinguishing between the two dimensions: execution-wise, you are sovereign and technically only track your app; incentive-wise, you voluntarily track dependencies to ensure liveness for your users




































