Skip to content

spireproto

Dev Tools

Is this your project? Claim and verify →

Clearing primitives for tokenised assets: settlement windows, novation, netting in time, margin, collateral limits and the default waterfall. BigInt throughout, zero dependencies.

What HEY knows

Building
Activity not measurableHEY has a ship on record (last ship on 2026-08-31) 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 · at least 3 commits · · Code activity

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

Latest change
Derived17 days ago: HEY reclassified the project — official source added: docs. Evidence Source

Follow puts spireproto 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 spireproto’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
Unknown6 gaps: Building activity (not enough yet), Repositories (source unavailable), Releases (not enough yet), Published packages (no source), API description (not enough yet), Official site changes (not enough yet). 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 3 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-06 · at least 3 commitsCode changes, week of 2026-08-24 – 2026-08-30 · at least 2 commitsv0.4.1 - Register entry array fix+1 moreWhat 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.
Source22 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitsCode changes, week of 2026-08-24 – 2026-08-30 · at least 2 commitsv0.4.1 - Register entry array fix+6 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-06 · at least 3 commitsspireproto/spire

Code activitySource linked

1 active day in spireproto/spire.

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

Shared change · Release

spireproto shipped v0.5.2 - Register summary field rename.

Dated 2026-08-30 by the sourceSource: github

Questions HEY can answer about spireproto — as of 2026-10-18

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

Build timeline

  1. Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitsspireproto/spireproto

    Code activitySource linked

    1 active day in spireproto/spireproto.

  2. Code changes, week of 2026-08-31 – 2026-09-06 · at least 2 commitsspireproto/awesome-tokenized-equities

    Code activitySource linked

    1 active day in spireproto/awesome-tokenized-equities.

  3. Code changes, week of 2026-08-24 – 2026-08-30 · at least 2 commitsspireproto/spire-checks

    Code activitySource linked

    1 active day in spireproto/spire-checks.

  4. Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commitspireproto/spire-sdk

    Code activitySource linked

    1 active day in spireproto/spire-sdk.

  5. v0.4.1 - Register entry array fixspireproto/spire-sdk

    GitHub releaseSource verified

    register() no longer loses the entry array. The summary spread over it, because the summary carried a field called entries holding a count.

  6. v0.4.0 - Ticker resolutionspireproto/spire-sdk

    GitHub releaseSource verified

    resolveTicker() returns every candidate with a verdict, and null when the answer is not unique.

  7. v0.3.0 - Register replayspireproto/spire-sdk

    GitHub releaseSource verified

    register() returns entries with flags plus both readings.

  8. v0.2.0 - Injectable fetchspireproto/spire-sdk

    GitHub releaseSource verified

    Transport takes an injected fetch, so the whole client is testable offline.

  9. v0.1.0 - Transport and selectorsspireproto/spire-sdk

    GitHub releaseSource verified

    JSON-RPC transport, hand-encoded selectors, token() and identify().

  10. v0.5.2 - Register summary field renamespireproto/spire-core

    GitHub releaseSource verified

    register.resolve() returns count, not a field named entries holding a number. It collided when callers spread the result next to the entry array.

  11. v0.5.0 - Pool look-throughspireproto/spire-core

    GitHub releaseSource verified

    snapshot.take() looks through pools with readable share accounting. · Look-through rounding dust stays with the pool so a snapshot still reconciles. Show all
    • snapshot.take() looks through pools with readable share accounting.
    • Look-through rounding dust stays with the pool so a snapshot still reconciles.
  12. v0.4.0 - Snapshot and allocationspireproto/spire-core

    GitHub releaseSource verified

    allocation.allocateAccrual() for issuers that bump the multiplier instead of paying.

  13. v0.2.0 - Bytecode identityspireproto/spire-core

    GitHub releaseSource verified

    identity.resolveTicker() throws on ambiguity rather than returning the first match.

  14. v0.3.0 - Corporate-action registerspireproto/spire-core

    GitHub releaseSource verified

    register.build() flags duplicates, reversals and outsized steps. · register.resolve() reports absolute and composed readings side by side. Show all
    • register.build() flags duplicates, reversals and outsized steps.
    • register.resolve() reports absolute and composed readings side by side.
  15. v0.1.0 - Fixed-point multiplier arithmeticspireproto/spire-core

    GitHub releaseSource verified

    Fixed-point multiplier arithmetic, BigInt throughout.

  16. Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commitspireproto/spire-core

    Code activitySource linked

    1 active day in spireproto/spire-core.

  17. Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commitspireproto/spire-contracts

    Code activitySource linked

    1 active day in spireproto/spire-contracts.

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 spireproto? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

18 changes on HEY’s record for spireproto: 11 releases · 7 weeks of code pushed.

  • Code pushed1mo ago · 3 weeks of code pushed · recorded by HEY 1mo ago

    Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commits

    See the change Source ↗

  • Code pushed1mo ago · 2 weeks of code pushed · recorded by HEY 1mo ago

    Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commit

    See the change Source ↗

  • Release1mo ago · 5 releases · recorded by HEY 1mo ago

    v0.4.1 - Register entry array fix

    See the change Source ↗

  • Release1mo ago · 6 releases · recorded by HEY 1mo ago

    v0.5.2 - Register summary field rename

    See the change Source ↗

  • Code pushed1mo ago · recorded by HEY 1mo ago

    Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commit

    See the change Source ↗

All 18 changes for spireproto →

The full change record holds 23 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 3 of the 9 research questions that apply.

3 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 docsMeasuredRead 12h ago.
  • 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

  • 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

11 more sources (docs)