Tic tac tic tac In the past 10 minutes $btc produced 1 block. In the past 10 minutes $kas produced 6000 blocks. Tic tac tic tac. Don't sleep on kaspa!
17
129
430
15,425
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
We’ll be rolling out some upgrades to the Zealous Launch testnet over the next several hours, and possibly into tomorrow. Expect degraded performance, temporary downtime, and possible network resets while we work. Thanks for testing with us πŸ’œ
2
11
57
2,719
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Trading on ZealousSwap is now reopened on Kasplex L2. With the KRC 20 indexer paused and the affected bridge routes closed, we are comfortable reopening trading on the network. Igra L2 trading remains open as well. Kasplex L2 users can now resume trading normally.
7
16
49
1,796
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Gm Cult! kaspa:native
2
11
93
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
#Kaspa L1 trading, upgraded. πŸ—‘οΈ #DAGGER is the Telegram bot that puts every KCC-20 market in your chat. Buy, sell, automate, snipe, settled on-chain in ~2 seconds. KRON is live. Five more venues are running on testnet. The web Terminal is out. Everything new πŸ§΅πŸ‘‡
4
18
52
845
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
In a few days we're launching on KCC standard. Early supporters get special treatment, follow for more updates! kaspa:native
4
9
27
1,166
If you're looking for true on-chain NFTs this one is for you! No ipfs storage, 100% on kaspas blockdag. Fastest PoW network finds clean art, stay tuned! kaspa:native
In a few days we're launching on KCC standard. Early supporters get special treatment, follow for more updates! kaspa:native
2
2
11
396
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
⚠️ KRC-20 incident response update Thank you for your support and understanding. It's been encouraging to see the professionalism and coordination across the Kaspa ecosystem during a difficult few days. We're working with Swiss legal counsel on the handling of incident-linked and returned funds, including the final distribution plan. iKAS to KAS canonical exits have resumed. Under the updated settlement policy, operators will release the portion cleared by review and withhold only the amount attributed to the incident. Because of these reviews, waiting times are longer than usual. Additional hardening is planned for the Hyperlane bridge before it reopens. We'll share the implementation and reopening criteria as they are confirmed. Our priority is restoring access for legitimate users while continuing recovery efforts for those affected. With questions or comments, please reach out in DM, on Telegram t.me/IgraCommunity and Discord discord.gg/invite/igralabs.
7
24
138
6,514
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Today's 1/1 is classy! kaspa:native
2
6
254
Wasn't expecting this to happen so fast! kaspa:native
🚨 Community Update Trading on ZealousSwap is now reopened on Igra L2. The Kasplex KRC 20 indexer has been paused and the KAT Bridge routes from KRC 20 L1 to Igra and Kasplex L2 are closed, preventing additional unbacked KRC 20 supply from entering Igra. We know ZEAL supply on the L2s was inflated as a result of the incident. While this issue did not originate from ZealousSwap, we are taking responsibility for dealing with its consequences as fairly as possible. All trades that happened during and after the incident remain valid. This includes users who bought ZEAL at heavily discounted prices. We will not invalidate legitimate trades or penalize anyone for trading the market that existed at the time. With the affected route now closed, we are comfortable reopening trading on Igra L2. Kasplex L2 trading will remain paused for now while we continue working on the recovery plan.
5
42
968
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
🚨 Community Update Trading on ZealousSwap is now reopened on Igra L2. The Kasplex KRC 20 indexer has been paused and the KAT Bridge routes from KRC 20 L1 to Igra and Kasplex L2 are closed, preventing additional unbacked KRC 20 supply from entering Igra. We know ZEAL supply on the L2s was inflated as a result of the incident. While this issue did not originate from ZealousSwap, we are taking responsibility for dealing with its consequences as fairly as possible. All trades that happened during and after the incident remain valid. This includes users who bought ZEAL at heavily discounted prices. We will not invalidate legitimate trades or penalize anyone for trading the market that existed at the time. With the affected route now closed, we are comfortable reopening trading on Igra L2. Kasplex L2 trading will remain paused for now while we continue working on the recovery plan.
9
21
78
4,573
RT @Igra_Labs: ⚠️ Status update: what to do if you received unexpected iKAS on 21 September. Short version: if you received iKAS from an…
4
15
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Today's 1/1 πŸ€– Heartless but sharp! kaspa:native
1
2
11
158
Glad this is getting resolved. This was not a ZealousSwap issue. The DEX worked as designed, bad actors exploited a vulnerability in kasplex krc20 protocol. This is a Kaspa ecosystem problem, and a Kasplex network rollback is the fairest outcome. Huge thanks to everyone who’s been working nonstop for two days to fix this. Brighter days ahead. KCC standard incoming. kaspa:native
We just want to take a moment to say thank you. The amount of support, patience, and kind messages we’ve received over the last couple of days has honestly meant a lot to us. We’ve read your messages, and we’re extremely grateful to have this community behind us during such unfortunate circumstances. As we’ve already explained in our reports, ZealousSwap itself was not exploited. The issue originated from the KRC 20 indexer, but unfortunately the consequences reached our liquidity pools and affected many of you. We also want to make something clear for anyone who may not know this: the ZealousSwap protocol itself was one of the biggest liquidity providers in both the ZEAL and NACHO pools, so the protocol suffered significant losses alongside everyone else. But when it comes to the recovery plan, recovering the protocol’s own liquidity is not our priority. Our focus is on the community. We are working tirelessly on a recovery plan that is as fair as possible to everyone affected, including those who bought after the incident. There are a lot of moving pieces and we want to make sure we get this right rather than rush into a solution that creates another group of people who are treated unfairly. If recovering users means the protocol never recovers its own lost liquidity, we are prepared for that. Removing the protocol from the recovery equation also makes what we are trying to achieve significantly more realistic. We’re sorry that our community has had to go through this, even though the vulnerability itself was outside of ZealousSwap. Right now, what matters to us is what we do next. Thank you again for sticking with us. ❀️ We’ll share the recovery plan as soon as we’re confident it is the fairest path forward.
2
2
37
1,531
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
We just want to take a moment to say thank you. The amount of support, patience, and kind messages we’ve received over the last couple of days has honestly meant a lot to us. We’ve read your messages, and we’re extremely grateful to have this community behind us during such unfortunate circumstances. As we’ve already explained in our reports, ZealousSwap itself was not exploited. The issue originated from the KRC 20 indexer, but unfortunately the consequences reached our liquidity pools and affected many of you. We also want to make something clear for anyone who may not know this: the ZealousSwap protocol itself was one of the biggest liquidity providers in both the ZEAL and NACHO pools, so the protocol suffered significant losses alongside everyone else. But when it comes to the recovery plan, recovering the protocol’s own liquidity is not our priority. Our focus is on the community. We are working tirelessly on a recovery plan that is as fair as possible to everyone affected, including those who bought after the incident. There are a lot of moving pieces and we want to make sure we get this right rather than rush into a solution that creates another group of people who are treated unfairly. If recovering users means the protocol never recovers its own lost liquidity, we are prepared for that. Removing the protocol from the recovery equation also makes what we are trying to achieve significantly more realistic. We’re sorry that our community has had to go through this, even though the vulnerability itself was outside of ZealousSwap. Right now, what matters to us is what we do next. Thank you again for sticking with us. ❀️ We’ll share the recovery plan as soon as we’re confident it is the fairest path forward.
9
31
131
6,239
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
KAT Bridge thoroughly verified two pending iKAS Exit transactions that were caught in a pending state when the bridge was paused. Once confirmed the involved exit transactions had zero relation to the attacker, the txns were released. The KAS/iKAS route is now returned to healthy balanced state, a rebalance to L1 was submitted to Igra although the bridge remains and will remain Paused for all routes. For KAS/iKAS bridging use the Canonical route described by @Igra_Labs below. Reminder: We strongly recommend NOT transferring, buying/selling, or otherwise interacting with KRC20 tokens on any network layer.
Status update: Canonical iKAS -> KAS exits have resumed and are operating normally. Pre-incident exits have been processed; the attacker’s exit requests remain blocked. We recommend you do not bridge, buy or add liquidity in any KRC-20 token on Igra until the indexer fix is confirmed.
4
25
1,805
In case the attacker sees this post: We ask you to send the stolen funds, the clock is ticking but one thing is for sure, kyc on exchanges never lies. Chose your path kaspa:native
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."
13
308
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Today's 1/1 "Be like water" (Bruce Lee). kaspa:native
4
15
224
𝔽𝕦𝕝𝕝𝔽𝕒𝕔𝕖.π•œπ•’π•€ 𐀊 retweeted
Lock in. For The Cult-ure! kaspa:native
Been working on this collection for a long time, months of work. Every trait is handmade, no shortcuts, just love and real passion for NFT culture. 1,111 NFTs 11 unique 1/1s You’ll find the elements, weapons, traditions, and sci-fi outfits. Lock in. kaspa:native
2
2
13
373