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.00027 | 169.61K | 71,100,324 | 0xeea3d9…3af122 ↗ |
| buy | 0x0A8c…9667deployer | 0.0003 | 169.61K | 71,094,697 | 0x4358aa…cc153f ↗ |
| # | 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 71,918,143 in 2.4 s (resolve 2 ms, reads 891 ms, logs 1499 ms, deployer 25 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/0x2a7B…0c72 · badge: /api/badge/…svg
