- Tweets 2,984
- Following 208
- Followers 1,036
- Likes 21,613
Chris retweeted
No matter where this journey takes us, I’m grateful we’re here together nacho-the-kat:native & kaspa:native family 💚
8
14
71
1,018
Chris retweeted
I hope the entire $KAS world does appreciate Igra Team.
This is NOT how 99% of crypto teams react.
⚠️ 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.
1
14
75
1,927
Mr. / Mrs. Attacker: Be aware.
We have gathered a ton of evidence.
Act accordingly.
$KAS
🚨 KRC 20 Incident: Complete Fund Trail
Yesterday we published the technical breakdown of how the KRC 20 indexer was exploited.
Today we are publishing the other half: where the money went.
We traced the proceeds from the forged transfers, through the bridges and liquidity pools, back onto Kaspa L1 and through the addresses used to move the funds.
The trail reaches identifiable exchange accounts, including KuCoin, while a significant portion of the iKAS remains trapped on Igra.
Every transaction in the report is public and can be verified independently.
Full report in comments.
11
26
966
Chris retweeted
We independently checked the transactions in this report and fully agree with @ZealousSwap's findings.
KAT Bridge behaved as designed: for KRC-20 it treats the @Kasplex indexer as the source of truth, and it minted on EVM only after that indexer reported a successful deposit. Routes are paused at the smart-contract level while we wait for a meaningful updates from @kasplex. The Vault signers keys, Relayers keys, Onboarder keys, and SC Admins keys were never accessed, the smart contracts were not hacked; the source of truth upstream (kasplex indexer) allowed forged transactions to remove liquidity from the vault without any valid signature.
We also audited the full KAT Bridge KRC-20 history. None of those mints used an empty-sig / OP_NOT / KASPLEX forge. The only transactions we found with that pattern are the ones in the ZealousSwap report ( vault outflows, not bridge mints or releases). Due to the structure of the possible forgeries we'll need to continue this research when a KRC20 indexer is available because not all possible forgery txn shapes require showing relation to the Bridge vault address on a kaspa explorer but they will in the indexer's oplist txn history.
Out of caution, KRC-721 bridge is paused as well. We have no evidence it was affected or targeted.
@ZealousSwap's incident report - drive.google.com/file/d/1X7j…
🚨 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.
2
11
34
2,218
Chris 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
Chris retweeted
GOALS FOR THE NEXT 18 MONTHS
Every kaspa:native @kaspaunchained account posting quality content regularly:
10K+ followers
Every nacho-the-kat:native @NachotheKat account doing the same:
1K+ followers.
Follow each other.
Support each other.
But bring value (fun is also value).
Bring the good vibes.
No need to be scientific.
No need to be techy.
Think about the culture we want to bring to the masses.
We're building for people.
Not algorithms.
Kaspa Fam, ARE YOU IN?
7
19
49
665
THIS question alone is a gigantic issue for our society.
Less power to the trackers.
110% power to the people.
$KAS
1
14
499
Chris retweeted
Vision like this is what moves the $KAS ecosystem forward. Glad to see Kaskad exploring new pathways, reaching beyond a single chain while keeping $KSKD and its Kaspa roots at the core.
New ground, new audiences, more seeds planted for Kaspa to grow.
I shared some thoughts on expanding Kaspa's reach a while back: nitter.net/Chriscrypto_89/status/…
Onward. 🌱
We've been silently cooking on Kaskad, and after delivering our lending on @Igra_Labs, we're now ready to expand our services to additional chains. Both EVM and POW 👀.
The KSKD token will stay at the center of them all, sharing the same existing supply, utility and tokenomic across all supported networks.
First stop: Robinhood chain. Ongoing work: Kaspa L1 (thanks to all the Kaspa Core taking the time to discuss and guide us).
Igra mainnet will of course remain as we have plans to scale there as well.
We were always meant to be multichain, and we will always keep building on the Kaspa Ecosystem.
Onward!
2
6
52
1,449