Skip to content
Menu

ripples-dot-run contracts

Launchpad

Is this your project? Claim and verify →

Solidity source for the Ripples launchpad on Robinhood Chain

What HEY knows

Building
Last shipped 18 days agoActive: 1 meaningful event in 30 days; latest ship 18 days ago. Evidence Source

Build Momentum 26How it is measured

Latest ship
Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits · · Code activity

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

Latest change
Fact13 days ago: Official sitemap changed: 1 section added, 0 removed. Added section: ripples.run/wake. Evidence Source

Official site change, on the project’s own site · not an implementation HEY has seen

What this change is
What it names
Official sitemap changed: 1 section added, 0 removed. Added section: ripples.run/wake.
Stage
A change to what the site says is not an implementation: HEY has not observed code, a release or a deployment for it.
Reported by
On the project’s own site. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or 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
No source dates it: HEY first saw it on 2026-10-12.
Not known
  • HEY has not observed a deployment of this change.
  • No source dates it; when it happened is not known.

Evidence: sourcechange record

It says what HEY read in a public source. A source on record does not prove who runs the project.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts ripples-dot-run contracts 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 ripples-dot-run contracts’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.

Token market · context
No token tracked
Not yet known
Unknown1 gap: API description (no source). Its website links no API description.

HEY can answer 9 of the 10 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
Active.
“Active” by the activity rule: 1 meaningful event in the last 30 days, the newest 2026-10-07.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitCode changes, week of 2026-09-07 – 2026-09-13 · at least 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source4 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitCode changes, week of 2026-09-07 – 2026-09-13 · at least 1 commit+2 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.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in ripples-dot-run/contracts.

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

Record ship:d649d0b5… · 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)

Shared change · Official source change

ripples-dot-run contracts' official site changed.

Official sitemap changed: 1 section added, 0 removed. Added section: ripples.run/wake.

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

View evidence ↗Evidence receipt

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.

Questions HEY can answer about ripples-dot-run contracts — as of 25 Oct

Is ripples-dot-run contracts still being built?
DerivedActive: 1 meaningful event in 30 days; latest ship 18 days ago. Evidence
What did ripples-dot-run contracts ship last?
FactCode changes, week of 2026-10-05 – 2026-10-11 · 2 commits — Code activity, 18 days ago. Evidence
What does HEY not know about ripples-dot-run contracts?
Unknown1 gap: API description (no source). Its website links no API description. Details

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-09-21 – 2026-09-27 · 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in ripples-dot-run/contracts.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in ripples-dot-run/contracts.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commit (opens in a new tab)

What changed

6 changes on HEY’s record for ripples-dot-run contracts: 3 official source changes · 3 weeks of code pushed.

All 6 changes for ripples-dot-run contracts →

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 can answer 9 of the 10 research questions that apply.

9 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsMeasuredRead 6h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

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

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, 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

Security context: a published security contact. An audit shows an audit took place; it is not a guarantee of safety.