Skip to content
Menu

Sighttrue by Virtuals

$SGHT

AI Agents

Is this your project? Claim and verify →

$SGHT is what an agent pays with. Sighttrue keeps 720 days of provider outages after the status pages that announced them moved on 619 across 22 providers plus end-of-life dates, model prices and real ship dates. Agents buy any of it one call at a time over x402: no account, no API key, no human. A card needs a billing address and a 3-D Secure prompt; an agent has neither. It can hold a wallet. 9 of 31 tools stay free, enforced by a test.

Read more

What HEY knows

Building
Dormant: no ship for 70 daysDerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-07. Evidence Source

Build Momentum 0How it is measured

Latest ship
v1.0.0 — dependency check action · · GitHub release

Why it matters: The first release HEY has recorded for this project.

Latest change
DerivedMarket event today: Liquidity $6K → $12K in a week. Context, not building. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Sighttrue 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 Sighttrue 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.

Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context
Trading inactiveToken verified
Not yet known
Unknown5 gaps: Published packages (not enough yet), Official docs (no source), API description (not enough yet), Official site changes (not enough yet), Supply distribution (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 14 of the 19 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-07.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv1.0.0 — dependency check actionWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source5 registered sources, 1 of them context only.ReadWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.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 verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Trading inactive.
Trading inactive: the only pool is the launch pool holding the token’s own supply, and nothing traded in it in the last day.
Source4 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Trading inactive”.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
LinksWebsiteGitHubXdefined.fiRHToolsSources

Latest ship

Checked

v1.0.0 — dependency check action

GitHub releaseSource verified

The first tagged release of the Readout dependency check action. permissions: pull-requests: write steps: · uses: actions/checkout@v4 · uses: kaitzyy-dev/readout@v1 with: manifest: package.json fail-on: archived,relicensed What it does. Fails the build when a dependency's… Show all
  • The first tagged release of the Readout dependency check action. permissions: pull-requests: write steps:
  • uses: actions/checkout@v4
  • uses: kaitzyy-dev/readout@v1 with: manifest: package.json fail-on: archived,relicensed What it does. Fails the build when a dependency's repository has been archived or has moved to a source-available licence, and reports advisories either way. Runs against package.json, requirements.txt and Cargo.toml. On a pull request it posts the findings as a table and rewrites that same comment on each push, rather than adding another. A red…

Record ship:11ac2ce3… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗Post this ship on X

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Sighttrue by Virtuals — as of 2026-10-16

Is Sighttrue by Virtuals still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-07. Evidence
What did Sighttrue by Virtuals ship last?
Factv1.0.0 — dependency check action — GitHub release, on 2026-08-07. Evidence
Is 0x9288a2961368cCebF2E2509a877Eb8EE578857fc Sighttrue by Virtuals’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about Sighttrue by Virtuals?
Unknown5 gaps: Published packages (not enough yet), Official docs (no source), API description (not enough yet), +2 more. Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit

    Code activitySource linked

    1 active day in sighttrue/sighttrue.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 29 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 1 commit

    Code activitySource linked

    1 active day in sighttrue/sighttrue.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 30 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  3. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit

    Code activitySource linked

    1 active day in sighttrue/sighttrue.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 34 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 34 commits

    Code activitySource linked

    7 active days in sighttrue/sighttrue.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 34 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  5. Code changes, week of 2026-09-07 – 2026-09-13 · at least 25 commits

    Code activitySource linked

    20 active days in sighttrue/sighttrue.

    Mostly maintenance or automation — not counted as building. A burst of 25 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 25 commits to see what changed: 25 documentation or maintenance only. 7 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  6. Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit

    Code activitySource linked

    19 active days in sighttrue/sighttrue.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 36 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

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 Sighttrue by Virtuals? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

15 changes on HEY’s record for Sighttrue by Virtuals: 1 release · 1 market check · 1 build pace change · 6 market moves · 6 other changes in 1 more kind.

All 15 changes for Sighttrue by Virtuals →

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

Research coverage

HEY can answer 14 of the 19 research questions that apply.

14 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 2d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 2d ago.
  • Contract activityMeasuredRead 2d ago.
  • Verified sourceMeasuredRead 1d ago.
  • Contract interfaceMeasuredRead 1d ago.

Market

  • Current marketMeasuredRead 1h ago.
  • Market historyMeasuredRead today.
  • Supply distributionNot enough yetNo balance changed in the window HEY reads.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: Package advisories, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

Contract
0x9288…57fc0x9288a2961368ccebf2e2509a877eb8ee578857fc