read the chain,
not the story.
Ignore the narrative. Read the chain.
Each issue picks one project and traces its token flows, gas sources, derivatives positions and order-book depth, then spells out what can be proven and what cannot.
ARIAAriaAI · BNB ChainLatest investigation

ARIA: tokens from the project's own wallets hit an exchange on crash day
- The official allocation table matches the chain exactly: the community airdrop, team, ecosystem fund and investor allocations all came from one distribution wallet, and every monthly community and ecosystem release went to the project's own hub wallet
- At 17:48 on 14 April, mid-crash, tokens the hub wallet had sent out in March passed through two layers of fresh addresses and reached Gate in the same second, 37.05 million in total, close in time and size to the sell-off flagged by on-chain analyst EmberCN
- Between 12:14 and 12:31 on 14 October, the 680 million tokens left in the team, investor, community, ecosystem and hub wallets all moved into five multisigs created that day; gas for all five came from Gate withdrawals in the same minute
How we investigate
Trace the holders
List the top holders and trace, one by one, where their tokens and gas came from, to see which wallets belong to the same entity.
Follow the flows
Track released and unlocked tokens, and check whether they moved to exchanges around price moves.
Match the market
Put on-chain spot flows next to derivatives volume, open interest and order-book depth, to see who is moving the price.
Separate the facts
What the chain proves is written as fact; what it cannot show is marked "cannot be verified". We do not label anyone.
By sector
Each issue is filed by the chain the project lives on: Layer 1, Layer 2, and everything else.
Layer 1
Projects on base-layer chains: BNB Chain, Ethereum, Solana, Tron and others.
Layer 2
Projects on Ethereum Layer 2 networks: Base, Arbitrum, Optimism and others.
Other
Everything else: multichain deployments, app-specific chains, the Bitcoin ecosystem and more.