Skip to content
HEY Research Lab
Menu

Verifiable Randomness Raffle Protocol

Is this your project? Claim it →

Smart contract for Winr.fun, a verifiable decentralized raffle protocol built for Robinhood chain using Quiver VRF for randmness

What HEY knows

Development

Last shipped 37 days agoActive: 0 counted ships in 30 days; latest ship 37 days ago. Evidence Source

Build Momentum 16How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 3 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Verifiable Randomness Raffle 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 Verifiable Randomness Raffle Protocol

No account? Email me Verifiable Randomness Raffle 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.

More detail
Not yet known
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.
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's longer window: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-10-01, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 3 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 3 commitsWhat 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 counted building from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 3 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 3 commitssource:4983cfb8-a469-4708-bfc9-162d4f5807c7What 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.
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 3h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 3d ago.
  • Published packagesMeasuredRead 3d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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.

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-09-28 – 2026-10-04 · 3 commits

Code activitySource-backed

What changed, in the repository’s own words:

1 active day in reinhartsamuel/verifiable-randomness-raffle-protocol.

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

Record ship:1c47ad32… · 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: 5 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-10-05 – 2026-10-11 · 1 commit

    Code activitySource-backed

    1 active day in reinhartsamuel/verifiable-randomness-raffle-protocol.

    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: Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit (opens in a new tab)

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in reinhartsamuel/verifiable-randomness-raffle-protocol.

    How HEY read this week

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

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

Other changes on HEY’s record

4 changes on HEY’s record for Verifiable Randomness Raffle Protocol: 1 new Verified Builder or owner proof · 3 weeks of code pushed.

All 4 changes for Verifiable Randomness Raffle Protocol →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

2 places HEY reads for Verifiable Randomness Raffle Protocol