Skip to content
HEY Research Lab
Menu

TeraWallet

RWA

Not named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0x3c12e57fa7817a86ce7c254db9ea5fe639e233f8

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

Is this your project? Claim it →

Tera Wallet is a self-custodial wallet for tokenized real-world assets on @RobinhoodApp’s Robinhood Chain. Before a trade moves, it checks the asset, its eligibility, the route, price and limits you set. AI can help prepare an idea, but it cannot access your keys or execute a trade without your approval.

Read more

What HEY knows

Development

Shipping consistentlyShipping: 4 counted ships in 30 days; latest ship 5 days ago. Evidence Source

Build Momentum 51How it is measured

Latest: Code changes this week (since Mon 26 Oct) · 22 commits

Token market · context

Trading inactive

Same ticker, different contract: 1 other published project uses the ticker $TERA. This page: 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

Not named by the project
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me TeraWallet’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 — the token is not tied to the project. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 688 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
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.
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: 4 counted ships in the last 30 days, the newest 2026-10-27.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 22 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 48 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 45 commits+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.
Source5 registered sources, 1 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 22 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 48 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 45 commits+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.
Not named by the project.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: HEY knows it from a launchpad record, and the site that record named 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.
Trading inactive.
Trading inactive: the pool holds liquidity, but nothing 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 “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.
Discovery Gap: Not measured — the token is not tied to the project.
Not measured — the token is not tied to the project: the project does not name the tracked token and another published project's token carries the same ticker, so HEY cannot tell it from a lookalike and does not measure its market as the project's.
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 — the token is not tied to the project.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 16 of the 19 research questions that apply.
16 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 13m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 36d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d ago.

Contracts

  • Contract creationMeasuredRead 3h ago.
  • Contract activityMeasuredRead 2d ago.
  • Published source codeMeasuredRead 15h ago.
  • Contract interfaceMeasuredRead 15h ago.

Market

  • Current marketMeasuredRead 4h ago.
  • Market historyMeasuredRead yesterday.
  • Supply distributionMeasuredRead 3d ago.
  • LocksMeasuredRead 5h 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.

Market figures are context only and never change activity status. Methodology
LinksWebsite (context only) (opens in a new tab)GitHub (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

Checked

Code changes this week (since Mon 26 Oct) · 22 commits

Code activitySource-backed

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

What changed, in the repository’s own words:

2 active days in terawalletrh/terawallet.

This week HEY looked inside 1 of 22 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-10-27; HEY first knew on 2026-10-26.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)

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

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-19 – 2026-10-25 · 48 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in terawalletrh/terawallet.

    How HEY read this week

    This week HEY looked inside 3 of 48 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 48 commits (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 45 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in terawalletrh/terawallet.

    How HEY read this week

    This week HEY looked inside 3 of 45 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 45 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 58 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in terawalletrh/terawallet.

    How HEY read this week

    This week HEY looked inside 3 of 58 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 58 commits (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 142 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in terawalletrh/terawallet.

    How HEY read this week

    This week HEY looked inside 3 of 142 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 142 commits (opens in a new tab)

  5. Tera Android

    GitHub releaseSource-backed

    Latest signed Android release. It installs over Tera Wallet (app.terawallet.android) only.

    View evidence: Tera Android (opens in a new tab)

Other changes on HEY’s record

11 changes on HEY’s record for TeraWallet: 1 release · 1 new Verified Builder or owner proof · 1 market check · 3 market moves · 5 other changes in 1 more kind.

All 11 changes for TeraWallet →

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

0x3c12…33f80x3c12e57fa7817a86ce7c254db9ea5fe639e233f8

Not named by the project.

Market context

Trading inactive · the tracked token's FDV (fully diluted) $43.5K, not the project's valuation: the project does not name this token and another published project’s token carries the same ticker, so HEY cannot tell it from a lookalike.

Token

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

Market

Liquidity
$24K
24h volume
$0
Trades 24h
0 buys · 0 sells
Price 24h
unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

The tracked token has liquidity but recorded no trades in the last 24 hours.

Read from GeckoTerminal, 4h ago.

Market history, trading and checks →

Market integrity

Liquidity is 7% below the level it held two days running ($25.5K, 2026-10-17).

Market
Trading inactive
Last day with trading
2026-10-30
  1. seen 2026-09-25Trading fell from 2,422 trades a day (the seven days to 2026-09-17) to 143 a day in the seven days to 2026-09-26, in HEY's decoded on-chain trades.

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-01 00:53 UTC · How HEY checks this

Questions HEY can answer about TeraWallet — as of 1 Nov

Show the answers
Is TeraWallet still being built?
DerivedShipping: 4 counted ships in 30 days; latest ship 5 days ago. Evidence
What did TeraWallet ship last?
FactCode changes this week (since Mon 26 Oct) · 22 commits — Code activity, 5 days ago. Evidence
Is 0x3c12E57fa7817a86CE7C254dB9Ea5Fe639e233F8 TeraWallet’s own contract?
UnknownNot named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Details
What does HEY not know about TeraWallet?
Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.

Sources

5 places HEY reads for TeraWallet