Methodology
How VibeProof knows what it shows
Verification states
- VerifiedVerified: Independently supported by bytecode, explorer source, or a cryptographic check.
- ObservedObserved: Measured directly by VibeProof at the time shown.
- Creator claimedCreator claimed: Supplied by the creator. VibeProof has not independently confirmed it.
- Not foundNot found: The check completed, and no evidence was found.
- UnavailableUnavailable: The check could not be performed. This is not a negative result.
Which contracts count as vibe/vibe
A token is treated as a vibe/vibe launch on Robinhood Chain Testnet only if one of these factories emitted its launch event. vibe/vibe publishes no address list: the addresses were read from the public vibe/vibe app configuration and confirmed onchain (bytecode present, factory creation transaction found, emitted event topics match). Their source is not verified on the explorer.
Contract analysis
Bytecode is read at a specific block. Function capabilities (mint, pause, blacklist, upgrade, fee and limit setters) are detected by matching 4-byte selectors in the runtime bytecode, or against the verified ABI when the explorer has source. Selector matching only recognises standard names; a custom-named admin function will not be detected. Proxies are detected via EIP-1967 storage slots, EIP-1167 minimal-proxy bytecode, and explorer metadata. For a beacon proxy, the beacon contract is asked for its implementation() and that address is analysed (the beacon itself is never treated as the implementation).
Activity
The indexer reads factory launch events, every ERC-20 Transfer of indexed tokens, and bonding-curve buy, sell, CurveCompleted and Graduated events emitted by each token's own curve. Holder counts are exact net balances above zero, excluding the zero and dead addresses, the token contract itself, its bonding curve and the launchpad's protocol contracts. Volume is summed only for ETH-quoted curves. Snapshots are stored every ten minutes per active token and power “What changed”.
Counters are shown only when a token's complete history from its launch block is indexed (fully covered). While history is queued (partial), being processed (indexing) or failed (error), counters are Unavailable and explorer counts are shown with their source instead. Historical event times come from block headers; for large backfills they are interpolated between headers at most 500 blocks apart and marked as such.
Creator history
- launches
- Tokens whose vibe/vibe launch event names this wallet as launcher/creator.
- graduated
- Launches for which a Graduated event was observed on their own bonding curve.
- active
- Launches not yet graduated with any observed Transfer/trade in the last 7 days.
- historical
- Launches not yet graduated, with complete indexed history and no observed activity in the last 7 days. Launches whose history is still being indexed are in neither group.
Product proof
Launch metadata (the JSON at the launch event's metadata URI) is fetched over IPFS gateways or HTTPS by the same sandboxed client. Its bytes are checked against the IPFS content identifier and, where the launch event commits to one, its metadataDigest. Matching hashes prove the bytes are the ones committed to, not that what they say is true: names, descriptions and social links in metadata are creator claims.
Only the launch creator (or a non-Vibe token's current owner) can submit links, after signing in with their wallet. Websites and demos are fetched from a sandboxed client that refuses private and internal network addresses. A site is observed if it is reachable, and verified if the page contains the token's contract address. GitHub repositories are read from the GitHub API; a README that contains the contract address upgrades the state to verified. Social links are recorded as creator claims only.
Sorting
- Newest
- Launch block timestamp, most recent first.
- Most transactions
- Count of ERC-20 Transfer events observed since launch. Only launches whose complete history is indexed are ranked.
- Most holders
- Wallets with a positive balance, excluding zero/dead, the token itself, the curve and protocol contracts. Only launches whose complete history is indexed are ranked.
- Most recently active
- Timestamp of the latest observed Transfer or curve trade. Only launches whose complete history is indexed are ranked.
- Most recently verified
- Most recent project proof submission.
- Recently graduated
- Graduation event timestamp (only launches with an observed Graduated event on their own curve).
What VibeProof never does
It does not produce a trust score, label a wallet or project as safe or unsafe, infer common ownership between wallets, predict prices, or recommend buying or selling anything.