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 trade from 1 wallet. Too little to say anything about demand.
Every flag is a fixed condition; definitions and thresholds.
| Side | Wallet | NVDA | Tokens | Block | Tx |
|---|---|---|---|---|---|
| buy | 0x6505…40Dc | 0.58332 | 32.56M | 70,736,099 | 0xa53ab4…30e174 ↗ |
| # | Wallet | Balance | Share |
|---|---|---|---|
| 1 | 0xc00d…b503 | 32.56M | 100.0% |
No bonds posted for this token.
Connect the deployer wallet to post a bond. Anyone can challenge an open bond below.
Computed at block 73,871,053 in 9.2 s (resolve 1 ms, reads 5342 ms, logs 3753 ms, deployer 40 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/0x7671…E919 · badge: /api/badge/…svg
