Skip to content

Relay Settlement

Payments

Is this your project? Claim and verify →

Multi-chain settlement protocol — smart contracts and TypeScript SDK

What HEY knows

Building
Quiet for 38 daysQuiet: 0 meaningful events in 30 days; latest ship 38 days ago. Evidence Source

Build Momentum 17How it is measured

Latest ship
v0.0.7 · · GitHub release

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

Latest change
Derived38 days ago: Code changes, week of 2026-09-07 – 2026-09-13. Not counted as building. Evidence Source

Follow puts Relay Settlement 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 Relay Settlement’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
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-11.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.0.7v0.0.6v0.0.4+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".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsv0.0.7v0.0.6v0.0.4+3 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

Latest ship

Checked

v0.0.7

GitHub releaseSource verified

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

Shared change · Release

Relay Settlement shipped v0.0.6.

Builder status: Quiet.

Dated 2026-09-01 by the sourceSource: github

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.

Questions HEY can answer about Relay Settlement — as of 2026-10-19

Is Relay Settlement still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 38 days ago. Evidence
What did Relay Settlement ship last?
Factv0.0.7 — GitHub release, 38 days ago. Evidence
What does HEY not know about Relay Settlement?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

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

    Code activitySource linked

    1 active day in relayprotocol/relay-settlement.

    Automated commits only — not counted as building. 1 automated commit (bot accounts or a repeating scripted message) not counted.

  2. 2 releases in relayprotocol/relay-settlement on 1 Sep

    GitHub release

    Show all 2 releases
    1. v0.0.6

      GitHub releaseSource verified

    2. v0.0.5

      GitHub releaseSource verified

  3. Code changes, week of 2026-08-31 – 2026-09-06

    Code activitySource linked

    6 active days in relayprotocol/relay-settlement.

    Automated commits only — not counted as building. 2 automated commits (bot accounts or a repeating scripted message) not counted.

  4. v0.0.4

    GitHub releaseSource verified

  5. v0.0.3

    GitHub releaseSource verified

    Stork ingester service · Price oracle IPC v2 migration · Stork provider smart contracts Show all
    • Stork ingester service
    • Price oracle IPC v2 migration
    • Stork provider smart contracts
  6. v0.0.2

    GitHub releaseSource verified

  7. v0.0.1

    GitHub releaseSource verified

    Public release test from current main.

  8. v0.0.0-test

    GitHub releaseSource verified

    Initial test for public release

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Relay Settlement? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

10 changes on HEY’s record for Relay Settlement: 8 releases · 2 weeks of code pushed.

All 10 changes for Relay Settlement →

The full change record holds 3 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 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 6h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d 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