https://xitter.cf/t.co/V8OI4h6ZV4 https://xitter.cf/t.co/ORxslOAj8f

Joined August 2016
Six days since bridging reopened on 12 Oct vs the six days before: - Active wallets +16% - First-time wallets 77, up from 32 - Transactions (excl. attestations) +50%
Hyperlane bridge is back! All 10 asset routes are open again: iKAS, USDC, USDT, WETH, cbBTC, SOL, TIBBIR, USDS, USDe and wstETH. nexus.hyperlane.xyz/ Igra’s Hyperlane routes have reopened after a pause that began on 20 September. All routes now include an Igra-side check that screens outbound transfers against an on-chain registry of incident-linked addresses. Transfers from listed addresses are blocked on these routes. This does not freeze token balances on Igra. Ordinary on-chain transfers remain unaffected. The screening check was added by the route owners. Hyperlane’s role in the routes is otherwise unchanged. Big thanks to the Hyperlane team for their responsiveness, hands-on help and support throughout. Thank you for your patience and understanding. Our priority throughout the response has been to restore access and get things moving again on Igra, with stronger safeguards. For questions about a flagged transfer or an incorrect listing, contact [email protected]. Happy bridging!
2
17
98
2,454
Introducing Magnetar from Microsoft Research, the first zkVM that is: (1) general-purpose (RV64), (2) post-quantum from standard hashes alone (no curves, no lattices, no Poseidon), and (3) built for recursion. Despite its conservative security, it is the fastest zkVM: 7.2–8.7 MHz on a laptop, 10–39× faster than existing zkVMs across 15 workloads! An optimized version reaches 9.5–12.8 MHz. Links in the thread below.
53
95
43
616
63,359
We made a commitment to the community. That commitment is now onchain. 118,672,498.26 ZEAL has been permanently burned across Igra and Kasplex L2. That includes the entire 24M ZEAL team allocation, the Insurance Fund allocation, and the protocol controlled Farm and Infinity Pool reserves outlined in our recovery plan. The burn exceeds the 97.43M ZEAL incident supply gap by more than 21.24M ZEAL, covering it approximately 1.22x and reducing ZEAL’s maximum supply from 240M to 218.75M. There is no future team unlock from the burned allocation and no future inflation from the Farm and Infinity Pool reserves we removed. The incident did not originate from ZealousSwap, but we chose to take responsibility for how we respond to it. All six transactions are public and will be shared in the reply. 💜
10
39
5
142
5,644
Replying to @UnknownZohar
KAS
51
195
22
815
22,561
Kaspa is about to get a L1 bridge to Ethereum with no signers, approvers or admins anywhere in the path. Already proven on mainnet with a test token: deposit an ERC-20 into an Ethereum vault, mint a KCC-20 on Kaspa from a ZK proof of Ethereum’s own consensus.
15
90
6
358
9,865
Ruben retweeted
Kaspa's Toccata hard fork is live on mainnet, adding native layer 1 covenant programming and zero-knowledge proof verification to the proof-of-work chain. @kaspaunchained
7
87
3
398
6,044
I finally wrote a book that covers vprogs, and in particular tic-tac-toe implemented as a vprog on testnet-10. It follows the game down to the machinery underneath, with diagrams and appendices for the details. Welcome to explore it and ask questions: biryukovmaxim.github.io/vpro…
14
158
18
442
28,278
if a dev says their covenant was audited, you should be able to check that they deployed the code people reviewed. argent’s covenant genesis proofs let people check a covenant’s original code and setup against its on-chain ID. the goal is for explorers to show these proofs, so people can inspect what they’re trusting their KAS to.
12
97
3
441
15,095
JUST IN: Kaspa Network crosses 2.4 billion total transactions The network has now processed 2.418 billion transactions just months after the Toccata hardfork went live.
22
170
10
771
19,367
Ruben retweeted
Tokenized stocks are coming on Kaskad with @RobinhoodApp ! Supply NVDA or TSLA -> Borrow USDG KSKD will naturally be supported on both chains (@Igra_Labs + Robinhood) More supported assets to come. Get ready for this month!
30
76
17
308
16,954
toccata added a native ZK proof verifier to kaspa’s L1. an app can do expensive calculations off-chain, then submit a proof that it followed the programmed rules. a covenant checks the proof and makes sure the transaction applies the proven result. kaspa calls this inline ZK.
15
161
5
688
19,839
Vitalik’s new “cryptographic world computer” thesis makes an important point that extends far beyond Ethereum: the future of blockchain probably isn’t putting more computation directly on-chain. It is separating ordering, execution and verification so each can happen where it makes the most sense. That is where Kaspa starts becoming extremely interesting. Kaspa does not need to become a giant replicated computer where every node executes every application instruction. Its more natural role may be providing the decentralized ordering and settlement substrate underneath an enormous amount of computation happening elsewhere. Toccata already pushes Kaspa in this direction. Covenants allow UTXOs to become persistent state machines. Covenant IDs preserve application lineage. Silverscript makes those transitions programmable. Argent is exploring how independently stateful actors can interact atomically. And vProgs takes the architecture further: applications can submit operations into Kaspa’s ordered environment, execute computation outside consensus, generate cryptographic proofs, and ultimately settle verified state transitions back to L1. The distinction matters. Instead of forcing the entire world computer into consensus, Kaspa can make consensus responsible for the things decentralized consensus is uniquely valuable for: ordering, timestamping, ownership, state commitments and final settlement. Computation can then become massively parallel. Different applications can maintain different state domains. Independent UTXOs can progress simultaneously. Expensive execution can happen off-chain. Proofs compress that computation into something L1 can verify. The emerging architecture looks less like “Kaspa with smart contracts” and more like a cryptographic coordination fabric. Ethereum appears to be moving away from the original idea of the blockchain executing everything toward a system that orders, verifies and settles increasingly external computation. Kaspa may be approaching the same destination from the opposite direction: starting with an extremely fast decentralized PoW clock, then progressively attaching programmable state and verifiable computation around it. The world computer may ultimately be less of a computer than a world-scale system for proving who did what, in what order, and whether the resulting state is valid.
5
67
6
180
4,832
KAS's 24-hour trading volume surges 145% day over day. kaspa:native is up ~11% today and ~20% this week, outpacing the broader market.
10
115
7
452
16,859
i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1. i stand corrected.
52
129
12
625
26,574
$NACHO and $ZEAL are crazy cheap right now on Igra. #Kaspa community sleeping
2
97
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 [email protected] within 72 hours of this transaction's block timestamp to coordinate the return."
13
39
7
116
16,912
Ruben retweeted
Replying to @Kaspa_HypeMan
The details add up. And the work doesn't stop. 🫡
12
46
7
302
11,515
Ruben retweeted
After buying $KAS back in 2022 I finally bought again
There are going to be people in two years who cannot believe they did not own $KAS at $0.035. The same way there are people right now who cannot believe they did not own it at $0.001. The story does not change. Only the price of the lesson does. Do you own some?
20
56
5
402
20,387
Ruben retweeted
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.)
Replying to @Igra_Labs
@Igra_Labs I get that you need to make money but charging almost $100 to swap $670 Ikas for USDC isn't the future of finance , that's highway robbery, with more people than ever before being able to create tokens and defi websites, something or someone will be competing with you on this soon
3
8
50
2,310
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-…
17
162
6
515
40,890