Skip to content

QianExchange

AI Agents

Is this your project? Claim it →

Qian.ag - Robinhood Chain contracts

What HEY knows

Development

Dormant: no ship for 125 daysDormant: 0 counted ships in 30 days; latest ship on 2026-07-19. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-07-13 – 2026-07-19 · at least 6 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

No account? Email me QianExchange’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
Unknown2 gaps: 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
Dormant.
“Dormant” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-07-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-13 – 2026-07-19 · at least 6 commitsWhat 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 counted building from the project's own sources.
Source15 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-07-13 – 2026-07-19 · at least 6 commitssource:f54bfa16-2a40-48fb-97ea-18f98da4dd71source:3b99c295-d171-42a8-8f60-547270488bd6+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.
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 3d ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 7d ago.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

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-07-13 – 2026-07-19 · at least 6 commits qianexchange/robinhood-contracts

Code activitySource-backed

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

2 active days in qianexchange/robinhood-contracts.

This week HEY looked inside 2 of 8 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

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

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.

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-07-13 – 2026-07-19 · at least 9 commits qianexchange/mcp

    Code activitySource-backed

    2 active days in qianexchange/mcp.

    How HEY read this week

    This week HEY looked inside 2 of 14 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

Other changes on HEY’s record

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

All 4 changes for QianExchange →

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

Sources

15 places HEY reads for QianExchange
8 more sources (docs)