Skip to content

SpikeCalls

Dev Tools

Is this your project? Claim and verify →

The exit radar for pons v2 on Robinhood Chain. Reads the wallet, not the chart. Local, open, read-only by default.

What HEY knows

Building
Activity not measurableHEY has a ship on record (last ship on 2026-09-06) but no repository, changelog or feed it can keep reading, so no count here is a measured zero. Evidence
Latest ship
Code changes, week of 2026-08-31 – 2026-09-06 · · Code activity

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

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
A week of code changes. It 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-06; HEY first knew on 2026-09-15. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • HEY could not read whether every commit of this week changed code.
  • 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.

Follow puts SpikeCalls on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me SpikeCalls’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.

Token market · context
No token tracked
Not yet known
Unknown7 gaps: Building activity (not enough yet), Repositories (source unavailable), Releases (not enough yet), Published packages (no source), Official docs (no source), API description (no source), Official site changes (no source). None of its builder sources can be read right now.

HEY cannot answer whether anyone is building this yet (building activity: not enough yet); it can answer 2 of the 9 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Activity not measurable.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06What HEY derivedHEY’s activity rule reads the counted events as “Activity not measurable”.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 verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06source:63b97be4-c876-41c3-895c-abbb351bc651source:a1d525c3-0021-42e4-aef8-67b098c4709e+1 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.
Build Momentum not measurable.
HEY holds no public repository, changelog or feed it can read building from, so there is nothing to measure yet.
Market figures are context only and never change activity status. Methodology

Latest ship

Code changes, week of 2026-08-31 – 2026-09-06spikecalls/hoodrat

Code activitySource linked

1 active day in SpikeCalls/hoodrat.

Record ship:e7c1a774… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Questions HEY can answer about SpikeCalls — as of 2026-10-21

Is SpikeCalls still being built?
UnknownActivity not measurable: HEY has a ship on record (last ship on 2026-09-06) but no repository, changelog or feed it can keep reading, so no count here is a measured zero. Evidence
What did SpikeCalls ship last?
FactCode changes, week of 2026-08-31 – 2026-09-06 — Code activity, on 2026-09-06. Evidence
What does HEY not know about SpikeCalls?
Unknown7 gaps: Building activity (not enough yet), Repositories (source unavailable), Releases (not enough yet), +4 more. None of its builder sources can be read right now. Details

Build timeline

  1. Code changes, week of 2026-08-31 – 2026-09-06spikecalls/tocsin

    Code activitySource linked

    1 active day in SpikeCalls/tocsin.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about SpikeCalls? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

2 changes on HEY’s record for SpikeCalls: 2 weeks of code pushed.

SpikeCalls on What changed →

The full change record holds 3 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY cannot answer whether anyone is building this yet (building activity: not enough yet); it can answer 2 of the 9 research questions that apply.

2 of 9 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityNot enough yetNone of its builder sources can be read right now.
  • RepositoriesSource unavailableEvery repository HEY holds has stopped answering.
  • ReleasesNot enough yetNone of its builder sources can be read right now.
  • 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

  • Published packagesNo sourceNo repository the project claims as its own.

Not applicable here: Repository details, Package advisories, Contract creation, Contract activity, Verified source, 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.

Sources