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 graduated tokens in the index use the same symbol. Only the address identifies a token.
2 trades from 2 wallets. Too little to say anything about demand.
Every flag is a fixed condition; definitions and thresholds.
| Side | Wallet | USDG | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x7Ab3…1aF0 | 94.09 | 29.10M | 68,979,017 | 0x048f18…e8e391 ↗ |
| buy | 0xD908…1944deployer | 100 | 29.10M | 68,977,193 | 0x6308c0…e6f969 ↗ |
| # | 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 69,524,737 in 2.6 s (resolve 0 ms, reads 315 ms, logs 2251 ms, deployer 1 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/0x6d58…29f5 · badge: /api/badge/…svg
