Skip to content

radian

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 →

Radian — memecoin launchpad for Circle's Arc chain (Pons V2 port, native-USDC quoted)

What HEY knows

Development

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

Build Momentum 18How it is measured

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

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts radian 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 radian

No account? Email me radian’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
More detail
Not yet known
Unknown1 gap: API description (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
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-09-25, 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-21 – 2026-09-27 · 39 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 33 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".
Research coverage: HEY can answer 9 of the 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsMeasuredRead 12h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

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

Latest ship

Checked

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

Code activitySource-backed

3 active days in adrianhihi/radian.

This week HEY looked inside 5 of 39 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

Record ship:fd1af4ee… · 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
3 of 5 commits 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-23. 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.

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-09-14 – 2026-09-20 · at least 33 commits

    Code activitySource-backed

    3 active days in adrianhihi/radian.

    How HEY read this week

    This week HEY looked inside 3 of 33 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

Other changes on HEY’s record

3 changes on HEY’s record for radian: 1 new Verified Builder or owner proof · 2 weeks of code pushed.

All 3 changes for radian →

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)

Questions HEY can answer about radian — as of 1 Nov

Show the answers
Is radian still being built?
DerivedActive: 0 counted ships in 30 days; latest ship 37 days ago. Evidence
What did radian ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 39 commits — Code activity, 37 days ago. Evidence
What does HEY not know about radian?
Unknown1 gap: API description (no source). Its website links no API description.

Sources

3 places HEY reads for radian