Skip to content
HEY Research Lab
Menu

Ripe Protocol

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

What HEY knows

Development

Quiet for 38 daysQuiet: 0 counted ships in 30 days; latest ship 38 days ago. Evidence Source

Build Momentum 18How it is measured

Latest: Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Ripe Protocol 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 Ripe Protocol

No account? Email me Ripe Protocol’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
Product usage

Ripe Protocol: TVL $98.9K · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-10-29). Registry context, not a measure of building.

Not yet known
Unknown3 gaps: API description (no source), Official site changes (no source), Protocol economics (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-21.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 2 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitsTeller and Credit Engine fixes+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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".
Research coverage: HEY can answer 8 of the 11 research questions that apply.
8 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 49d ago.

Building

  • Building activityMeasuredRead 10h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1y ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1d ago.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

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

Protocol economics

  • Protocol economicsNo sourceDefiLlama lists the protocol but tracks no fees, revenue or volume for it.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks.

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
LinksGitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits

Code activitySource-backed

What changed, in the repository’s own words:

1 active day in ripe-foundation/ripe-protocol.

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:3c4d9fae… · HEY counts it as building; it does not judge the release’s quality.

View evidence ↗ (opens in a new tab)

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: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

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-07 – 2026-09-13 · at least 2 commits

    Code activitySource-backed

    7 active days in Ripe-Foundation/ripe-protocol.

    How HEY read this week

    HEY has not looked inside this week’s commits yet.

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

  2. Teller and Credit Engine fixes

    GitHub releaseSource-backed

    View evidence: Teller and Credit Engine fixes (opens in a new tab)

  3. New Curve Prices

    GitHub releaseSource-backed

    View evidence: New Curve Prices (opens in a new tab)

  4. BondRoom updates

    GitHub releaseSource-backed

    View evidence: BondRoom updates (opens in a new tab)

  5. Update Underscore Integration

    GitHub releaseSource-backed

    View evidence: Update Underscore Integration (opens in a new tab)

  6. BondRoom update to restart epoch at the endBlock

    GitHub releaseSource-backed

    View evidence: BondRoom update to restart epoch at the endBlock (opens in a new tab)

  7. Switchboard Delta Bond Booster fix

    GitHub releaseSource-backed

    View evidence: Switchboard Delta Bond Booster fix (opens in a new tab)

  8. Redeploy LootBox to reset points

    GitHub releaseSource-backed

    View evidence: Redeploy LootBox to reset points (opens in a new tab)
Earlier ships (4)

  1. RIPE token initial params

    GitHub releaseSource-backed

    View evidence: RIPE token initial params (opens in a new tab)

  2. New Endaoment

    GitHub releaseSource-backed

    View evidence: New Endaoment (opens in a new tab)

  3. Curve Prices Update

    GitHub releaseSource-backed

    View evidence: Curve Prices Update (opens in a new tab)

  4. Ripe Protocol - Base Mainnet - v1

    GitHub releaseSource-backed

    View evidence: Ripe Protocol - Base Mainnet - v1 (opens in a new tab)

Questions HEY can answer about Ripe Protocol — as of 29 Oct

Show the answers
Is Ripe Protocol still being built?
DerivedQuiet: 0 counted ships in 30 days; latest ship 38 days ago. Evidence
What did Ripe Protocol ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 2 commits — Code activity, 38 days ago. Evidence
What does HEY not know about Ripe Protocol?
Unknown3 gaps: API description (no source), Official site changes (no source), Protocol economics (no source). No official website on record.

Sources

16 places HEY reads for Ripe Protocol
10 more sources (docs)