
if #Kaspa failed, crypto is nonsense 👊| Kaspa Badges = 𐤊
🛸
Joined December 2022
- Tweets7.5K
- Following159
- Followers4.4K
- Likes9.9K
Pinned Tweet
#Kaspa wallpaper creativity, let's build a community with positive things, drop your wallpaper creativity below ⬇️
#Kaspa is more than just what you imagine
From Us to Us 🫶
#Bitcoin #CryptoNews
#cryptocurrency
I’ve seen a few more projects that claim to be better than Kaspa. As far as I’m concerned, they’re bound to fail on their own.
There’s no other Kaspa !
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
.@KaspaSilver explains how Kaspa solves the “Blockchain Trilemma” by processing multiple blocks in parallel
“It’s not taking the traditional blockchain approach”
Yeah, Shai, it seems like your collaboration with QUAI $QUAI didn’t end as well as it did with Kaspa $KAS.
I don’t know why this pattern keeps repeating itself—is it you who’s the problem, or are they just too naive? I wish you the best for your upcoming projects.
Oh wow, ok. That's a goid example of what I mean by lack of integrity. This total lack of refrain from blusterfoully making misleading statements about topics you don't really understand.
(There are thisr who attempt to argue there's a yet-to-be-fou d theoretical barrier oto implementing quantum fault tolerance, but none have produced compelling evidence, and not for lack of trying.
I don't know if scalable universal quantum computation will ever exist. Nobody does. But the idea that an unexpected, insurmountable theoretical obstacle is lurking in the shadows is a fringe opinion that constantly loses popularity as bigger scale computations are demonstrated.
And this is just the cherry on the top of weeks of counterfactual tirades about Kaspa's scalability.
The guy had rapport with me. We had biweekly meetings for months. He never asked me anything about GHOSTDAG before starting to inject his half baked interpretation as fact.
You don't see me attack quai-network:native like that. And believe me, it's *not* because Quai is flawless. So why don't I swing back?
Because I only ever commented on other projects if I thought they were being harmfully misleading. That's why I went after projects like Kadena, Nano, Chia, Qubic, Xelis, Dynex, Saito etc. while not getting into fights with projects doing their own thing like Ergo, Iowa, Taraxa etc. Even when I disagreed with their approach, and even when tgeir founders and community pissed me off.
And I don't recognize anything malicious about Quai, so I dont tear into its flaws either. Because that would just be stepping on other people's work for clout, or because their peers pissed me off. And such conduct, in my opinion at least, lacks integrity.
Btw., and do with this information as you will. Karl is the third crypto founder I personally know who claims to have a theory that solves central problems of modern physics, despite all of the above's Ph.Ds being in TCS. I don't know what to make of it, but it *is* curious.
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Yup stay away. I shouldn't even need to explain further. Another Kaspa fork same red flags.
Replying to @Kaidul1111 @KaspaSilver
no one ever does need the kaspa copycat, thats why you really need to read the white paper, or keep on fudding, and keep missing out on gains..
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Seven months since the first commit, and after an extensive review and standardization process (thanks to @manyfest_,@iziodev,@michaelsuttonil and @asaefstroem), I'm publishing a release candidate for Silverscript v1.
The last merged PR was written by @michaelsuttonil and numbered #235, which is a nice reminder to the fact that Silverscript started as my (someone235) project and is now becoming a project involving the entire Kaspa community.
You can find a link to the release candidate in the reply, and I'd love to hear the community's feedback. If we don't receive any substantial feedback, we'll release Silverscript v1 for mainnet use one week from now.
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
WSX News: Kaspa (@kaspaunchained) has taken a major step toward programmable Layer 1 applications following the activation of its Toccata hard fork in June 2026.
The upgrade introduced native covenant programming, transaction v1, expanded introspection opcodes, and infrastructure for based ZK applications, allowing application state to be enforced directly on Kaspa’s UTXO layer.
One of the more interesting pieces is the ability to run computation off-chain and return a cryptographic proof to Kaspa for verification, rather than forcing the entire computation onto the base layer.
Partitioned sequencing lanes further allow ZK applications to prove activity related to their own lane instead of processing the network’s entire transaction flow.
That gives Kaspa a new programming model without abandoning its UTXO architecture, opening the door to stateful applications and proof-based systems while keeping the base layer focused on verification and settlement.
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
I heard Kaspa is the new Bitcoin.
Is this true? $KAS
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
I’m finishing my argent compiler sprint (proof attached) and then I’ll do my best to communicate. Thing is, I think you are not my target audience despite indeed being a very informed investor. Talk is cheap, I want you to be INFORMED through the first serious app launching natively on Kaspa L1 and making you ask yourself “wait, how the hell is this even possible on KAS L1??”
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Like our new ads? $KAS
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Account Abstraction is fully enabled on Igra.
Type-4 transactions (EIP-7702) are enabled on all RPCs with the latest Igra node release. Combined with the ERC-4337 stack already deployed, Igra now has full account abstraction support.
What you can do today:
- Batch EOA transactions. Send a single type-4 tx that delegates your EOA to Simple7702Account and combines multiple calls (approve + swap, mint + transfer, anything) into one atomic transaction. No smart account deployment needed.
- Deploy smart accounts. EntryPoint, SimpleAccountFactory, and the bundler are live on mainnet.
- Submit UserOps through community bundler. Full step-by-step guide with working code is in docs: gas estimation, signing, submission, and an error reference for common pitfalls.
- Pay gas in USDC. The ERC-20 Paymaster lets users pay gas in USDC instead of holding iKAS.
Docs: igra-labs.gitbook.io/igralab…
Please reach out with any questions, comments or support requests.
Telegram: t.me/IgraCommunity
Discord: discord.com/invite/igralabs
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Let's show @RasterlyRock, @Bitwise's Head of Research, just how strong the #Kaspa community really is!
Give him a follow!
(Screenshot posted with permission)
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
We happy to report that Igra Network has fully migrated to Kaspa Toccata with zero chain downtime. Block production and transactions stayed intact throughout.
All 35 Igra nodes and 17 attesters (including one archival node with 30-day retention) are now Toccata compatible.
59 entry transactions could not complete because the sender side was not yet Toccata ready. All 59 deposits were returned to senders in full, no funds lost.
The Toccata era starts now. 🎶
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
Covenants need receipts too.
A covenant example should show:
• transaction link
• rule description
• spend condition
• follow-up spend path
• code or decoded script where possible
A vague “covenants are live” claim can be technically true after activation without showing usable tooling.
Can an observer see what rule was enforced?
That is the bar.
$KAS #Kaspa
ᴋᴀꜱᴘᴀ ᴀʀᴍʏ 𐤊 🪖 retweeted
There is a name inside the Ethereum whitepaper that almost nobody in crypto can pronounce.
He went on to build $KAS. Here are the receipts.





























