Skip to content

Cyber Inu

$CYBERINU

Not confirmed by the project: The project’s own site named this contract when HEY read it, but the site has not answered HEY’s reads since. HEY keeps that reading as context and does not treat the token as confirmed until the site answers again. Token market

Contract 0xc2703284e399a9778dce9734e69dd6ab0dc71e18

HEY holds 18 other Robinhood Chain tokens that use $CYBERINU. This page is only the contract above. See them

Is this your project? Claim it →

CYBERINU/TSLA

What HEY knows

Development

Last shipped 32 days agoActive: 0 counted ships in 30 days; latest ship 32 days ago. Evidence Source

Build Momentum 25How it is measured

Latest: Deployed a new contract: 0x8e6a…4889

Token market · context

Launch pool only

Token check

Not confirmed by the project
FollowCreate alertTerminal preview
Get updates

Get updates

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

Sign in to follow Cyber Inu

No account? Email me Cyber Inu’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.

View latest ship
Share
Attention
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
Product usage
Fact1 of 29 watched contracts active · 16 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact29 contracts on record for code changes, 4 behind a proxy, 1 with published source code; latest change 32 days ago: Deployed a new contract: 0x8e6a…4889. Source
Not yet known
Unknown5 gaps: Repositories (no source), Releases (no source), Official docs (source unavailable), Official site changes (source unavailable), Contract activity (partly measured). No repository the project claims as its own.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule's longer window: 19 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-09-29, is more than 30 days old.
SourceHEY holds no repository, changelog or feed it can read for this project; the status rests on building events it counted from the chain or from corroborated sources.ReadRecordsDeployed a new contract: 0x8e6a…4889Deployed a new contract: 0xf373…15cfDeployed a new contract: 0x359c…1ff4+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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 counted building from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsDeployed a new contract: 0x8e6a…4889Deployed a new contract: 0xf373…15cfDeployed a new contract: 0x359c…1ff4+4 moreWhat 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.
Not confirmed by the project.
Not confirmed by the project: HEY has not confirmed that the project stands behind this contract — the project’s site named it, and has not answered HEY’s reads since.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot confirmed by the project: the project’s site named it, and has not answered HEY’s reads since.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Launch pool only.
Launch pool only: the only pool is the launch pool holding the token’s own supply, and it traded in the last day.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Launch pool only”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Launch pool only”. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 11 of the 16 research questions that apply.
11 of 16 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasured
  • RepositoriesNo sourceNo repository the project claims as its own.
  • ReleasesNo sourceNo source HEY reads releases from.
  • TimelineMeasured

Official site

  • Official docsSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Contracts

  • Contract creationMeasuredRead 2d ago.
  • Contract activityPartly measuredSome days’ events were decoded; on others only the calls could be read.
  • Published source codeMeasuredRead 2d ago.
  • Contract interfaceMeasuredRead 2d ago.

Market

  • Current marketMeasuredRead 24m ago.
  • Market historyMeasuredRead yesterday.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: API description, Repository details, Published packages, 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.

Market figures are context only and never change activity status. Methodology

Latest ship

Deployed a new contract: 0x8e6a…4889

New contractSource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

The account that launched Cyber Inu’s token deployed 0x8e6a…4889 on 2026-09-29. Read from the chain; the creating transaction is the evidence.

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

Shared change · Development spike

Cyber Inu: 4 meaningful ships were recorded in the latest 7 days, from 0 in the 7 days before.

Builder status: Active.

