per astra ad aspera⸮
Joined October 2023
- Tweets11.2K
- Following661
- Followers562
- Likes17.5K
Pinned Tweet
I can come up with 2 broad reasons developers migrate to build on top of a new chain:
1) high volumes
2) technological affinity
Kaspa doesn't have volume.
The crucial initial devs we need are those that appreciate Kaspa's programmability cornerstone aspect: The UTXO model.
Radical Edward retweeted
Argent compiler refactor merged.
kaspa-hashes 2.1.1 out, fixes the Windows build.
covenant_id index review, devs on paging and database limits.
lab.kaspa.news/s/BtnI3dOOb
Radical Edward retweeted
i’ll do everything in my power on the technical side to help this initiative move forward and navigate any protocol-level obstacles along the way.
on a personal note, Alex has a rare mix of technical depth, bizdev talent and deep Kaspa knowledge. i honestly can’t think of anyone better suited to lead it, and i really appreciate him taking this on
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
Radical Edward retweeted
looking for a head of growth for a prediction markets company.
looking for someone cracked who has actually built and scaled products before. ideally someone who has taken a product from zero to millions of users, figured out distribution, and built growth loops that compound.
if you've scaled something meaningful and want to help build the next big thing in prediction markets, reach out.
Radical Edward retweeted
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
Radical Edward retweeted
yup. on eth it’s called WETH--an ERC-20 wrapper for ETH. the difference is that all the backing ETH is held under one contract address, while individual WETH balances are tracked in the contract’s storage.
on kaspa, each UTXO simply holds the actual KAS together with the KAS20 state representing it 1:1. there’s no shared wrapper vault or wrapper-level contention. it’s just native KAS managed by a KAS20 contract through the common KCC-20 interface, so the design is more streamlined and there’s no real reason to add a “w”
cc @elperorr
Radical Edward retweeted
There's another world in which all of the once high flying crypto companies that raised gazillions of dollars at absurd valuations in 2021 and are now shutting down, raising soul-crushing down rounds or selling for a fraction of their previous valuation, didn't.
And because they didn't raise too much, they also didn't hire too many people, didn't try too many things, didn't blow millions on pointless conference sponsorships and side parties, and didn't have a high burn during the bear market.
Most of all, they'd have a lower cost structure and could stick around a bit longer, especially now that things are getting interesting.
This is obviously not the world we live in, and I'm not necessarily blaming anyone, though I have consistently advised companies and projects to only raise what they need, not what they can (and nobody listened).
But what's happening to companies like Fireblocks only validates my thesis that in crypto, how much money you raise is negatively correlated with success.
The fact that the money has been there in the first place reflects one of the great ironies of this industry: in the short term, the incentives are always bad.
Radical Edward retweeted
Dom, respectfully - you are full of shit and a complete LARP.
Tearing down others doesn't help your situation at ICP.
Let's go through some facts about the "Internet Computer", an completely unoriginal and uninspiring name swiped from Ethereum's world computer:
- 3,870 daily active users (lol, lmfao really)
- spent millions of dollars on terrible conference marketing to get exit liquidity in 2021-2022
- down 99.9% from all time highs
- company makes ZERO revenue
- team max extracted and contributed negative value to the industry
- the transactions on the network are clearly wash traded/bot volume and one claude prompt will get you there
You've contributed practically nothing to the industry yet got rich as f*ck, funny how that works. To be clear, and concise:
$ICP is a total shitcoin, has zero reason to exist, and this post reeks of desperation & pure jealousy.
Envy is a major sin, and you should celebrate the successes of others, rather than try to tear them down. This industry is far too small to not grow the pie.
Ask any ZK, privacy, or developer about NEAR's TEEs and confidential tech and they will tell you the same thing: it's not perfect, but it's pretty damn good for onchain privacy in 2026.
Meanwhile, ICP is still paying the worst KOLs in the industry to promote while you dump on side wallets and OTC.
Rant over. Don't fuck with NEAR.
This is craazy. I asked one of our PhD engineers to look into NEAR *Confidential* Intents wondering how they designed their system. Unredacted, word-for-word, this was his answer 😱😱😱
"Everything I found out about the privacy claims and confidential intents is so bad that it seems almost comical and I cannot believe what I am seeing. Apparently they run a completely separate instance of the protocol, which is called FAR (as an opposite to NEAR), and that has a permissioned operator set. The entire confidentiality claim seems to rest upon the fact that it is a permissioned chain and the nodes are trusted to keep things private, there doesn't seem to be any deep technology behind it and it also does not seem to be open source. The entities running the nodes are also not publicly known.
I almost feel weird writing this because it is so absurdly bad that it feels like ... I don't know ... a simulation? I know the usual level of overpromising in Web3 but this is so many levels beyond believable that it still feels unreal."
Radical Edward retweeted
🚨 THE NEXT MONETARY WAR BETWEEN U.S. and CHINA HAS ALREADY STARTED
The U.S. is betting on Digital Dollars (Stablecoins) while China is betting on physical gold.
Trump and the Treasury just admitted the quiet part out loud.
Treasury Secretary Scott Bessent: We will keep the dollar as the world’s reserve currency and will use stablecoins to do it.
Trump’s January 2025 order made dollar-backed coins official policy. The GENIUS Act locked the mechanism in: every compliant stablecoin must sit 1-for-1 on cash, T-bills, and Treasury repos.
That’s the escape hatch. America can’t print gold. It can print demand for its own debt.
How it works:
Billions of people who will never open a U.S. bank account can hold a dollar token. Every new token forces the issuer to buy short-term Treasuries.
Dollar demand gets exported on crypto rails.
The reserve currency survives even if SWIFT loses corridors because the world is still holding a claim on U.S. paper.
It’s not a gold standard. It’s a digital T-bill standard wearing a crypto costume.
Meanwhile China is doing the opposite:
The PBOC just posted its 21st straight month of gold buying. Official holdings: ~2,366 tonnes. They’re stacking metal like the clock is running out.
Hong Kong already opened the first offshore Shanghai Gold Exchange vault. The city wants 2,000+ tonnes of storage. More vaults are being scoped for Singapore, Dubai, Riyadh, Moscow. The pitch is simple: hold yuan, convert it to gold you can actually take delivery of.
That’s the old-school play.
Physical collateral.
Offshore vaults.
Yuan contracts settled in metal, not promises.
Two strategies. Same problem.
The London Metal Exchange (LME) Treasury Chief Just Quit London For The Crypto Firm “Ripple” For Tokenized Commodities on XRP Ledger As China Builds a Yuan-Gold Vault Settlement System.
That product is already live. Assetiko gold XAUa and silver XAGa on the XRP Ledger. Swap metal to native XRP on @Trensik_com without leaving the book.
The U.S. is trying to keep the dollar’s privilege by turning private coins into a global bid for Treasuries.
China is trying to leave the privilege by stacking gold and building a vault-and-settlement network that doesn’t need Washington’s permission.
One side is digitizing the debt. The other is hoarding the metal.
Watch which one the rest of the world actually trusts when the next shock hits.
Radical Edward retweeted
Ok, I put too much time & effort on this one but I'm happy with the result and I hope you guys like it. 😁
weirdtualguy.github.io/silly…
1/7 🧵
I built #SillyKuest — a free, interactive learning adventure for anyone curious about Kaspa, Silverscript & covenants.
Let's take a look. 👇
Radical Edward retweeted
Zealous Swap X v3 is now live on Igra.
It enables multihop routing across V2 and V3 liquidity, giving traders access to better routes and better quotes in a single swap.
Radical Edward retweeted
4 months ago Toccata enabled native L1 programmability.
Last month, SilverScript brought a high-level language for covenants.
Today KCC-20 finalization gives the ecosystem a shared convention for defining, deploying, interacting with, and composing fungible token assets.
There is still more work to do on indexers, tooling, and KRC-20 migration, but the pieces are coming together.
I made some interactive walkthroughs so curious interns can explore these conventions visually. They cover the Argent reference implementation, hash-chain borrowing, and KCC-23 metadata declaration.
KCC-20 spec:
github.com/kaspanet/kccs/blo…
Reference implementation:
github.com/argent-lang/kcc20…
KCC-20 walkthrough:
kcc20.manyfest.dev/
Hash-chain demo:
kcc20.manyfest.dev/hash-chai…
KCC-23 walkthrough:
kcc23.manyfest.dev/
Radical Edward retweeted
What is Kaspa? Well, keep scrolling. And scrolling. And scrolling. Hope your finger or scroll wheel survives.
kaspa.news/what-is-kaspa
Radical Edward retweeted
Everyone are welcomed to come build on Kaspa's new programmability primitives: KCC20, based ZK apps, L1 covenants!
The frontier is getting ready to take off.
Radical Edward retweeted
I like! This is a really simple and inexpensive way to significantly reduce the quantum threat to Kaspa users.
Traditional addresses expose the public key controlling the funds. A sufficiently powerful quantum computer could derive the private key from that public key and steal the funds.
KIP-22 proposes a simple change: instead of exposing the public key, an address commits to a cryptographic hash (a fingerprint) of the spending conditions. The public key stays hidden, and unlike elliptic-curve cryptography, strong cryptographic hashes remain highly resistant to quantum attacks.
Only when we spend the funds do we reveal the necessary information for the network to verify the transaction.
There is still a theoretical attack vector where an attacker could intercept a spending transaction, derive the private key, and attempt to front-run the original transaction. But since PoW relies on hashing, which is far more resistant to quantum attacks, the network should remain operational and continue confirming transactions, leaving an attacker with only a very narrow window to act.
Exploiting this would require not just a quantum computer capable of breaking public-key cryptography, but one powerful enough to do this faster than the network converges. On Kaspa, that means just a few seconds. That's a much stronger "theoretical adversary," and it's unclear whether such a machine will ever exist.
Personally, I doubt quantum computers will ever be able to break public-key cryptography at realistic key sizes (I suspect that Hilbert space itself is discrete and has a much coarser resolution than commonly assumed, but that's a different topic).
So TL;DR: KIP-22 isn't a "complete" post-quantum solution, but it's an elegant, relatively low-cost way to significantly reduce the attack surface for quantum adversaries.
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
