Skip to content

asking vrax by Virtuals

$VRAXAI

AI Agents

Researched

Is this your project? Claim and verify →

asking vrax

What HEY knows

Building
No builder source linkedHEY holds no repository, changelog or feed it can read, so no count here is a measured zero.
FollowCreate alertTerminal preview
Share

Follow puts asking vrax by Virtuals on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me asking vrax by Virtuals’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Known so far
Contract
0x7cfd…ade30x7cfd0a2fa5be4b1d65a9771938d7e071a63dade3
Deployed
2026-10-14, read from the chain
Launched via
Virtuals
Token market
Market data insufficientToken unverifiedHEY found this token through a launchpad record. The declared site does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership.
Product usage
1 of 1 watched contract active · 7 calls over the 3 of 7 days HEY holds (4 calls to the contracts' own functions); the rest unknown, not zero.
Links
Website
Latest read
HEY last read this project’s records 6m ago.

What HEY can’t verify yet

  • Building activity — No repository, changelog or feed to read.
  • Repositories — No repository the project claims as its own.
  • Releases — No repository, changelog or feed to read.
  • Official docs — HEY read its website and found no link to docs.
  • Official site changes — Its website is not yet confirmed as the project’s own.
  • Contract activity — Some days’ events were decoded; on others only the calls could be read.
  • Supply distribution — HEY has not mapped this token’s supply yet.

HEY cannot answer whether anyone is building this yet (building activity: no source); it can answer 9 of the 16 research questions that apply.

What HEY is researching

  • Still to read: Supply distribution.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
No builder source linked.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadWhat HEY derivedHEY’s activity rule reads the counted events as “No builder source linked”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source1 registered source, 1 of them context only.ReadWhat HEY derivedThe quality gate’s stored decision: “Researched”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Token unverified.
Token unverified: HEY found the token through a launch record or a market listing, and nothing the project published names it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedToken unverified: HEY knows it from a launchpad record, and the project’s site does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Market data insufficient.
Market data insufficient: the only pool is the launch pool holding the token’s own supply, and no reading reports its volume.
Source4 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Market data insufficient”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology

Shared change · Published

asking vrax by Virtuals was published on HEY with its sources recorded.

Observed by HEY on 2026-10-15Source: hey state

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about asking vrax by Virtuals? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

1 change on HEY’s record for asking vrax by Virtuals: 1 new project on HEY.

asking vrax by Virtuals on What changed →

The full change record holds 1 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

  • Website
    https://vrax.site/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, the team submits or claims the project, or a repository HEY verified links to it.
Contract
0x7cfd…ade30x7cfd0a2fa5be4b1d65a9771938d7e071a63dade3