Skip to content
HEY Research Lab
Menu

Cheq3 Contracts

Is this your project? Claim it →

CHEQ3 smart contracts: private programmable credit on Robinhood Chain

What HEY knows

Development

Quiet for 46 daysQuiet: 0 counted ships in 30 days; latest ship on 2026-09-25. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Cheq3 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.

Sign in to follow Cheq3 Contracts

No account? Email me Cheq3 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.

More detail
Product usage

CHEQ3: TVL $18 · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-11-10). Registry context, not a measure of building.

Not yet known
Unknown2 gaps: API description (no source), Protocol economics (no source). Its website links no API description.
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-25.
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 · 1 commitWhat 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 counted building from the project's own sources.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitsource:b91cc83c-ca48-4b87-a6db-a6adb99bab00source:f595102a-7a52-4248-9436-47a405924604+1 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.
Research coverage: HEY can answer 9 of the 11 research questions that apply.
9 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsMeasuredRead 2d ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 4d ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 6d 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, Published source code, 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
LinksWebsite (opens in a new tab)GitHub (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 · 1 commit

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

What changed, in the repository’s own words:

1 active day in cheq3app/cheq3-contracts.

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

Record ship:ba893ed4… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not 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
The source dates it to the week of 2026-09-25; HEY first knew on 2026-09-26. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

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

What changed

2 changes on HEY’s record for Cheq3 Contracts: 1 new Verified Builder or owner proof · 1 week of code pushed.

All 2 changes for Cheq3 Contracts →

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

Sources

4 places HEY reads for Cheq3 Contracts