We are proud to announce that we as #Kaspa community are a Silver Sponsor of the UK AI Agent Hackathon by the Imperial College London.
This is organized by Imperial Blockchain & Fintech Society and Imperial AI Group.
We will find ourselves amongst good company like @Microsoft , @OpenAI , @bittensor and @AskVenice.
A big thank you to all who contributed to the fundraiser to help make this possible! This is an effort of all of us combined. Contributions are still possible for those who want to help: https://t.co/5ho8FylkLE
Stay tuned for more information that we will be releasing both today and over the next few days.
We are working hard to get $KAS the awareness it deserves!
Ps. please like and retweet and comment to the original post of @iclblockchain as well!
The Architectural Edge: Why Kaspa Outpaces Ethereum for DEX Infrastructure
Building a Decentralized Exchange (DEX) on a traditional single-chain blockchain like Ethereum is like trying to run a high-frequency trading firm on a narrow, one-lane highway. While Ethereum pioneered automated market makers (AMMs), its sequential design forces every transaction to wait in a single queue.
Kaspa’s BlockDAG architecture—complemented by the Toccata hard fork—rebuilds the Layer 1 foundation to handle the intensive demands of decentralized trading natively. Kaspa offers several architectural advantages that make it a superior backbone for a modern DEX compared to Ethereum.
Parallel Processing vs. Sequential Bottlenecks
Ethereum processes transactions sequentially. One block is added at a time, roughly every 12 seconds. When thousands of traders rush to swap assets during market volatility, the network bottlenecks, causing a massive surge in gas fees.
Kaspa replaces the single blockchain with a Directed Acyclic Graph (**BlockDAG**). Using the GHOSTDAG protocol, the network processes multiple blocks **in parallel** simultaneously (~10 blocks per second on mainnet). For a DEX, this means transactions don’t get jammed in a single queue; trades are woven together concurrently without degrading network performance.
Structural Defense Against Predatory MEV
Because Ethereum relies on a public mempool where a single block producer dictates the exact sequential order of transactions every 12 seconds, **Maximal Extractable Value (MEV)** bots thrive. They spot a pending trade and "sandwich" the user—buying right before them and selling right after—forcing the trader to execute at a worse price.
Kaspa's Advantage: Real-time decentralization dismantles the mechanics of MEV bots. With Kaspa producing blocks at a rapid-fire pace, there is no single consensus leader holding a monopoly over transaction ordering for long intervals. Rapid parallel block creation and real-time sequencing make it virtually impossible for bots to accurately predict the state and insert predatory sandwich attacks. Traders get the exact execution price they expect.
Sub-Second Latency (CEX Speed, DEX Security)
Waiting 12 seconds for a block—and minutes for true finality—is a lifetime in live trading. While Layer 2 rollups speed up execution, they fragment liquidity, introduce bridge vulnerabilities, and complicate the user experience.
Driven by the Rusty Kaspa engine, the network features sub-second block times. After just 10 seconds, a trade has accumulated roughly 10 layers of confirmation deep within the DAG structure. A DEX on Kaspa delivers the instant, responsive user experience of a Centralized Exchange (CEX) while settling entirely on an ultra-secure, decentralized Layer 1.
.
Predictable, Sub-Cent Transaction Fees
High traffic turns Ethereum into a playground for whales, where a simple token swap can easily cost $20 to $100+ in gas fees.
Because Kaspa scales horizontally at the base layer rather than relying on vertical scaling, the throughput handles massive volume natively. Transaction fees remain consistently sub-cent (<$0.01), making micro-swaps and algorithmic high-frequency trading economically viable for retail users.
My logic is different.
If the market can assign a trillion-dollar valuation to a digital asset that primarily serves as a store of value…
Then how much could infrastructure be worth that:
operates 24/7
runs 365 days a year
settles transactions in seconds
enables programmability
supports stablecoins
powers AI agents
facilitates financial coordination
serves as the global internet of money
👀
That’s a legitimate question. ⚡🚀🍻
since many (~4) asked me about the zcash bug - - - earlier this year I had this convo with a zcash core dev:
zk: it's weird that kaspa is pruning past records
me: why does it need to keep 'em?
zk: the whole point of ledgers is to prove correctness of all state transitions
me: the whole point of ledgers is to provide focal points for the consensus state
zk: the whole point...
me: hmm then why did you come work in zcash? you know the Sprout->Sapling counterfeiting bug
zk: Turnstile guarantees that the counterfeit could have been very limited
me: true but you still cannot prove or even reason about correct state transitions besides the total supply cap
zk: that's actually a good point
----
the most hardcore cryptography coin is shifting away from correctness proofs to practical-enough proofs. I believe this is a step in the right+practical direction, yet the paradigm shift should not go unnoticed - -cryptography is giving way to consensus.
if you came to zcash for cryptographic integrity, reconsider. there are many good reasons to root for zcash prospering. zcash is serving a more important role than bitcoin, whose utility for the original mission is by now blurry. cryptographic integrity is/should not be one of those reasons.
----
BTW the bug should definitely have been exploited. I don't know the personal values of Taylor Hornby, and I shouldn't be required to make the effort to learn them. I only know that if I found such an exploit, it wouldn't take me more than a few minutes to tempt myself into printing a longint amount of ZEC and deciding later what to do with it.
I wouldn't necessarily use it to exit the pool immediately and corrupt the supply, I'd wait to see if some portion of the broken pool does not seem to migrate on time (probably lost funds), in which case I would not think twice before claiming the funds myself.
you could argue that no harm done, and you might be right, but then again you are here -- in zcash / in crypto -- for its consensus dynamics, the ability to coordinate interests and convictions across different trust zones around some shared asset; not for some pristine mathematical integrity.
I’m super excited for Toccata.
It could open the door to a whole new generation of Kaspa products: real-time, permissionless financial apps that are cheap enough to use at scale.
I updated https://t.co/oH0cCaHY0c to celebrate. Go on a Toccata-style easter egg hunt while learning how Kaspa works. Visit the site and let me know what you think!
Cheers to everyone celebrating this, especially the devs involved:
@michaelsuttonil@OriNewman@IzioDev@Max143672@coderofstuff_ and others.
The L1 he’s hinting at was built to make VCs and seed investors rich.
The L1 actually built for instant, decentralized, censorship‑resistant AI micro‑tx is kaspa:native.