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 2 wallets. Too little to say anything about demand.
Every flag is a fixed condition; definitions and thresholds.
| Side | Wallet | ETH | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0xB3EA…2832 | 0.01881 | 11.42M | 69,757,784 | 0x4080d9…02bf5d ↗ |
| buy | 0x5236…Ab6fdeployer | 0.02 | 11.42M | 69,756,950 | 0xab6b7a…8f558a ↗ |
| # | 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 72,988,789 in 3.5 s (resolve 1 ms, reads 1156 ms, logs 2253 ms, deployer 31 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/0x5cC2…6713 · badge: /api/badge/…svg