Dated 2026-09-28 by the sourceSource: HEY Signal

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: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

  1. 2 contracts deployed by the project’s deployer between 22:37:48 and 22:37:56 UTC on 29 Sep

    New contract

    Show all 2 contracts
    1. Deployed a new contract: 0x14f4…edc4

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x14f4…edc4 on 2026-09-29. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x5970…f3e2

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x5970…f3e2 on 2026-09-29. Read from the chain; the creating transaction is the evidence.

  2. 3 contracts deployed by the project’s deployer between 22:22:31 and 22:23:28 UTC on 28 Sep

    New contract

    Show all 3 contracts
    1. Deployed a new contract: 0xf373…15cf

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0xf373…15cf on 2026-09-28. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x04e1…b7db

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x04e1…b7db on 2026-09-28. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0xd013…8d8a

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0xd013…8d8a on 2026-09-28. Read from the chain; the creating transaction is the evidence.

  3. Deployed a new contract: 0x359c…1ff4

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x359c…1ff4 on 2026-09-28. Read from the chain; the creating transaction is the evidence.

  4. Deployed a new contract: 0xa559…cdcb

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0xa559…cdcb on 2026-09-28. Read from the chain; the creating transaction is the evidence.

  5. 2 contracts deployed by the project’s deployer between 02:15:11 and 02:15:19 UTC on 28 Sep

    New contract

    Show all 2 contracts
    1. Deployed a new contract: 0xba6b…1c7b

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0xba6b…1c7b on 2026-09-28. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x2716…c4ad

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x2716…c4ad on 2026-09-28. Read from the chain; the creating transaction is the evidence.

  6. 2 contracts deployed by the project’s deployer between 12:16:38 and 12:16:46 UTC on 27 Sep

    New contract

    Show all 2 contracts
    1. Deployed a new contract: 0x354f…7d42

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x354f…7d42 on 2026-09-27. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x568b…945d

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x568b…945d on 2026-09-27. Read from the chain; the creating transaction is the evidence.

  7. 2 contracts deployed by the project’s deployer between 21:55:33 and 21:55:38 UTC on 25 Sep

    New contract

    Show all 2 contracts
    1. Deployed a new contract: 0x974b…df08

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x974b…df08 on 2026-09-25. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x504d…74ec

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x504d…74ec on 2026-09-25. Read from the chain; the creating transaction is the evidence.

  8. Deployed a new contract: 0xa6ad…46b6

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0xa6ad…46b6 on 2026-09-25. Read from the chain; the creating transaction is the evidence.

Earlier ships (10)
  1. Deployed a new contract: 0xb47a…0701

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0xb47a…0701 on 2026-09-25. Read from the chain; the creating transaction is the evidence.

  2. Deployed a new contract: 0x5097…d826

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x5097…d826 on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  3. 3 contracts deployed by the project’s deployer between 21:58:31 and 21:59:02 UTC on 24 Sep

    New contract

    Show all 3 contracts
    1. Deployed a new contract: 0xba38…2cd1

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0xba38…2cd1 on 2026-09-24. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x0feb…7dba

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0x0feb…7dba on 2026-09-24. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0xde51…aadf

      New contractSource-backed

      The account that launched Cyber Inu’s token deployed 0xde51…aadf on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  4. Deployed a new contract: 0xa014…1f73

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0xa014…1f73 on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  5. Deployed a new contract: 0x3d4e…ff72

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x3d4e…ff72 on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  6. Deployed a new contract: 0x00d5…ea08

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x00d5…ea08 on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  7. Deployed a new contract: 0x979f…cbab

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x979f…cbab on 2026-09-24. Read from the chain; the creating transaction is the evidence.

  8. Deployed a new contract: 0x58eb…221f

    New contractSource-backed

    The account that launched Cyber Inu’s token deployed 0x58eb…221f on 2026-09-24. Read from the chain; the creating transaction is the evidence.

Other changes on HEY’s record

40 changes on HEY’s record for Cyber Inu: 1 new Verified Builder or owner proof · 1 contract in use again or for the first time · 2 token check changes · 28 contract changes · 8 other changes in 2 more kinds.

All 40 changes for Cyber Inu →

The full change record holds 5 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xC2703284E399a9778DcE9734e69dD6aB0dC71E18 on Robinhood Chain

0xc270…1e180xc2703284e399a9778dce9734e69dd6ab0dc71e18

Not confirmed by the project.

Market context

Launch pool only · FDV (fully diluted) $26.1K · liquidity $27.5K (launch pool inventory, not a market) · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
51d ago

Market

24h volume
$5
Trades 24h
2 buys · 1 sells

The pool still holds the token’s own supply, so its reported liquidity is not a depth figure; trades in the last 24 hours are what make this a market.

Market history, trading and checks →

Market integrity

Liquidity is 47% below the level it held two days running ($51.7K, 2026-09-17).

Market
Launch pool only
Last day with trading
2026-10-30

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-31 00:52 UTC · How HEY checks this

Questions HEY can answer about Cyber Inu — as of 31 Oct

Show the answers
Is Cyber Inu still being built?
DerivedActive: 0 counted ships in 30 days; latest ship 32 days ago. Evidence
What did Cyber Inu ship last?
FactDeployed a new contract: 0x8e6a…4889 — New contract, 32 days ago. Evidence
Is 0xC2703284E399a9778DcE9734e69dD6aB0dC71E18 Cyber Inu’s own contract?
UnknownNot confirmed by the project: The project’s own site named this contract when HEY read it, but the site has not answered HEY’s reads since. HEY keeps that reading as context and does not treat the token as confirmed until the site answers again. Details
What does HEY not know about Cyber Inu?
Unknown5 gaps: Repositories (no source), Releases (no source), Official docs (source unavailable), +2 more. No repository the project claims as its own.

Sources

2 places HEY reads for Cyber Inu