Skip to content

Tokyo Futuro

$ZENI

Gaming

Contract 0x6354a37799e96ed6ccaecffbe1c100fa7f30cec8

HEY holds 2 other Robinhood Chain tokens with the ticker $ZENI. This page is only the contract above. See them

Is this your project? Claim it →

Tokyo, 2089. Build a crew, work the rackets, bet the Pit, and keep company with the girls of the Bath House. One of the first GameFi games on Robinhood Chain.

What HEY knows

Development

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

Build Momentum 71How it is measured

Latest: Deployed a new contract: 0xfcc7…e1f0

Token market · context

Active market$81K fully diluted valuation

Token check

Project names this contract
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Tokyo Futuro 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 Tokyo Futuro

No account? Email me Tokyo Futuro’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.

Attention
Building ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 98.6% of them, its market attention ahead of 83.6% (a gap of 15). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

More detail
Product usage
Fact20 of 44 watched contracts active · 101,366 calls in 7 days (25,029 calls to the contracts' own functions; 76,337 ERC-20 token transfers and approvals, which trading alone produces).

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

Contracts
Fact47 contracts on record for code changes, 12 with published source code; latest change 18 days ago: Deployed a new contract: 0xfcc7…e1f0. Source
Not yet known
Unknown3 gaps: Repositories (no source), Releases (no source), Official docs (no source). 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: 24 counted ships in the last 30 days, the newest 2026-11-02.
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: 0xfcc7…e1f0Deployed a new contract: 0xbaa2…9f8aDeployed a new contract: 0x750d…e8f6+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.
Source13 registered sources, 0 of them context only.ReadRecordsDeployed a new contract: 0xfcc7…e1f0Deployed a new contract: 0xbaa2…9f8aDeployed a new contract: 0x750d…e8f6+7 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.
Project names this contract.
Project names this contract: 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 derivedProject names this contract: 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.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Research coverage: HEY can answer 13 of the 16 research questions that apply.
13 of 16 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

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

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • Official site changesMeasuredRead 3d ago.

Contracts

  • Contract creationMeasuredRead 11h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 27m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 5h 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: 0xfcc7…e1f0

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 Tokyo Futuro’s token deployed 0xfcc7…e1f0 on 2026-11-02. Read from the chain; the creating transaction is the evidence.

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

Contract deployment, recorded on chain · no release names it
What it names
A new contract. The chain record names no capability.
Stage
A contract on chain. A deployment says nothing about whether anything uses it.
Reported by
Recorded on chain. Independently recorded: HEY read it from the chain, not from the team.
Release and deployment
Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
Activity
0xfcc7…e1f0 (a contract the project’s deployer put up): 0 calls to its own functions and 0 ERC-20 token calls in 7 days to 2026-11-19. Whether calls succeeded is not measured. Calls come from addresses, not people.
When
The source dates it 2026-11-02 17:16 UTC; HEY first knew on 2026-11-03.
Not known
  • No source HEY holds names what this change does.
  • Not established: no release text HEY holds names this contract. Timing alone never links a release to a deployment.
  • Whether calls succeeded is not measured: failed transactions are not read.

Evidence: ship record

A contract record says what the chain shows about a contract. It is not a safety check, and it does not say who runs the contract.

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

Build timeline

  1. Deployed a new contract: 0xbaa2…9f8a

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0xbaa2…9f8a on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  2. Deployed a new contract: 0x750d…e8f6

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x750d…e8f6 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  3. Deployed a new contract: 0xf53d…6ef6

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0xf53d…6ef6 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  4. Deployed a new contract: 0x23b5…e2c8

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x23b5…e2c8 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  5. Deployed a new contract: 0x1323…4e2a

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x1323…4e2a on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  6. Deployed a new contract: 0x77d3…f5c4

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x77d3…f5c4 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  7. Deployed a new contract: 0x28c1…b34a

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x28c1…b34a on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  8. Deployed a new contract: 0xe770…afc4

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0xe770…afc4 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

Earlier ships (16)
  1. Deployed a new contract: 0x5831…62a2

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x5831…62a2 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  2. Deployed a new contract: 0x5a44…3f6a

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x5a44…3f6a on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  3. Deployed a new contract: 0x3a35…c150

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x3a35…c150 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  4. Deployed a new contract: 0x3ad9…3b4d

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x3ad9…3b4d on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  5. Deployed a new contract: 0x7e23…d860

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x7e23…d860 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  6. Deployed a new contract: 0x955a…da34

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x955a…da34 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  7. Deployed a new contract: 0x449f…391d

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x449f…391d on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  8. Deployed a new contract: 0x168a…213f

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x168a…213f on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  9. Deployed a new contract: 0x5156…4cb8

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x5156…4cb8 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  10. Deployed a new contract: 0xdf5c…6c49

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0xdf5c…6c49 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  11. Deployed a new contract: 0x69b9…54a1

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x69b9…54a1 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  12. 3 contracts deployed by the project’s deployer between 01:42:00 and 01:43:45 UTC on 30 Oct

    New contract

    Show all 3 contracts
    1. Deployed a new contract: 0x745e…6932

      New contractSource-backed

      The account that launched Tokyo Futuro’s token deployed 0x745e…6932 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x9a5f…fecd

      New contractSource-backed

      The account that launched Tokyo Futuro’s token deployed 0x9a5f…fecd on 2026-10-30. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0xec53…549d

      New contractSource-backed

      The account that launched Tokyo Futuro’s token deployed 0xec53…549d on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  13. Deployed a new contract: 0x6161…26fb

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x6161…26fb on 2026-10-30. Read from the chain; the creating transaction is the evidence.

  14. Deployed a new contract: 0x4e62…c2d5

    New contractSource-backed

    The account that launched Tokyo Futuro’s token deployed 0x4e62…c2d5 on 2026-10-30. Read from the chain; the creating transaction is the evidence.

Other changes on HEY’s record

50 changes on HEY’s record for Tokyo Futuro: 1 new Verified Builder or owner proof · 1 contract in use again or for the first time · 1 token check change · 1 new project on HEY · 46 other changes in 3 more kinds.

All 50 changes for Tokyo Futuro →

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

Build through the drawdown

Down 66.5% from the HEY-tracked high, with 1 counted ship since.

Deployed a new contract: 0xfcc7…e1f0 — 18d agoDeployed a new contract: 0xbaa2…9f8a — 21d agoDeployed a new contract: 0x750d…e8f6 — 21d agoDeployed a new contract: 0xf53d…6ef6 — 21d agoDeployed a new contract: 0x23b5…e2c8 — 21d agoDeployed a new contract: 0x1323…4e2a — 21d agoDeployed a new contract: 0x77d3…f5c4 — 21d agoDeployed a new contract: 0x28c1…b34a — 21d agoDeployed a new contract: 0xe770…afc4 — 21d agoDeployed a new contract: 0x5831…62a2 — 21d agoDeployed a new contract: 0x5a44…3f6a — 21d agoDeployed a new contract: 0x3a35…c150 — 21d agoDeployed a new contract: 0x3ad9…3b4d — 21d agoDeployed a new contract: 0x7e23…d860 — 21d agoDeployed a new contract: 0x955a…da34 — 21d agoDeployed a new contract: 0x449f…391d — 21d agoDeployed a new contract: 0x168a…213f — 21d agoDeployed a new contract: 0x5156…4cb8 — 21d agoDeployed a new contract: 0xdf5c…6c49 — 21d agoDeployed a new contract: 0x69b9…54a1 — 21d agoDeployed a new contract: 0x745e…6932 — 21d agoDeployed a new contract: 0x9a5f…fecd — 21d agoDeployed a new contract: 0xec53…549d — 21d agoDeployed a new contract: 0x6161…26fb — 21d agoDeployed a new contract: 0x4e62…c2d5 — 21d ago$287K
Fully diluted valuation over time. Each marker is a meaningful ship.

A factual observation about past activity and market context. It is not a prediction, and not investment advice.

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

Contract 0x6354a37799e96ed6CCaeCfFbE1c100FA7F30cec8 on Robinhood Chain

0x6354…cec80x6354a37799e96ed6ccaecffbe1c100fa7f30cec8

Project names this contract.

Market context

Active market · FDV (fully diluted) $81.3K · current liquidity $17.6K · reading under an hour old (DEX Screener).

Token

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

Market

24h volume
$2.7K
Trades 24h
46 buys · 10 sells
Price 24h
up 29.6 percent over 24 hours· 6hdown 2.0 percent over 6 hours

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Market history, trading and checks →

Market integrity

Liquidity is 49% below the level it held two days running ($34.6K, 2026-10-31).

Market
Active market
Last day with trading
2026-11-19

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

Sources

13 places HEY reads for Tokyo Futuro