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 | NVDA | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x6505…40Dc | 1.11695 | 64.10M | 76,705,344 | 0x07dc33…f15ede ↗ |
| buy | 0xb3ef…EFaCdeployer | 1.16301 | 64.10M | 76,704,938 | 0xd89ebd…390891 ↗ |
| # | 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 80,015,370 in 3.0 s (resolve 0 ms, reads 1133 ms, logs 1755 ms, deployer 15 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/0x4fD4…8Fb7 · badge: /api/badge/…svg
