Igra Network is MEV resilient EVM layer on top of Kaspa BlockDAG. Mainnet is live.
Berlin
- Tweets 565
- Following 110
- Followers 8,569
- Likes 1,193
Pinned Tweet
⚠️ 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.
6
24
135
5,903
Igra Labs retweeted
Fair token launches on Igra, straight from your wallet.
ZAP runs timed auctions where every bidder pays the same clearing price, designed to keep bots and frontrunners out.
Connect Zelcore over WalletConnect from the Igra screen. Every bid is approved inside Zelcore before it's signed.
1
14
41
1,633
Post updated with the link to attacker wallets: explorer.igralabs.com/accoun…
⚠️ Status update: what to do if you received unexpected iKAS on 21 September.
Short version:
if you received iKAS from any address on this list, please send it to the Igra DAO Governance contract: 0xB3300fcC2F3EF3DeCdF8B1f710c21666f33Cbf18
explorer.igralabs.com/accoun…
Long version:
The attacker behind the KRC-20 incident sent amounts of 5,000 to 10,000 iKAS to around 35 wallets that seemingly have nothing to do with the attack. This was done to make uninvolved users look connected to it.
You are not under suspicion. Anyone can send to any address and you could not have refused it. Your own funds are unaffected, and exits covered by your own balance and deposits will settle normally.
Funds originating from the attacker cannot be bridged out. The exit settlement operators settle against amounts traceable to your own deposits, so anything traced to the attacker's wallets will not be paid out.
These are stolen funds. Returning them is voluntary, takes one transaction, and costs you nothing you could otherwise use.
If you already moved or spent it, email team@igralabs.com and we'll help sort it out.
9
41
2,793
⚠️ Status update: what to do if you received unexpected iKAS on 21 September.
Short version:
if you received iKAS from any address on this list, please send it to the Igra DAO Governance contract: 0xB3300fcC2F3EF3DeCdF8B1f710c21666f33Cbf18
explorer.igralabs.com/accoun…
Long version:
The attacker behind the KRC-20 incident sent amounts of 5,000 to 10,000 iKAS to around 35 wallets that seemingly have nothing to do with the attack. This was done to make uninvolved users look connected to it.
You are not under suspicion. Anyone can send to any address and you could not have refused it. Your own funds are unaffected, and exits covered by your own balance and deposits will settle normally.
Funds originating from the attacker cannot be bridged out. The exit settlement operators settle against amounts traceable to your own deposits, so anything traced to the attacker's wallets will not be paid out.
These are stolen funds. Returning them is voluntary, takes one transaction, and costs you nothing you could otherwise use.
If you already moved or spent it, email team@igralabs.com and we'll help sort it out.
18
44
110
11,679
Igra Labs 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,789
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.
3
14
91
5,410
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
38
114
16,437
Regarding the recently discovered attacks on the KRC20 underlying protocol, we are conducting a detailed technical analysis and expect to provide further conclusions within 24 hours at the earliest.
The public API will be temporarily disabled. During this period, please suspend all KRC20-related operations (such as transfers).
25
27
113
17,053
Igra Labs retweeted
KAT Bridge KRC20, KAS/iKAS, Hyperlane Bridging has been paused and taken offline while investigation proceeds.
@KastleWallet @KaspagentAI and any other integrated products, Please disable your integrations as well
⚠️ Security notice: KRC-20 incident
An incident on offchain indexer earlier today resulted in unauthorised movement of ZEAL and NACHO out of the KRC-20 bridge custody. The custody's entire holdings of both tokens were taken, so ZEAL and NACHO on Igra and Kasplex L2 are not backed on L1.
Our current understanding is that the underlying issue affects KRC-20 accounting more broadly, not only these two tokens. We have escalated to the indexer, bridge and exchange teams.
Until they confirm a fix, treat KRC-20 balances and deposits on Igra as unconfirmed.
Paused until further notice: iKAS exits to Kaspa L1 and Hyperlane transfers. Existing balances are unaffected and nothing is lost. Both resume once the issue is confirmed resolved.
Until further notice:
- Do not bridge any KRC-20 token in either direction.
- Do not buy ZEAL or NACHO on any L2 DEX.
- Do not add liquidity to ZEAL or NACHO pools.
- Existing positions in WiKAS/ZEAL and NACHO/WiKAS, including farm positions, are impaired.
Exchanges and bridges crediting KRC-20 deposits should pause them pending confirmation from the indexer team.
Not affected on Igra: iKAS, WiKAS, IGRA, USDC, USDT, staking, LYNX, Kaskad.
ZEAL and NACHO are the only KRC-20 tokens bridged to Igra.
The Igra bridge contracts and relayers operated correctly throughout. The attacker's L2 address is 0x1B4B7108a49F028598c5ED49B7951c80d44e7FD2. Technical details will follow.
1
11
37
3,776
Igra Labs retweeted
🚨 KRC 20 Indexer Signature Bypass: Incident Report
We have completed our analysis of the KRC 20 incident that affected ZEAL and other bridged assets.
Importantly, our investigation found no exploit in ZealousSwap, Igra, or Kaspa L1. All three operated as intended. The vulnerability was in the Kasplex KRC 20 indexer.
The report covers the signature bypass, how unauthorized KRC 20 balances were created, how they were bridged to L2, and the resulting impact on liquidity.
Full incident report in the reply.
11
45
130
15,689
⚠️ Security notice: KRC-20 incident
An incident on offchain indexer earlier today resulted in unauthorised movement of ZEAL and NACHO out of the KRC-20 bridge custody. The custody's entire holdings of both tokens were taken, so ZEAL and NACHO on Igra and Kasplex L2 are not backed on L1.
Our current understanding is that the underlying issue affects KRC-20 accounting more broadly, not only these two tokens. We have escalated to the indexer, bridge and exchange teams.
Until they confirm a fix, treat KRC-20 balances and deposits on Igra as unconfirmed.
Paused until further notice: iKAS exits to Kaspa L1 and Hyperlane transfers. Existing balances are unaffected and nothing is lost. Both resume once the issue is confirmed resolved.
Until further notice:
- Do not bridge any KRC-20 token in either direction.
- Do not buy ZEAL or NACHO on any L2 DEX.
- Do not add liquidity to ZEAL or NACHO pools.
- Existing positions in WiKAS/ZEAL and NACHO/WiKAS, including farm positions, are impaired.
Exchanges and bridges crediting KRC-20 deposits should pause them pending confirmation from the indexer team.
Not affected on Igra: iKAS, WiKAS, IGRA, USDC, USDT, staking, LYNX, Kaskad.
ZEAL and NACHO are the only KRC-20 tokens bridged to Igra.
The Igra bridge contracts and relayers operated correctly throughout. The attacker's L2 address is 0x1B4B7108a49F028598c5ED49B7951c80d44e7FD2. Technical details will follow.
9
13
72
15,381
Important correction, incident related to KRC-20 offchain indexer, not L1.
L1 infrastructure is not affected.
17
20
118
6,996
Yes. Incident is contained on offfchain indexer, has nothing to do with L1 infrastructure. Apologies for not being clear on this.
just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)
12
33
177
6,801
Igra Labs retweeted
We are currently investigating a critical exploit affecting the Kasplex KRC20 indexer.
Based on what we know so far, the exploit allows an attacker to create unauthorized KRC20 balances, which were then bridged to Igra and Kasplex L2 and used to drain liquidity pools, including ZEAL and NACHO pools.
We strongly advise everyone not to buy or interact with KRC20 tokens until the issue is resolved, as the exploit may affect any KRC20 token.
We are in contact with the relevant teams and are working to block the exploiter from moving the remaining funds.
More details will be shared as soon as we complete our investigation.
25
32
152
25,017
Winners, a few of you have asked about sharing personal details. Use any name, address and phone number you're comfortable with. We just need somewhere a parcel can be delivered and a number the courier can reach. A parcel locker, PO box or a friend's address all work.
Igra × Tangem giveaway update:
The first claim window is closed. 2 prizes were claimed and will be sent to winners soon; 8 unclaimed prizes have now passed to reserve ranks 11-18 in the original draw order.
Check your wallet and claim by 14 Sep, 18:00 UTC:
igralabs.com/tangem-claim
Newly selected wallets:
11 — 0x9912…90da
12 — 0x48c7…02d4
13 — 0x1da8…b317
14 — 0xcfc8…7b59
15 — 0xfc69…3098
16 — 0x947b…4fe0
17 — 0xd08f…786b
18 — 0x16df…6568
(These are the next wallets in the reserve order fixed by the original cryptographically verifiable draw.)
Any prizes not claimed by the deadline will pass to the next eligible wallets.
Verify the order:
github.com/IgraLabs/tangem-z…
1
40
3,358
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!
11
47
216
8,430
Proposal passed. Welcome to Igra, @HallidayHQ! Pilot details to follow.
DAO proposal to integrate Halliday Payments and fund a two-month pilot is live: governance.igralabs.com/prop…
Background
Igra Network has no native fiat on-ramp or off-ramp today, so moving between fiat and Igra assets means manual bridging and third-party services.
Halliday Payments by @HallidayHQ would provide fiat on-ramp and off-ramp, crypto deposits and withdrawals across independent Igra ecosystem applications.
This Proposal
Approves the initial integration and a two-month pilot, authorizes Igra Association to sign the agreement and coordinate implementation as a non-profit ecosystem steward, and allocates 1,606,855 IGRA, about USD 6,000 at the CoinGecko reference price on 31 August, covering a USD 5,000 integration fee plus up to USD 1,000 contingency.
The Association will neither own nor operate the participating applications. It will publish a pilot assessment before the contractual notice deadline, and must terminate the agreement unless the DAO approves continuation in a separate vote. Anything unused returns to the DAO within 30 days.
Action if passed
Transfer 1,606,855 IGRA from the DAO treasury to the Igra Association treasury. The Association signs the Halliday agreement, coordinates technical integration and testing, and publishes the assessment.
Who can vote on this proposal?
Any IGRA holder. Voting is live.
6
39
173
8,376
Igra × Tangem giveaway update:
The first claim window is closed. 2 prizes were claimed and will be sent to winners soon; 8 unclaimed prizes have now passed to reserve ranks 11-18 in the original draw order.
Check your wallet and claim by 14 Sep, 18:00 UTC:
igralabs.com/tangem-claim
Newly selected wallets:
11 — 0x9912…90da
12 — 0x48c7…02d4
13 — 0x1da8…b317
14 — 0xcfc8…7b59
15 — 0xfc69…3098
16 — 0x947b…4fe0
17 — 0xd08f…786b
18 — 0x16df…6568
(These are the next wallets in the reserve order fixed by the original cryptographically verifiable draw.)
Any prizes not claimed by the deadline will pass to the next eligible wallets.
Verify the order:
github.com/IgraLabs/tangem-z…
Reminder to all winners to claim prizes by 7 September 2026, 18:00 UTC!
igralabs.com/tangem-claim
Unclaimed prizes will pass to the next wallets.
1
3
52
6,737
Dear Attesters, the dashboard has been upgraded: attester-dashboard.igralabs.…
- Added: Partial unstake. Withdraw part of your stake and remain an attester. Requires a pending exit with the cooldown elapsed, and must leave the 400,000 IGRA minimum.
- Fixed: WalletConnect on mobile browsers.
- Fixed: Attestations sometimes showing as n/a.
2
9
60
2,241