Skip to content

Reservum

$RESV

Contract 0x4d897bb08c5af792cf50451a20487d4f70f1f2b2

HEY holds 1 other Robinhood Chain token with the ticker $RESV. This page is only the contract above. See them

Is this your project? Claim it →

Reservum ($RESV) is a fixed-supply token on Robinhood Chain. Every trade pays a fee that automatically converts into ETH, held directly in the verified contract — no basket, no intermediary asset. Holders can redeem anytime for their pro-rata share of the reserve. 99% of coins can go to zero, Reservum has a floor that can only raise.

Read more

What HEY knows

Development

Not measuredActivity not measurableHEY has a ship on record (last ship on 2026-09-26) but no repository, changelog or feed it can keep reading, so no count here is a measured zero. Evidence

Latest: Deployed a new contract: 0x8dff…e85c

Token market · context

Launch pool only

Token check

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

Get updates

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

No account? Email me Reservum’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
Fact2 of 8 watched contracts active · 6 calls in 7 days (3 calls to the contracts' own functions; 3 ERC-20 token transfers and approvals, which trading alone produces).

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

Contracts
Fact28 contracts on record for code changes, 11 with published source code; latest change on 2026-09-26: Deployed a new contract: 0x8dff…e85c. 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
Not measured — 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: 0x8dff…e85cDeployed a new contract: 0xea38…f66dDeployed a new contract: 0x6043…05b5+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Not measured — 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".
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.
Source9 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.
Build Momentum not measurable.
HEY holds no public repository, changelog or feed it can read building from, so there is nothing to measure yet.
Research coverage: HEY cannot answer whether anyone is building this yet (building activity: no source); it can answer 12 of the 16 research questions that apply.
12 of 16 applicable dimensions measured.

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 docsNo sourceHEY read its website and found no link to docs.
  • Official site changesMeasuredRead 3d ago.

Contracts

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

Market

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

Latest ship

Deployed a new contract: 0x8dff…e85c

New contractSource-backed

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

The account that launched Reservum’s token deployed 0x8dff…e85c on 2026-09-26. Read from the chain; the creating transaction is the evidence.

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

Build timeline

  1. Deployed a new contract: 0xea38…f66d

    New contractSource-backed

    The account that launched Reservum’s token deployed 0xea38…f66d on 2026-09-19. Read from the chain; the creating transaction is the evidence.

  2. Deployed a new contract: 0x6043…05b5

    New contractSource-backed

    The account that launched Reservum’s token deployed 0x6043…05b5 on 2026-09-19. Read from the chain; the creating transaction is the evidence.

  3. Deployed a new contract: 0x3761…cea2

    New contractSource-backed

    The account that launched Reservum’s token deployed 0x3761…cea2 on 2026-09-19. Read from the chain; the creating transaction is the evidence.

  4. 2 contracts deployed by the project’s deployer between 15:53:44 and 15:53:46 UTC on 19 Sep

    New contract

    Show all 2 contracts
    1. Deployed a new contract: 0xb36c…60d1

      New contractSource-backed

      The account that launched Reservum’s token deployed 0xb36c…60d1 on 2026-09-19. Read from the chain; the creating transaction is the evidence.

    2. Deployed a new contract: 0x1bd5…9814

      New contractSource-backed

      The account that launched Reservum’s token deployed 0x1bd5…9814 on 2026-09-19. Read from the chain; the creating transaction is the evidence.

  5. Deployed a new contract: 0x83e1…d68a

    New contractSource-backed

    The account that launched Reservum’s token deployed 0x83e1…d68a on 2026-09-12. Read from the chain; the creating transaction is the evidence.

  6. Deployed a new contract: 0x2002…8575

    New contractSource-backed

    The account that launched Reservum’s token deployed 0x2002…8575 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

  7. 6 contracts deployed by the project’s deployer between 02:00:10 and 02:00:24 UTC on 12 Sep

    New contract

    Show all 6 contracts
    1. Deployed a new contract: 0xde81…321c

      New contractSource-backed

      The account that launched Reservum’s token deployed 0xde81…321c on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    2. Deployed a Uniswap v4 hook: 0xf5d9…c0cc

      New contractSource-backed

      The account that launched Reservum’s token deployed a Uniswap v4 hook at 0xf5d9…c0cc through a deterministic deployer on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0xf407…7de8

      New contractSource-backed

      The account that launched Reservum’s token deployed 0xf407…7de8 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    4. Deployed a new contract: 0xedb2…d7d5

      New contractSource-backed

      The account that launched Reservum’s token deployed 0xedb2…d7d5 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    5. Deployed a new contract: 0x3220…df19

      New contractSource-backed

      The account that launched Reservum’s token deployed 0x3220…df19 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    6. Deployed a new contract: DigitalFrontierIndex

      New contractSource-backed

      The account that launched Reservum’s token deployed DigitalFrontierIndex at 0x4280…c3f9 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

  8. 6 contracts deployed by the project’s deployer between 01:47:49 and 01:48:57 UTC on 12 Sep

    New contract

    Show all 6 contracts
    1. Deployed a new contract: 0x901f…62cd

      New contractSource-backed

      The account that launched Reservum’s token deployed 0x901f…62cd on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    2. Deployed a Uniswap v4 hook: 0xfdd5…00cc

      New contractSource-backed

      The account that launched Reservum’s token deployed a Uniswap v4 hook at 0xfdd5…00cc through a deterministic deployer on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    3. Deployed a new contract: 0x4f8d…91a7

      New contractSource-backed

      The account that launched Reservum’s token deployed 0x4f8d…91a7 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    4. Deployed a new contract: 0x5184…4224

      New contractSource-backed

      The account that launched Reservum’s token deployed 0x5184…4224 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    5. Deployed a new contract: 0xabed…78a2

      New contractSource-backed

      The account that launched Reservum’s token deployed 0xabed…78a2 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

    6. Deployed a new contract: DigitalFrontierIndex

      New contractSource-backed

      The account that launched Reservum’s token deployed DigitalFrontierIndex at 0xfdf1…3e84 on 2026-09-12. Read from the chain; the creating transaction is the evidence.

Earlier ships (5)
  1. Deployed a new contract: MemberBadge

    New contractSource-backed

    The account that launched Reservum’s token deployed MemberBadge at 0xc321…5da2 on 2026-09-10. Read from the chain; the creating transaction is the evidence.

  2. Deployed a new contract: MemberBoard

    New contractSource-backed

    The account that launched Reservum’s token deployed MemberBoard at 0xec5b…fd6e on 2026-09-09. Read from the chain; the creating transaction is the evidence.

  3. Deployed a new contract: HighWaterLeaderboard

    New contractSource-backed

    The account that launched Reservum’s token deployed HighWaterLeaderboard at 0x7005…c16c on 2026-09-09. Read from the chain; the creating transaction is the evidence.

  4. Deployed a new contract: 0x21a5…3559

    New contractSource-backed

    The account that launched Reservum’s token deployed 0x21a5…3559 on 2026-09-09. Read from the chain; the creating transaction is the evidence.

  5. Deployed a new contract: SellHelper

    New contractSource-backed

    The account that launched Reservum’s token deployed SellHelper at 0x84f2…07a3 on 2026-09-03. Read from the chain; the creating transaction is the evidence.

Other changes on HEY’s record

36 changes on HEY’s record for Reservum: 1 new Verified Builder or owner proof · 1 new project on HEY · 26 contract changes · 2 build pace changes · 6 other changes in 2 more kinds.

All 36 changes for Reservum →

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

0x4d89…f2b20x4d897bb08c5af792cf50451a20487d4f70f1f2b2

Project names this contract.

Market context

Launch pool only · FDV (fully diluted) $846 · liquidity $1.2K (launch pool inventory, not a market) · reading 1 h old (GeckoTerminal).

Token

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

Market

24h volume
$0
The market status rests on $3 of trading volume HEY read within a day of this reading, from another reading or its record of on-chain trades — not on this reading’s own figure.
Trades 24h
0 buys · 0 sells
Price 24h
unchanged over 24 hours· 6hunchanged over 6 hours· 1hunchanged over 1 hour

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

5 places HEY reads for Reservum

2 Uniswap v4 hooks HEY ties to this project · Builders shipping Uniswap v4 hooks