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 | ETH | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0xB3EA…2832 | 0.00009 | 58.63K | 69,747,709 | 0x2ecd74…6827bf ↗ |
| buy | 0x478b…114ddeployer | 0.00009 | 58.63K | 69,747,154 | 0x61ae44…c7b808 ↗ |
| # | 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,772,796 in 0.9 s (resolve 0 ms, reads 104 ms, logs 729 ms, deployer 18 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/0x3566…8D33 · badge: /api/badge/…svg
