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.
1 graduated token 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 | COIN | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x5408…4670 | 0.00118 | 58.42K | 71,537,125 | 0x58f1e9…b1b41a ↗ |
| buy | 0xC23C…2646 | 0.00135 | 58.42K | 71,537,120 | 0x01bbb4…8175bb ↗ |
| # | 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 74,093,066 in 1.1 s (resolve 0 ms, reads 320 ms, logs 531 ms, deployer 16 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/0xe124…A4fe · badge: /api/badge/…svg
