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 | 0x3868…6E00 | 0.00457 | 2.84M | 59,433,524 | 0xbd0a24…9ac3c2 ↗ |
| buy | 0x3D0f…Ff6cdeployer | 0.005 | 2.84M | 59,111,599 | 0x72ad33…a1c846 ↗ |
| # | Wallet | Balance | Share |
|---|---|---|---|
| 1 | 0x3868…6e00 | 0.0000 | 100.0% |
No bonds posted for this token.
Connect the deployer wallet to post a bond. Anyone can challenge an open bond below.
Computed at block 70,945,872 in 3.3 s (resolve 3 ms, reads 508 ms, logs 2751 ms, deployer 34 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/0xdEE7…4e7B · badge: /api/badge/…svg
