Skip to content
Menu

clan.tech

$clan

Meme

Contract 0xcebc0cfbc5dd0893a9e3b9d0f75b211ddf5934a0

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

Is this your project? Claim and verify →

What HEY knows

Building
Activity not measurableHEY has a ship on record (last ship on 2026-09-03) but no repository, changelog or feed it can keep reading, so no count here is a measured zero. Evidence
Latest ship
Deployed a new contract: 0x25f8…326c
This change
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
0x25f8…326c (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-10-27. Whether calls succeeded is not measured. Calls come from addresses, not people.
When
The source dates it 2026-09-03 20:48 UTC; HEY first knew on 2026-09-12. HEY indexed it later, as history.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts clan.tech 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 clan.tech’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 — market too thin. What the Discovery Gap is
Product usage
Fact1 of 2 watched contracts active · 9,762 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
Fact4 contracts on record for code changes, 1 with verified source; latest change on 2026-09-03: Deployed a new contract: 0x25f8…326c. Source
Token market · context
Active market$16K fully diluted valuationToken verified
Not yet known
Unknown5 gaps: Building activity (no source), Repositories (no source), Releases (no source), Official docs (source unavailable), Official site changes (source unavailable). No repository, changelog or feed to read.

HEY cannot answer whether anyone is building this yet (building activity: no source); it can answer 11 of the 16 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
Activity not measurable.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadRecordsDeployed a new contract: 0x25f8…326cDeployed a new contract: 0xc98c…d559What HEY derivedHEY’s activity rule reads the counted events as “Activity not measurable”.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.
Source2 registered sources, 0 of them context only.ReadRecordsDeployed a new contract: 0x25f8…326cDeployed a new contract: 0xc98c…d559source:7785299a-7910-4180-b757-73bf517ae37b+1 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.
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.
Active market.
Active market: the pool holds liquidity and the token 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 “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.
Discovery Gap: Not measured — market too thin.
Not measured — market too thin: the tracked token's market reads “Active market” but traded $207.24 in the 24 hours of its reading, under the $1,000 a measured market needs. 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.
Build Momentum not measurable.
HEY holds no public repository, changelog or feed it can read building from, so there is nothing to measure yet.
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: 0x25f8…326c

New contractSource verified

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

The account that launched clan.tech’s token deployed 0x25f8…326c on 2026-09-03. Read from the chain; the creating transaction is the evidence.

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

View evidence ↗ (opens in a new tab)

Questions HEY can answer about clan.tech — as of 28 Oct

Is clan.tech still being built?
UnknownActivity not measurable: HEY has a ship on record (last ship on 2026-09-03) but no repository, changelog or feed it can keep reading, so no count here is a measured zero. Evidence
What did clan.tech ship last?
FactDeployed a new contract: 0x25f8…326c — New contract, on 2026-09-03. Evidence
Is 0xCEbc0cFbc5DD0893A9E3B9D0f75b211DDf5934A0 clan.tech’s own contract?
FactToken verified: The project’s own site names this contract. Details
What does HEY not know about clan.tech?
Unknown5 gaps: Building activity (no source), Repositories (no source), Releases (no source), +2 more. No repository, changelog or feed to read. Details

Build timeline

  1. Deployed a new contract: 0x0860…f2a7

    New contractSource verified

    The account that launched clan.tech’s token deployed 0x0860…f2a7 on 2026-09-03. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x0860…f2a7 (opens in a new tab)

  2. Deployed a new contract: 0xc98c…d559

    New contractSource verified

    The account that launched clan.tech’s token deployed 0xc98c…d559 on 2026-09-03. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0xc98c…d559 (opens in a new tab)

What changed

8 changes on HEY’s record for clan.tech: 1 contract in use again or for the first time · 1 market check · 3 contract changes · 3 market moves.

All 8 changes for clan.tech →

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

Research coverage

HEY cannot answer whether anyone is building this yet (building activity: no source); it can answer 11 of the 16 research questions that apply.

11 of 16 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityNo sourceNo repository, changelog or feed to read.
  • RepositoriesNo sourceNo repository the project claims as its own.
  • ReleasesNo sourceNo repository, changelog or feed to read.
  • TimelineMeasured

Official site

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

Contracts

  • Contract creationMeasuredRead 4d ago.
  • Contract activityMeasuredRead yesterday.
  • Verified sourceMeasuredRead 4d ago.
  • Contract interfaceMeasuredRead 4d ago.

Market

  • Current marketMeasuredRead 9m ago.
  • Market historyMeasuredRead today.
  • 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.

Sources

Contract
0xcebc…34a00xcebc0cfbc5dd0893a9e3b9d0f75b211ddf5934a0