Pinned Tweet
My first on-chain review of ZEAL, based only on public Igra L2 data.
Five wallets funded by the ZealousSwap contract deployer sold 18.78M ZEAL for 1.91M KAS (Apr 12 – Oct 5), no buys recorded.
How does this fit the stated vesting?
@ZealousSwap @IgraLabs
1/13
My read: every funding link leads back to the protocol deployer. Gas, a shared proceeds hub, sellers created minutes apart. Holders deserve a clear answer. @ZealousSwap, who controls these wallets, and how does this square with the stated vesting?
@Igra_Labs fyi
13/13
0x09a00896 was created on 4 October. No other assets, no purchases.
11:59 sold 300,000 ZEAL. Next day 12:11, another 300,000.
Two million left at that rate is roughly a week, with two million more in the hub.
Verify at explorer.igralabs.com
12/13
Meanwhile, on 8 Sep 11:48 UTC, the deployer had sent 100 KAS to 0x5317F8C50bF206cAA00F3d05cdE212E497Ac97DF.
That was the first transaction in that wallet's history. Two minutes later 4,000,000 ZEAL arrived via the bridge, and at 14:40 it went into staking
10/13
Every KRC-20 user frozen on @CoinExcom is still locked out.
Their Sept 29 deadline to withdraw assets in original form came and went while our funds were blocked. We could not act not because we missed it, but because they froze us.
Oleg Galansky retweeted
CEO, Haipo Yang @YHaiYang required immediately.
Withdraws are still suspended for Kaspa KRC20 tokens (i.e. NACHO) on CoinEx because the Kasplex KRC20 node indexer received a new critical update. Support tickets remain unresolved.
@CoinExCom must update their Kaspa KRC20 node as soon as possible with the GitHub code link provided directly from @Kasplex: nitter.cf/kasplex/status/2106266…
"Stop the node process (or Docker container), delete the data directory, and restart the node; it will then automatically begin syncing."
GitHub link: github.com/kasplex/go-krc20d…
This is a simple yet crucial update to allow withdraws according to the CoinEx wind-down.
Please share to extend outreach, while continuing to tag, email, and submit support tickets on CoinEx until resolved.
Update on the KRC20 incident:
The code repository has been updated:
github.com/kasplex/go-krc20d
If you are running your own node, please upgrade:
github.com/kasplex/go-krc20d…
Stop the node process (or Docker container), delete the data directory, and restart the node; it will then automatically begin syncing.
Oleg Galansky retweeted
Every KRC-20 user frozen on @CoinExcom is still locked out.
Their Sept 29 deadline to withdraw assets in original form came and went while our funds were blocked. We could not act not because we missed it, but because they froze us.
Sending KRC-20 does not require a synced indexer it takes one signature.
Final withdrawals close Dec 22.
If your KRC-20 or USDT is stuck on CoinEx, reply. We're building a list of everyone affected.
Everything still sits in one wallet, verifiable by anyone:
8,424,913 ZEAL
11,190,759,960 NACHO
+ 19 more KRC-20 tokens
api.kasplex.org/v1/krc20/add…
The @kasplex reindex is complete. Our deposits verify as valid on-chain. The technical reason for the freeze no longer exists.