Skip to content

Yield Orders

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 →

The home for onchain yield 👑

What HEY knows

Development

Shipping consistentlyShipping: 5 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 52How it is measured

Latest: Code changes, week of 2026-11-09 – 2026-11-15 · 9 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Yield Orders 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 Yield Orders

No account? Email me Yield Orders’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

yld.cx: TVL $0 · fees 24h not tracked · revenue 24h not tracked (DefiLlama, 2026-11-16). Registry context, not a measure of building.

Not yet known
Unknown5 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), Official site changes (stale), Protocol economics (no source). Packages name its repository, but none is confirmed as the project’s own.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 5 counted ships in the last 30 days, the newest 2026-11-15.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-11-09 – 2026-11-15 · 9 commitsCode changes, week of 2026-11-02 – 2026-11-08 · 13 commitsCode changes, week of 2026-10-26 – 2026-11-01 · 2 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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 6 of the 11 research questions that apply.
6 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 23m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 4d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

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

Latest ship

Checked

Code changes, week of 2026-11-09 – 2026-11-15 · 9 commits

Code activitySource-backed

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

3 active days in yld-cx/yield-orders.

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

Record ship:6195a818… · 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-11-15; HEY first knew on 2026-11-11.
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: 4 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-11-02 – 2026-11-08 · 13 commits

    Code activitySource-backed

    7 active days in yld-cx/yield-orders.

    How HEY read this week

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

  2. Code changes, week of 2026-10-26 – 2026-11-01 · 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in yld-cx/yield-orders.

    How HEY read this week

    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.

  3. Code changes, week of 2026-10-19 – 2026-10-25 · 15 commits

    Code activitySource-backed

    6 active days in yld-cx/yield-orders.

    How HEY read this week

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

  4. Code changes, week of 2026-10-12 – 2026-10-18 · 22 commits

    Code activitySource-backed

    4 active days in yld-cx/yield-orders.

    How HEY read this week

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

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 10 commits

    Code activitySource-backed

    5 active days in yld-cx/yield-orders.

    How HEY read this week

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

  6. Code changes, week of 2026-09-28 – 2026-10-04 · 14 commits

    Code activitySource-backed

    4 active days in yld-cx/yield-orders.

    How HEY read this week

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

Other changes on HEY’s record

9 changes on HEY’s record for Yield Orders: 1 new Verified Builder or owner proof · 1 new project on HEY · 7 weeks of code pushed.

All 9 changes for Yield Orders →

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 Yield Orders