Skip to content

Mancer

$mancer

Contract 0xc72f232a6869e6cf34dc06129affd07f8a2a246a

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

Is this your project? Claim it →

What HEY knows

Development

Shipped this weekShipping: 1 counted ship in 30 days; latest ship today. Evidence Source

Build Momentum 25How it is measured

Latest: Code changes this week (since Mon 2 Nov) · 4 commits

Token market · context

Active market$1.6M market cap

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me Mancer’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
Building and market attention rank about level among comparable projects: its building is ahead of 94% of them, its market attention ahead of 96.6% (a gap of -2.6). 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
Fact1 of 1 watched contract active · 23,778 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
Fact6 contracts on record for code changes, 1 with published source code; latest change on 2026-08-14: Deployed a new contract: 0x6a92…aeba. Source
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s 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: 1 counted ship in the last 30 days, the newest 2026-11-05. Not called Resumed: HEY began reading the source of the newest ships after the quiet stretch before them began, so it did not watch that gap.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 2 Nov) · 4 commitsDeployed a new contract: 0x6a92…aebaDeployed a new contract: 0x2e8e…36c8What 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.
Source16 registered sources, 0 of them context only.RecordsCode changes this week (since Mon 2 Nov) · 4 commitsDeployed a new contract: 0x6a92…aebaDeployed a new contract: 0x2e8e…36c8+5 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.
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.
Research coverage: HEY can answer 17 of the 19 research questions that apply.
17 of 19 applicable dimensions measured.

Identity

  • IdentityMeasured

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 20m ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 3d ago.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 56m ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 5d ago.
  • Contract interfaceMeasuredRead 5d ago.

Market

  • Current marketMeasuredRead just now.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 3d ago.
  • LocksMeasuredRead 1h 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

Latest ship

Checked

Code changes this week (since Mon 2 Nov) · 4 commits

Code activitySource-backed

Why it matters: First week of code changes after 83 quiet days.

3 active days in blockhash-xyz/mancer-sdk.

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

Record ship:e1ba715f… · 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-11-05; HEY first knew on 2026-11-02.
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.

Shared change · Official source change

Mancer's official site changed.

Links the official site declares changed: 3 added, 3 removed. Added docs link….

Observed by HEY on 2026-10-31Source: Project’s official site

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. Verified contract source published: CollectionToken

    Contract source publishedSource-backed

    CollectionToken at 0xc72f…246a has verified source on Robinhood Chain Blockscout (compiler v0.8.26+commit.8a97fa7a).

  2. Deployed a new contract: 0x6a92…aeba

    New contractSource-backed

    The account that launched Mancer’s token deployed 0x6a92…aeba on 2026-08-14. Read from the chain; the creating transaction is the evidence.

  3. 4 contracts deployed by the project’s deployer at 05:41:51 UTC on 14 Aug

    New contract

    Show all 4 contracts
    1. Deployed a new contract: 0x2e8e…36c8

      New contractSource-backed

      The account that launched Mancer’s token deployed 0x2e8e…36c8 on 2026-08-14. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0xbb56…97ae

      New contractSource-backed

      The account that launched Mancer’s token deployed 0xbb56…97ae on 2026-08-14. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0x5f3b…656e

      New contractSource-backed

      The account that launched Mancer’s token deployed 0x5f3b…656e on 2026-08-14. Read from the chain; the creating transaction is the evidence.

    4. Deployed a new contract: MancerFeeSplit

      New contractSource-backed

      The account that launched Mancer’s token deployed MancerFeeSplit at 0x0ffb…f975 on 2026-08-14. Read from the chain; the creating transaction is the evidence.

Other changes on HEY’s record

25 changes on HEY’s record for Mancer: 2 new Verified Builders or owner proofs · 1 token check change · 1 market check · 12 official source changes · 9 other changes in 3 more kinds.

All 25 changes for Mancer →

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

0xc72f…246a0xc72f232a6869e6cf34dc06129affd07f8a2a246a

Project names this contract.

Market context

Active market · market cap $1.6M · current liquidity $593K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
3mo ago

Market

Fully diluted valuation
$3.5M
24h volume
$71K
Trades 24h
242 buys · 325 sells
Price 24h
up 10.7 percent over 24 hours· 6hdown 0.1 percent over 6 hours· 1hdown 0.3 percent over 1 hour

The tracked token has liquidity and traded in the last 24 hours.

Market history, trading and checks →

Market integrity

Liquidity is 1% below the level it held two days running ($602.7K, 2026-09-21).

Market
Active market
Last day with trading
2026-11-04
  1. seen 2026-09-24Trading fell from 25,821 trades a day (the seven days to 2026-08-09) to 1,109 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-05 00:53 UTC · How HEY checks this

Sources

16 places HEY reads for Mancer
11 more sources (docs)