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 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 | 0x6505…40Dc | 0.01843 | 11.30M | 69,837,667 | 0xc547d1…9afbab ↗ |
| buy | 0x23aC…fc8edeployer | 0.02 | 11.30M | 69,835,609 | 0x2adb1a…77b721 ↗ |
| # | 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 73,729,203 in 0.9 s (resolve 0 ms, reads 63 ms, logs 745 ms, deployer 51 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/0x14Eb…2de5 · badge: /api/badge/…svg
