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 | SPY | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x6505…40Dc | 0.96991 | 183.48M | 60,415,906 | 0x61ddeb…412bfe ↗ |
| buy | 0x0ca3…734Bdeployer | 0.9896 | 183.48M | 60,415,830 | 0xb5f374…de0ff9 ↗ |
| # | 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,926,476 in 9.8 s (resolve 0 ms, reads 2371 ms, logs 7286 ms, deployer 27 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/0xeC2d…3bc6 · badge: /api/badge/…svg
