Skip to content
HEY Research Lab
Menu

Float

Perps

Is this your project? Claim it →

Stock exposure. Settled in USDG.

What HEY knows

Development

Last shipped 15 days agoActive: 1 counted ship in 30 days; latest ship 15 days ago. Evidence Source

Build Momentum 22How it is measured

Latest: Code changes, week of 2026-10-19 – 2026-10-25 · 83 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

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

No account? Email me Float’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
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.
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: 1 counted ship in the last 30 days, the newest 2026-10-25.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 83 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 81 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".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 83 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 81 commitssource:4e192ec8-e912-4cde-ad7c-b696557be617What 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 2h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 5d 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-19 – 2026-10-25 · 83 commits

Code activitySource-backed

Why it matters: First week of code changes after 31 quiet days.

What changed, in the repository’s own words:

6 active days in floatsheets/float.

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.

Record ship:dd4e92cc… · 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 3 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-10-25; HEY first knew on 2026-10-23.
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

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

1 meaningful development event was recorded in the last 30 days. Builder status: Active.

Observed by HEY on 2026-09-25Source: 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-21 – 2026-09-27 · 81 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in floatsheets/float.

    How HEY read this week

    This week HEY looked inside 4 of 81 commits to see what changed: 3 changed code, 1 documentation or maintenance only. 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-21 – 2026-09-27 · 81 commits (opens in a new tab)

Other changes on HEY’s record

5 changes on HEY’s record for Float: 2 new Verified Builders or owner proofs · 1 build pace change · 2 weeks of code pushed.

All 5 changes for Float →

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 Float