Skip to content
HEY Research Lab
Menu

deltadesk

StockFi

Is this your project? Claim it →

DeltaDesk: the open market-making desk for tokenized stocks. Truth layer (markouts vs Hyperliquid), x402 API, Bankr skills, and on-chain desk lanes on Robinhood Chain with a Dynamic-delegated agent.

What HEY knows

Development

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

Build Momentum 12How it is measured

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

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me deltadesk’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
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
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: 1 counted ship in the last 45 days (the rule needs at least 2); the newest, 2026-09-24, 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 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · at least 83 commitsDeployed a new contract: 0x7edd…a283+2 moreWhat 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, 1 of them context only.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitCode changes, week of 2026-09-14 – 2026-09-20 · at least 83 commitsDeployed a new contract: 0x7edd…a283+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 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

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

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 10m ago.
  • Published packagesMeasuredRead 10m 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
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

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

Code activitySource-backed

What changed, in the repository’s own words:

1 active day in oojae/deltadesk.

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

Record ship:025d1066… · 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-24; HEY first knew on 2026-09-24. 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)

Shared change · Verified Builder

deltadesk is now a Verified Builder: HEY checked its builder sources.

Builder status: Active.

Observed by HEY on 2026-09-20Source: HEY Signal

View evidence ↗Evidence receipt

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in oojae/deltadesk.

    How HEY read this week

    This week HEY looked inside 3 of 83 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.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 83 commits (opens in a new tab)

  2. Deployed a new contract: 0x7edd…a283

    New contractSource-backed

    The account that launched deltadesk’s token deployed 0x7edd…a283 on 2026-08-03. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: 0x7edd…a283 (opens in a new tab)

  3. Deployed a new contract: SwapProxy

    New contractSource-backed

    The account that launched deltadesk’s token deployed SwapProxy at 0xa472…29df on 2026-05-29. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: SwapProxy (opens in a new tab)

  4. Deployed a new contract: SwapProxy

    New contractSource-backed

    The account that launched deltadesk’s token deployed SwapProxy at 0xc87d…bf13 on 2026-05-29. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: SwapProxy (opens in a new tab)

  5. 3 contracts deployed by the project’s deployer between 19:51:18 and 19:51:57 UTC on 26 May

    New contract

    Show all 3 contracts

    1. Deployed a new contract: 0x0cf5…4c24

      New contractSource-backed

      The account that launched deltadesk’s token deployed 0x0cf5…4c24 on 2026-05-26. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x0cf5…4c24 (opens in a new tab)

    2. Deployed a new contract: 0xe047…94de

      New contractSource-backed

      The account that launched deltadesk’s token deployed 0xe047…94de on 2026-05-26. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xe047…94de (opens in a new tab)

    3. Deployed a new contract: 0xc7af…940d

      New contractSource-backed

      The account that launched deltadesk’s token deployed 0xc7af…940d on 2026-05-26. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0xc7af…940d (opens in a new tab)

  6. Deployed a new contract: UnsupportedProtocol

    New contractSource-backed

    The account that launched deltadesk’s token deployed UnsupportedProtocol at 0x7332…02c4 on 2026-05-26. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: UnsupportedProtocol (opens in a new tab)

  7. 2 contracts deployed by the project’s deployer between 21:15:20 and 21:15:33 UTC on 22 May

    New contract

    Show all 2 contracts

    1. Deployed a new contract: 0x42bc…8b1b

      New contractSource-backed

      The account that launched deltadesk’s token deployed 0x42bc…8b1b on 2026-05-22. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x42bc…8b1b (opens in a new tab)

    2. Deployed a new contract: 0x99f3…2e0e

      New contractSource-backed

      The account that launched deltadesk’s token deployed 0x99f3…2e0e on 2026-05-22. Read from the chain; the creating transaction is the evidence.

      View evidence: Deployed a new contract: 0x99f3…2e0e (opens in a new tab)

  8. Deployed a new contract: UniversalRouter

    New contractSource-backed

    The account that launched deltadesk’s token deployed UniversalRouter at 0x53bf…6f77 on 2026-05-22. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: UniversalRouter (opens in a new tab)
Earlier ships (1)

  1. Deployed a new contract: SwapRouter02

    New contractSource-backed

    The account that launched deltadesk’s token deployed SwapRouter02 at 0xcaf6…5cb2 on 2026-05-22. Read from the chain; the creating transaction is the evidence.

    View evidence: Deployed a new contract: SwapRouter02 (opens in a new tab)

Other changes on HEY’s record

14 changes on HEY’s record for deltadesk: 1 new Verified Builder or owner proof · 11 contract changes · 2 weeks of code pushed.

All 14 changes for deltadesk →

The full change record holds 3 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 deltadesk
  • Repository
    https://github.com/OoJae/assayContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
  • Repository
    https://github.com/OoJae/deltadeskOfficial