Assaying · reading Robinhood Chain
Resolving the launch, reading the curve, replaying the tape and transfers, then the deployer's record. A few seconds on the public RPC.
Resolving the launch, reading the curve, replaying the tape and transfers, then the deployer's record. A few seconds on the public RPC.
2 wallets are linked by passing the token between them; together they bought 100.0% of all quote in. A heuristic, not proof of one owner.
2 trades from 1 wallet. Too little to say anything about demand.
Every flag is a fixed condition; definitions and thresholds.
| Side | Wallet | ETH | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x6505…40Dc | 0.17869 | 100.69M | 61,962,002 | 0xdc84f6…7a004e ↗ |
| buy | 0x6505…40Dc | 0.198 | 100.69M | 61,201,729 | 0x70e904…8ab868 ↗ |
| # | Wallet | Balance | Share |
|---|
No bonds posted for this token.
Connect the deployer wallet to post a bond. Anyone can challenge an open bond below.
Computed at block 71,419,867 in 3.6 s (resolve 1 ms, reads 311 ms, logs 3246 ms, deployer 0 ms). Sources: pons factory and curve contracts, the token's Transfer logs, and the Chainlink ETH/USD feed, all on Robinhood Chain via public RPC.
What this cannot tell you: intent, off-chain coordination, funding links between wallets, liquidity after graduation, or what the price will do. Full method and limits →
JSON: /api/assay/0x99C2…700D · badge: /api/badge/…svg
