Yo @davidgokhshtein
Down to run a space Thursday or Friday?
Been a minute and i saw you were open to hearing more about $KAS, the community is awesome.
@PoW_Odie Support #KUDOS to go to the Imperial College London!
kaspa:qrryda035xkx02l7yg7lx65ct89zk6ku2greszt475rvn80z6ydkyy9q3zl8r
There is also a big fundraiser on the Kaspa Discord in support of this effort, that is to be announced soon. (tomorrow?)
The Fundraising vote has been closed and it is accepted by a wide margin 299 vs 18!
Next and final step is the official fundraiser by the Kaspa Discord: https://t.co/NnehY5AGfi
They will offer both KAS and USD options afaik.
Once it starts, we will also post about it here on X and on our own KUDOS Discord: https://t.co/SxMVPRwrBW
Aside from the above, there is also a KUDOS wallet for direct donations that also will be used for the event at the Imperial College London.
Simple math: if the people who voted on average pitch in $85 this marketing campaign will happen in full scale. Stag hunt at its finest!
kaspa:qrryda035xkx02l7yg7lx65ct89zk6ku2greszt475rvn80z6ydkyy9q3zl8r
#Kaspa $KAS #KUDOS
KIP-21 matters because it gives Kaspa the missing commitment structure between raw blockDAG ordering and future verifiable execution. Without it, sequencing commitments behave too much like a single global stream: every accepted transaction contributes to one shared historical surface, which is fine for proving total network order, but hostile to app-local ZK proving. If a future DEX, stablecoin system, covenant market, or vProg only cares about its own state transitions, it should not be forced to carry the weight of unrelated network activity through its witness. That is the bottleneck KIP-21 cuts through.
The design partitions sequencing into lanes, where lane identity is derived from transaction subnetworks. Each active lane maintains its own recursive lane commitment through values like "lane_tip_hash" and "last_touch_blue_score". Those active lane tips are then inserted into an active-lanes sparse Merkle tree, producing a compact commitment that rolls upward into the broader sequencing commitment while still fitting inside Kaspaβs existing header commitment structure. So Kaspa keeps one global proof-of-work anchor, but the proof burden becomes local. That is the important architectural move.
This is not Ethereum-style global state. It is not βsmart contracts on Kaspaβ in the lazy EVM sense. It is closer to proof-indexed settlement: many isolated execution lanes, each proving the activity that touched it, all inheriting the same PoW-backed DAG ordering. Inactive lanes can be purged after enough blue-score time, which prevents the system from turning into permanent historical garbage collection for dead applications. The inactivity shortcut then lets proofs skip empty spans instead of walking every irrelevant block.
That makes KIP-21 one of the quietest but most important pieces of Toccata. Covenants define constrained UTXO behavior. ZK verification proves external computation. Native covenant IDs preserve lineage. KIP-21 gives all of it a scalable anchoring map. It is how Kaspa begins moving from fast money into sovereign execution infrastructure.
Kaspa Toccata mainnet process update:
Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1β2 days of broader network sanity testing.
Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today
Dear $ETH, $SOL, $SUI developers:
Why should you build on $KAS ? -
Kaspa is built to fix whatβs broken in every other chain youβre already shipping on.
Ethereum forces you into L2 fragmentation, bridges, and fees.
Solana gives speed but still fights congestion and validator centralization.
Sui is elegant, but itβs another PoS system competing in the same crowded lane.
Kaspa is different.
It runs a BlockDAG with GHOSTDAG β not a linear chain. Blocks are produced in parallel (currently 10 blocks per second). All honest work counts. No orphans. Weβve already hit real-world peaks above 5,500 TPS with sub-second to few-second finality β all on pure L1 Proof-of-Work.
That means:
β’ No L2 tax
β’ No sequencer risk
β’ No sharding complexity
β’ Bitcoin-grade security that actually
gets stronger as throughput increases
Programmability is here and getting better fast.
Right now you can deploy full EVM dApps on Kasplex or Igra Labs β Solidity + MetaMask, but settled on Kaspaβs fast, cheap, secure L1.
In the next few weeks (Toccata hard fork, June 2026), $KAS is activating native L1 covenants via SilverScript + ZK primitives directly on the DAG. Youβll get powerful on-chain logic and verifiable computation without bloating the base layer.
For builders this means:
β’ Port your existing EVM code easily today
β’ Build new apps that feel instant and cost almost nothing
β’ Ship on a chain where MEV and front-running are structurally harder
β’ Be early on the fastest, most decentralized PoW programmable platform
$KAS has solid tooling (WASM SDK, Rusty Kaspa, gRPC/REST) and a technical community that actually cares about the protocol.
If youβre tired of trading off speed for security, or security for decentralization, or decentralization for usability β stop compromising.
Build on $KAS.
The base layer finally scales. The security model is sound. The developer path is open.
The window to be early is right now.
why Iβm personally excited about Kaspaβs upcoming Toccata covenants
- for the first time, I can build creative, complex apps directly over infrastructure I helped design and build
- we designed under architectural constraints, but the result came out surprisingly expressive and powerful
- Silverscript is cool as hell
- I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1
- (nottoself: create a 10-minute video showing the building of such an app e2e)
- I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet
- covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover
- sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking)
- complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it
- as Iβve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves
- I didnβt even mention based apps yet. Thatβs a whole vertical that isnβt ready for exploration yet, but will be very soon
The suppression of Kaspa is not just a Kaspa problem. It exposes a deeper rot in the broader crypto industry: the market still pretends to be decentralized while price discovery, liquidity access, and legitimacy are filtered through centralized gatekeepers.
That matters because CEXs do not simply βlist assets.β They manufacture visibility. They decide which coins get the easy retail buy button, which coins get deep liquidity, which coins get market-maker support, which coins get institutional routing, and which coins remain fragmented across smaller venues. In theory, crypto is supposed to route around permissioned finance. In practice, most users still discover assets through the same centralized funnels.
This creates a distorted incentive system. Fair launches are punished because there is no insider allocation to distribute, no VC inventory to monetize, no foundation treasury to negotiate with, and no easy promotional machine behind the asset. Meanwhile, weaker projects with better insider economics can receive cleaner access because they fit the exchange business model better. The result is not meritocratic capital formation. It is liquidity favoritism disguised as market neutrality.
Kaspa threatens that model because it represents something crypto was originally supposed to protect: open proof-of-work issuance, no premine, no insider launch, no committee, no sequencer, no foundation-controlled float. If that kind of asset can be delayed while more centralized or venture-shaped tokens receive smoother access, the industry has to confront an ugly truth: much of cryptoβs βdecentralizationβ is downstream of centralized distribution.
The implication is bigger than price. If exchanges can suppress, delay, or derivative-wrap genuine open networks while accelerating assets with cleaner insider monetization, then crypto becomes a permissioned casino wearing cypherpunk clothing. The assets that survive anyway become more important, not less, because they prove that neutral monetary infrastructure can still emerge without begging the gatekeepers for validation.
Bitcoin was supposed to change everything.
It did. In 2009.
Now it's a 16-year-old relic running on 1 block every 10 minutes while the world burns for faster, scalable PoW.
Kaspa ships 10 blocks per SECOND.
Same UTXO model. Same proof-of-work. Zero excuses.
Bitcoin's problem isn't its enemies. It's the linear chain. One block at a time. No parallelism. No throughput. No evolution. Just vibes and laser eyes.
Bitcoiners love to call everything else a scam β but what do you call a system that deliberately stays slow and calls it a feature?
GHOSTDAG doesn't orphan blocks. It incorporates them into the DAG. Every valid block counts. Meanwhile Bitcoin throws away work like it's 2009 and bandwidth doesn't exist.
Dr. Yonatan Sompolinsky β the man who designed the architecture Bitcoin wished it had β just won Binance's Top 100 Blockchain People.
Not a VC. Not a influencer. A researcher who actually solved what Bitcoin couldn't.
10 blocks/sec vs 1 block/600 sec.
Same security model. Completely different reality.
Keep holding your digital gold.
We'll be over here building the future Bitcoin was too rigid to become.
kaspa:native bitcoin:native ripple:native ethereum:native binancecoin:native solana:So11111111111111111111111111111111111111112 tron:native dogecoin:native cardano:native
KasKad are honestly doing insanely well already and I can see why.
Extremely easy to use and extremely useful. Iβve been waiting for a borrowing and lending platform for ages because I donβt want to sell my KAS but I do want to unlock some liquidity at times and now we have it!
Awesome job @AppKaskad π₯
$KAS #Kaspa