Skip to content
Menu

novamp

No narrative yet

Is this your project? Claim and verify →

You didn't get rugged. You bought the copy. Read-only clone resolver for pons v2 on Robinhood Chain.

What HEY knows

Building
Last shipped 42 days agoActive: 0 meaningful events in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 12How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · 76 commits · · Code activity

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

Latest change
Derived4 days ago: Code changes this week (since Mon 19 Oct). Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 1 of 1 commit HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-19; HEY first knew on 2026-10-20.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts novamp 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 novamp’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
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 of the 10 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
Active.
“Active” by the activity rule's longer window: 3 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-11, 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-07 – 2026-09-13 · 76 commitsv0.4.0 - swarm detection and the exec hand-offnovamp 0.3.0What 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 verified building evidence from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · 76 commitsv0.4.0 - swarm detection and the exec hand-offnovamp 0.3.0+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.
Market figures are context only and never change activity status. Methodology
LinksGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · 76 commits

Code activitySource linked

What changed, in the repository’s own words:

5 active days in bored2boar/novamp.

This week HEY looked inside 3 of 76 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. 38 automated commits (bot accounts or a repeating scripted message) not counted.

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

View evidence ↗

Shared change · Release

novamp shipped v0.4.0 - swarm detection and the exec hand-off.

Builder status: Active.

Dated 2026-09-10 by the sourceSource: GitHub

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: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about novamp — as of 2026-10-23

Is novamp still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 42 days ago. Evidence
What did novamp ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · 76 commits — Code activity, 42 days ago. Evidence
What does HEY not know about novamp?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes this week (since Mon 19 Oct) · 1 commit

    Code activitySource linked

    1 active day in bored2boar/novamp.

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

    View evidence: Code changes this week (since Mon 19 Oct) · 1 commit (opens in a new tab)

  2. v0.4.0 - swarm detection and the exec hand-off

    GitHub releaseSource verified

    A name catching fire is visible in the data before anyone knows which token is going to be the one. This release catches that moment and answers the question it raises, which is not "will this pump" but "eleven of these are copies, which one is not". Added · novamp swarm. A… Show all
    • A name catching fire is visible in the data before anyone knows which token is going to be the one. This release catches that moment and answers the question it raises, which is not "will this pump" but "eleven of these are copies, which one is not". Added
    • novamp swarm. A burst of launches collapsing into one cluster inside a short window, from wallets that are not each other, is a crowd reacting to something. The distinct-deployer bar is what keeps one farm spraying a ticker from ten wallets out of the results.
    • News correlation with the order checked. A match requires the…
    View evidence: v0.4.0 - swarm detection and the exec hand-off (opens in a new tab)

  3. novamp 0.3.0

    GitHub releaseSource verified

    novamp finds every token fighting over the same name on Robinhood Chain, works out which one is the original, and flags the ones to leave alone. A name catches, and sixty seconds later there are fourteen tokens carrying it. Most of what retail loses on this chain is not lost to… Show all

    novamp finds every token fighting over the same name on Robinhood Chain, works out which one is the original, and flags the ones to leave alone. A name catches, and sixty seconds later there are fourteen tokens carrying it. Most of what retail loses on this chain is not lost to the rug they bought, it is lost to buying number seven while reading number one's timeline. Read only. No key, no signer, no transaction path, and CI fails the build if a signing primitive ever appears in the source. This is the first tagged release. Everything below is in it. What it does Paste a ticker or a…

    View evidence: novamp 0.3.0 (opens in a new tab)

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

What changed

4 changes on HEY’s record for novamp: 2 releases · 2 weeks of code pushed.

novamp on What changed →

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

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 6m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • 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 3d ago.
  • Published packagesMeasuredRead 3d ago.

Not applicable here: 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