Skip to content
Menu

Sluice Xyz

Data

Is this your project? Claim and verify →

Per-second money streaming on Robinhood Chain — the SluiceStream contract, @sluice/sdk and docs for Sluice ($SLU).

What HEY knows

Building
Dormant: no ship for 88 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-07-22. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-20 – 2026-07-26 · 2 commits · · Code activity

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Sluice Xyz 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 Sluice Xyz’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 (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.

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
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-07-22.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-20 – 2026-07-26 · 2 commitsv0.2.0 — SDK + docsv0.1.0 — reference contract+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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.
Source7 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-07-20 – 2026-07-26 · 2 commitsv0.2.0 — SDK + docsv0.1.0 — reference contract+6 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
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-07-20 – 2026-07-26 · 2 commitssluice-xyz/sluice-protocol

Code activitySource linked

What changed, in the repository’s own words:

1 active day in sluice-xyz/sluice-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:82ac41c2… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Release

Sluice Xyz shipped v0.1.0 — reference contract.

Builder status: Dormant.

Dated 2026-07-22 by the sourceSource: github

View evidence ↗Evidence receipt

Builder activity

No meaningful, source-backed updates in the 7 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

Questions HEY can answer about Sluice Xyz — as of 2026-10-18

Is Sluice Xyz still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-22. Evidence
What did Sluice Xyz ship last?
FactCode changes, week of 2026-07-20 – 2026-07-26 · 2 commits — Code activity, on 2026-07-22. Evidence
What does HEY not know about Sluice Xyz?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer. Details

Build timeline

  1. v0.2.0 — SDK + docssluice-xyz/sluice-protocol

    GitHub releaseSource verified

    @sluice/sdk typed client, realtimeBalanceOf/netFlowRate wired, full docs, community files. Unaudited reference — not for mainnet.

    View evidence

  2. v0.1.0 — reference contractsluice-xyz/sluice-protocol

    GitHub releaseSource linked

    First public cut: SluiceStream contract, interface, Foundry tests, CI, MIT. Unaudited reference — not for mainnet.

    View evidence

  3. Code changes, week of 2026-07-20 – 2026-07-26 · at least 1 commitsluice-xyz/sluice-sdk

    Code activitySource linked

    1 active day in sluice-xyz/sluice-sdk.

    This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. Only part of this week's commits were listed, so the week is not called documentation only.

    View evidence

  4. Code changes, week of 2026-07-20 – 2026-07-26 · 1 commitsluice-xyz/sluice-docs

    Code activitySource linked

    1 active day in sluice-xyz/sluice-docs.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    View evidence

  5. Code changes, week of 2026-07-20 – 2026-07-26 · at least 1 commitsluice-xyz/awesome-sluice

    Code activitySource linked

    3 active days in sluice-xyz/awesome-sluice.

    This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. Only part of this week's commits were listed, so the week is not called documentation only.

    View evidence

  6. Code changes, week of 2026-07-13 – 2026-07-19 · at least 3 commitssluice-xyz/sluice-subgraph

    Code activitySource linked

    1 active day in sluice-xyz/sluice-subgraph.

    This week HEY looked inside 3 commits to see what changed: 3 documentation or maintenance only. Only part of this week's commits were listed, so the week is not called documentation only.

    View evidence

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 Sluice Xyz? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

8 changes on HEY’s record for Sluice Xyz: 2 releases · 1 build pace change · 5 weeks of code pushed.

All 8 changes for Sluice Xyz →

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 2d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • 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.

Code and packages

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