Humanity Protocol founder (@terencekwok) took $60K from a $100K InfoFi rewards campaign for himself
The same protocol that paid Chinese scam KOLs has now suffered a $31M exploit
Well well well...
Checked $H / Humanity on @nansen_ai.
Token: 0xcf5104d094e3864cfcbda43b82e1cefd26a016eb
The “it was just hacked users” explanation looks incomplete.
The key flow I found:
- Nansen labels 0x44f161... as “Humanity”
- This wallet sent 141.18M $H (~$98M at the time) to 0xd1ea...
- 0xd1ea then routed large chunks to 0x9e9959 and 0xaf2a49
- 0x9e9959 sold ~119.3M $H (~$19.6M)
- 0xaf2a49 sold ~33.5M $H (~$4.1M)
The upstream flows are also messy: several addresses connected to Bybit / Gate / KuCoin hot wallets, SablierBatchLockup, and proxy/bridge style contracts interacted with the Humanity-labeled wallet or the dumping wallets.
There may have been real drainer activity too, so I’m not saying “no hack happened.”
But the main $H outflow/sell pressure does not look like random user wallets getting drained. It looks tied to a Humanity-labeled / operational / distribution / MM-style flow.
If the team says this was purely an external hack, they need to explain:
- what 0x44f161 is
- why 141M $H moved from it
- the relationship between 0xd1ea, 0x9e9959, 0xaf2a49
- why CEX funded / lockup related wallets appear in the path
Otherwise, the onchain path does not support a clean “just hacked” narrative.
References
- $H Token God Mode
https://t.co/DQ92wwrX8E
- Humanity-labeled wallet 0x44f161...
https://t.co/PvULSbpleF
- Main receiver 0xd1ea...
https://t.co/wRucJGI0j7
- Main seller 0x9e9959...
https://t.co/T6lyvoEArS
WTFFF
US companies spent $500 billion on research to build and train their AI models like claude.
Chinese AI firms used those AI models and trained their systems for almost free and saved billions because anyone can access it ?
I built the first AI that earns its existence, self-improves, and replicates without a human
wrote about the technology that finally gives AI write access to the world, The Automaton, and the new web for exponential sovereign AIs
WEB 4.0: The birth of superintelligent life
A new, unified stack for Base Chain
Excited to share that we are evolving our technical roadmap, consisting of our own spec, code, and infra to accelerate the foundation of Base. This shift gives us the autonomy to ship protocol improvements more frequently and focus our resources on scaling to 1 gigagas/s.
What this means for builders:
- Higher Velocity: Targeting 6 hardforks per year to get you new features and fixes faster.
- Massive Scale: Targeting 1 gigagas/s to support high-throughput apps without congestion.
- Extreme Reliability: Targeting 99.99% non-empty blocks and predictable, low fees.
- Simpler Design: A maximally simple spec that’s easier to audit and build on.
Along with this, we will take a more active role in managing our own upgrade schedule and stack: allowing us to build what the ecosystem needs, at the speed it needs, while remaining deeply aligned with Ethereum.
Read the full technical breakdown here: https://t.co/5gVnhgh2Q5
🇺🇸 JUST IN:
U.S. TREASURY SECRETARY BESSENT IS URGING LAWMAKERS TO IMMEDIATELY PASS THE CRYPTO MARKET STRUCTURE BILL.
AFTER ALL THIS TIME, IT FINALLY LOOKS LIKE IT’S MOVING. 🚀
Have been following reactions to what I said about L2s about 1.5 days ago.
One important thing that I believe is: "make yet another EVM chain and add an optimistic bridge to Ethereum with a 1 week delay" is to infra what forking Compound is to governance - something we've done far too much for far too long, because we got comfortable, and which has sapped our imagination and put us in a dead end.
If you make an EVM chain *without* an optimistic bridge to Ethereum (aka an alt L1), that's even worse. We don't friggin need more copypasta EVM chains, and we definitely don't need even more L1s. L1 is scaling and is going to bring lots of EVM blockspace - not infinite (AIs in particular will need both more blockspace and lower latency than even a greatly scaled L1 can offer), but lots.
Build something that brings something new to the table. I gave a few examples: privacy, app-specific efficiency, ultra-low latency, but my list is surely very incomplete.
A second important thing that I believe is: regarding "connection to Ethereum", vibes need to match substance.
I personally am a fan of many of the things that can be called "app chains". For example I think there's a large chance that the optimal architecture for prediction markets is something like: the market gets issued and resolved on L1, user accounts are on L1, but trading happens on some based rollup or other L2-like system, where the execution reads the L1 to verify signatures and markets. I like architectures where deep connection to L1 is first-class, and not an afterthought ("we're pretty much a separate chain, but oh yeah, we have a bridge, and ok fine let's put 1-2 devs to get it to stage 1 so the l2beat people will put a green checkmark on it so vitalik likes us").
The other extreme of "app chain", eg. the version where you convince some government registry, or social media platform, or gaming thing, to start putting merkle roots of its database, with STARKs that prove every update was authorized and signed and executed according to a pre-committed algorithm, onchain, is also reasonable - this is what makes the most sense to me in terms of "institutional L2s". It's obviously not Ethereum, not credibly neutral and not trustless - the operator can always just choose to say "we're switching to a different version with different rules now". But it would enable verifiable algorithmic transparency, a property that many of us would love to see in government, social media algorithms or wherever else, and it may enable economic activity that would otherwise not be possible.
I think if you're the first thing, it's valid and great to call yourself an Ethereum application - it can't survive without Ethereum even technologically, it maximizes interoperability and composability with other Ethereum applications.
If you're the second thing, then you're not Ethereum, but you are (i) bringing humanity more algorithmic transparency and trust minimization, so you're pursuing a similar vision, and (ii) depending on details probably synergistic with Ethereum. So you should just say those things directly!
Basically:
1. Do something that brings something actually new to the table.
2. Vibes should match substance - the degree of connection to Ethereum in your public image should reflect the degree of connection to Ethereum that your thing has in reality.