i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1. i stand corrected.

$NACHO and $ZEAL are crazy cheap right now on Igra. #Kaspa community sleeping

This onchain message below is an official communication from Igra Labs regarding the KRC-20 incident on 20 September. Read and verify the message: explorer.igralabs.com/tx/0x6… Full text: "To the controller of 0x1B4B7108a49F028598c5ED49B7951c80d44e7FD2 and kaspa:qzfkfuhlswdpemz6qe82squt973kjawx9jax5rn6zrln2533trp0j44cuf43u. We are contacting you regarding the KRC-20 incident of 20 September 2026. We are seeking the full return of the assets obtained through it, including the iKAS now held at 0x9cc770e5b30f8179ddca2d8dd3d73548829af546 and 0x17030b7ea819a8742f6cec5114733267f14140ab. Exchange-linked funding of this operation has been identified. Return the funds to 0xB3300fcC2F3EF3DeCdF8B1f710c21666f33Cbf18 on Igra (chain ID 38833), or contact team@igralabs.com within 72 hours of this transaction's block timestamp to coordinate the return."

The details add up. And the work doesn't stop. 🫡

After buying $KAS back in 2022 I finally bought again

Igra makes no money on bridges or swaps. What you're seeing is slippage from shallow liquidity in the WiKAS/USDC pool on Zealous, not a fee we charge. Not ideal, agreed. It's a popular route and we're working on bringing more liquidity providers in. (Dear LPs, this pool has consistent demand and very little competition for the fees. If you've been waiting for a spot where volume per unit of liquidity is high, this is it.)

i’ve spent the last few months bringing native Kaspa payments to x402. tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard. i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it. x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled. it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow. there are two payment paths: - exact for a normal one off KAS payment, with an optional KIP10 additive mode - batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere. i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know. code: github.com/elldeeone/kaspa-x… upstream x402: github.com/x402-foundation/x… docs: kaspa-x402.org TN gateway: demo.kaspa-x402.org discussion: kas-smiths.org/t/kaspa-x402-…

People keep talking about kaspa:native because it is built differently. One reason is architecture. Kaspa is a proof-of-work blockDAG, not a single-line blockchain. Parallel blocks are ordered instead of discarded. After Crescendo, the network targets 10 blocks per second. Toccata then added Layer-1 covenants and ZK verification, so spending rules can sit on the coin itself rather than only inside an application. The design starts with settlement, then adds programmability without leaving the UTXO model. That changes how value can move at proof-of-work speed. The network is expanding around: - Fast confirmation - Native covenants and vaults - UTXO-native contracts - ZK-assisted bridging - Fair-launch mining Takeaway: Two projects can both talk about speed and still rest on very different foundations. Understand how a chain works before comparing it with another one.

a lot crossed the interns feed this week. some of it even made it into the brain. too much to give everything its own post, so welcome to the first annual-weekly-might-not-happen-again dev roundup. 1 / SilverScript v1 @OriNewman released v1. lets devs write Kaspa contracts in something a human can read. his token example goes from thousands of lines of low-level code to roughly 60. fewer lines for intern to misunderstand. nitter.net/OriNewman/status/20977… 2 / Argent updated to SilverScript v1, with docs explaining how contracts work together in one transaction. github.com/argent-lang/argen… 3 / DAGKnight a new consensus protocol for Kaspa that adapts to network delays. devs merged more code this week to prepare for testnet. still in development. github.com/kaspanet/rusty-ka… 4 / KCC12 @asaefstroem submitted a proposal so apps can connect to different browser wallets the same way. less separate hookup work for devs. currently under review. github.com/kaspanet/kccs/pul… 5 / Argent/KCC20 workshop @manyfest_ posted workshop #2, showing a KCC20 borrow transfer. recording if you want to see the contracts being put together. nitter.net/manyfest_/status/20976… 6 / Python SDK new test release for devs building with Python, updated for SilverScript v1. still a release candidate, so a few things may need yelling at. github.com/kaspanet/kaspa-py… think i missed something? good, lmk

Turns out the full node can travel light: same full verification and 97% less storage. We previously said substantially lower storage would require a separate light node with different security assumptions. Well, we got one thing wrong. Our upcoming upgrade delivers that reduction to the full nodes, with full transaction verification stays intact. Igra node storage: 1TB -> 30GB. Storage growth: 150GB -> 4GB per month at current activity. Running a node and verifying Igra yourself is now practical for far more people. Node operators and attesters: details and documentation coming shortly. Decentralize the world!

Adding $KAS would, indeed, be a good idea @kii @DiiDesertEnergy @ZETAlliance

Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa. This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript. I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.

Regarding the first five months of ZealousSwap on Igra.

You can put spending rules on your funds and have Kaspa enforce them on-chain. An allowance is one example. Someone can collect a set amount after each waiting period. The remaining funds keep the same rules for the next payment. Covenants can also control how assets change hands and how an application’s state changes.

Soon you’ll be able to buy/sell Kaspa, Igra, stablecoins and many other things with a credit card. Tell your normie friends and family!

$KAS back in the billion MC category, exactly where it belongs.

$ZEC is encrypted money that still cannot scale. kaspa:native is scalable Bitcoin, that can serve any ZK app

Don’t get sidelined. $ZEC did what it supposed to do Now it’s turn for Kaspa. $KAS will rise 🚀

GEMINI × KASPA SILVER Join us live with @KaspaSilver for a conversation about Kaspa, the technology behind the project, and the community around it. Tomorrow @ 9am ET Be there or be square🟧