Skip to content

Damkeeper

$DAM

Contract 0x70ecc8a7af0c97bd5b5a420ffd35b5e693f4e4b4

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

Is this your project? Claim it →

Inspired by Streamflow on Solana. Built for Robinhood Chain. Lock tokens for a flat 0.0007 ETH, choose the release date, and share verifiable onchain proof.

What HEY knows

Development

Not measuredBuilder sources stopped answering

HEY cannot read this project’s building: its repository stopped answering on 21 Oct 2026.

Build Momentum not measured

Latest: Code changes, week of 2026-10-12 – 2026-10-18 · 23 commits

Token market · context

Trading inactive

Same ticker, different contract: 1 other published project uses the ticker $DAM. This page: its site damkeeper.xyz names 0x70ec…e4b4. Modam: its site modam.tech does not name 0x7c65…a0e2. 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 Damkeeper 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 Damkeeper

No account? Email me Damkeeper’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 — see market. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 6 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
Unknown5 gaps: Repositories (source unavailable), Releases (source unavailable), Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Every repository HEY holds has stopped answering.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Not measured — builder sources stopped answering.
HEY cannot read this project’s building: its repository stopped answering on 21 Oct 2026. No counted ship is dated since, so after 21 days the status is unknown, not dormant; the ships HEY counted before stay on the timeline.
SourceThe repositories, changelogs and feeds HEY read for this project, every one now unavailable, and the ship events recorded from them before.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 23 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 19 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 48 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Not measured — builder sources stopped answering”.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".
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.
Trading inactive.
Trading inactive: the only pool is the launch pool holding the token’s own supply, and nothing traded in it in the last day.
Source8 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 — see market.
Not measured — see market: the tracked token has no live market, so it has no market-attention percentile.
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 — see market.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Build Momentum not measured.
Every repository, changelog or feed HEY read this project’s building from stopped answering, so no score is published.
Research coverage: HEY cannot answer whether anyone is building this yet (building activity: source unavailable); it can answer 11 of the 17 research questions that apply.
11 of 17 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activitySource unavailableEvery builder source HEY holds has stopped answering.
  • RepositoriesSource unavailableEvery repository HEY holds has stopped answering.
  • ReleasesSource unavailableEvery builder source HEY holds has stopped answering.
  • TimelineMeasured

Official site

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

Contracts

  • Contract creationMeasuredRead 3d ago.
  • Contract activityMeasuredRead 4d ago.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 6h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 3d ago.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Not applicable here: 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

Code changes, week of 2026-10-12 – 2026-10-18 · 23 commits

Code activitySource-backed

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

2 active days in wealthy-org/damkeeper.

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

Record ship:b349afbd… · 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-17; HEY first knew on 2026-10-16.
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.

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-05 – 2026-10-11 · 19 commits

    Code activitySource-backed

    2 active days in wealthy-org/damkeeper.

    How HEY read this week

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

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 48 commits

    Code activitySource-backed

    5 active days in wealthy-org/damkeeper.

    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.

Other changes on HEY’s record

12 changes on HEY’s record for Damkeeper: 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 · 8 other changes in 2 more kinds.

All 12 changes for Damkeeper →

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

0x70ec…e4b40x70ecc8a7af0c97bd5b5a420ffd35b5e693f4e4b4

Project names this contract.

Market context

Trading inactive: HEY holds a valuation and does not publish it while the market is not live.

Token

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

Market

Valuation
Withheld — see market
Liquidity
Not a market reading
24h volume
$0
Trades 24h
0 buys · 0 sells
Price 24h
unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

The pool reports its liquidity as the token’s own supply at its last price, and recorded no trades in the last 24 hours. HEY does not read that reserve as liquidity.

Read from GeckoTerminal, 6h ago.

Market history, trading and checks →

Market integrity

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

Market
Trading inactive
Last day with trading
2026-11-14

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-18 06:59 UTC · How HEY checks this

Sources

3 places HEY reads for Damkeeper