Skip to content

loxley

DEX

Is this your project? Claim it →

Deploy Robinhood Chain exit desks with a single HTML file—no custody, no dependencies, no install.

What HEY knows

Development

Quiet for 44 daysQuiet: 0 counted ships in 30 days; latest ship 44 days ago. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-09-14 – 2026-09-20 · at least 3 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

No account? Email me loxley’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
Quiet.
“Quiet” by the activity rule: 0 counted ships in the last 30 days, the newest 2026-09-20.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 3 commitsWhat 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.
Source1 registered source, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 3 commitssource:0bdacbef-a374-4d15-a106-bb6d9b9cf350What 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 46d ago.

Building

  • Building activityMeasuredRead 14h 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 6d ago.
  • Published packagesMeasuredRead 6d 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-14 – 2026-09-20 · at least 3 commits

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:

2 active days in srane5798-cpu/loxley.

HEY could not tell what 1 commit changed this week. This week HEY looked inside 2 commits to see what changed: 1 documentation or maintenance only, 1 could not be classified.

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

Shared change · Verified Builder

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

Builder status: Quiet.

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

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

  1. 4 code weeks of maintenance or automation only — not counted as building

    Show the 4 weeks
    1. Code changes, week of 2026-10-12 – 2026-10-18 · 1 commit

      Code activitySource-backed

      1 active day in srane5798-cpu/loxley.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

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

      Code activitySource-backed

      1 active day in srane5798-cpu/loxley.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 9 commits to see what changed: 9 documentation or maintenance only.

    3. Code changes, week of 2026-09-28 – 2026-10-04 · 4 commits

      Code activitySource-backed

      1 active day in srane5798-cpu/loxley.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 4 commits to see what changed: 4 documentation or maintenance only.

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

      Code activitySource-backed

      1 active day in srane5798-cpu/loxley.

      Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

Other changes on HEY’s record

6 changes on HEY’s record for loxley: 1 new Verified Builder or owner proof · 5 weeks of code pushed.

All 6 changes for loxley →

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

Sources

1 place HEY reads for loxley