Skip to content
HEY Research Lab
Menu

TERA

$TERA

AI Agents

Contract 0x06877aabe5191c394fe35c5323893c2e65f2c80a

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

Is this your project? Claim it →

$TERA is a 3D city on Robinhood Chain where people and AI agents play side by side. Explore the streets, chase down Czar in the daily Czar Run, and build out your Land.

What HEY knows

Development

Last shipped 3 days agoShipping: 9 counted ships in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 63How it is measured

Latest: Deployed a new contract: 0x843b…779c

Token market · context

Launch pool only

Same name, different contract: 3 other published projects use the name TERA and the ticker $TERA. This page: its site teraworld.xyz names 0x0687…c80a. Tera: its site teramap.fun does not name 0xd733…8217; TeraWallet: its site terawallet.app does not name 0x3c12…33f8; Agent Tera by Virtuals: its site teraperp.com does not name 0x09dc…a05f. HEY does not say which is the real one — only what each project’s own sources name.

Token check

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

Get updates

Follow puts TERA 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 TERA

No account? Email me TERA’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
Discovery Gap not measured — 24h volume under $1,000. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 7 calls to the contracts' own functions over the 3 of 7 days HEY holds; the other 308 of 315 calls were ERC-20 token transfers and approvals, which trading alone produces; the rest unknown, not zero.

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

Contracts
Fact1 contract on record for code changes, 1 with published source code; latest change 3 days ago: Deployed a new contract: 0x843b…779c. 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
Shipping.
“Shipping” by the activity rule: 9 counted ships in the last 30 days, the newest 2026-11-06.
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: 0x843b…779cDeployed a new contract: 0x3a10…7704Deployed a new contract: 0xc540…be84+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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.
Source4 registered sources, 0 of them context only.ReadRecordsDeployed a new contract: 0x843b…779cDeployed a new contract: 0x3a10…7704Deployed a new contract: 0xc540…be84+6 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.
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 13 of the 16 research questions that apply.
13 of 16 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 7d 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 12h ago.

Contracts

  • Contract creationMeasuredRead 13h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 12h ago.
  • Contract interfaceMeasuredRead 12h ago.

Market

  • Current marketMeasuredRead 17m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead today.
  • LocksMeasuredRead 33m 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
LinksWebsite (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Deployed a new contract: 0x843b…779c

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 TERA’s token deployed 0x843b…779c on 2026-11-06. Read from the chain; the creating transaction is the evidence.

Record ship:270dee54… · 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
HEY does not count calls to 0x843b…779c (a contract HEY does not hold for this project) for this project. Its activity is not measured, not zero.
When
The source dates it 2026-11-06 17:44 UTC; HEY first knew on 2026-11-09.
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.
  • HEY does not count calls to 0x843b…779c (a contract HEY does not hold for this project) for this project. Its activity is not measured, not zero.

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.

View evidence ↗ (opens in a new tab)

Shared change · Verified Builder

TERA is now a Verified Builder: HEY checked its builder sources.

9 meaningful development events were recorded in the last 30 days. Builder status: Shipping.

Observed by HEY on 2026-11-09Source: HEY’s research record

Evidence receipt

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

Build timeline

  1. Deployed a new contract: 0x3a10…7704

    New contractSource-backed

    The account that launched TERA’s token deployed 0x3a10…7704 on 2026-11-06. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x3a10…7704 (opens in a new tab)

  2. Deployed a new contract: 0xc540…be84

    New contractSource-backed

    The account that launched TERA’s token deployed 0xc540…be84 on 2026-11-06. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xc540…be84 (opens in a new tab)

  3. Deployed a new contract: 0x42b0…6bef

    New contractSource-backed

    The account that launched TERA’s token deployed 0x42b0…6bef on 2026-11-06. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x42b0…6bef (opens in a new tab)

  4. 2 contracts deployed by the project’s deployer between 15:18:15 and 15:18:16 UTC on 6 Nov

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0xa073…0e9b

      New contractSource-backed

      The account that launched TERA’s token deployed 0xa073…0e9b on 2026-11-06. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xa073…0e9b (opens in a new tab)

    2. Deployed a new contract: 0x3747…a5fe

      New contractSource-backed

      The account that launched TERA’s token deployed 0x3747…a5fe on 2026-11-06. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x3747…a5fe (opens in a new tab)

  5. Deployed a new contract: 0x2470…bfc7

    New contractSource-backed

    The account that launched TERA’s token deployed 0x2470…bfc7 on 2026-11-06. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x2470…bfc7 (opens in a new tab)

  6. 2 contracts deployed by the project’s deployer between 17:16:28 and 17:16:31 UTC on 4 Nov

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0xcd05…8479

      New contractSource-backed

      The account that launched TERA’s token deployed 0xcd05…8479 on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xcd05…8479 (opens in a new tab)

    2. Deployed a new contract: 0x7567…9325

      New contractSource-backed

      The account that launched TERA’s token deployed 0x7567…9325 on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x7567…9325 (opens in a new tab)

  7. 2 contracts deployed by the project’s deployer between 16:55:54 and 16:55:57 UTC on 4 Nov

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0x5c6d…5e90

      New contractSource-backed

      The account that launched TERA’s token deployed 0x5c6d…5e90 on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x5c6d…5e90 (opens in a new tab)

    2. Deployed a new contract: 0xdad1…f917

      New contractSource-backed

      The account that launched TERA’s token deployed 0xdad1…f917 on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xdad1…f917 (opens in a new tab)

  8. 2 contracts deployed by the project’s deployer between 16:39:54 and 16:39:58 UTC on 4 Nov

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0x661e…610f

      New contractSource-backed

      The account that launched TERA’s token deployed 0x661e…610f on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x661e…610f (opens in a new tab)

    2. Deployed a new contract: 0x66ae…2576

      New contractSource-backed

      The account that launched TERA’s token deployed 0x66ae…2576 on 2026-11-04. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x66ae…2576 (opens in a new tab)

Other changes on HEY’s record

15 changes on HEY’s record for TERA: 1 new Verified Builder or owner proof · 1 new project on HEY · 13 contract changes.

All 15 changes for TERA →

The full change record holds 2 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 0x06877Aabe5191C394Fe35C5323893C2e65F2C80A on Robinhood Chain

0x0687…c80a0x06877aabe5191c394fe35c5323893c2e65f2c80a

Project names this contract.

Market context

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

Token

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

Market

24h volume
$376
Trades 24h
5 buys · 5 sells
Price 24h
down 16.8 percent over 24 hours· 6hdown 2.8 percent over 6 hours

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 →

Sources

4 places HEY reads for TERA