Skip to content
Menu

Amplifi Utils SDK

No narrative yet

Is this your project? Claim and verify →

What HEY knows

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

Build Momentum 30How it is measured

Latest ship
v1.0.6 · · GitHub release

Why it matters: First release after 22 quiet days.

This change
Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “v1.0.6”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Independently recorded: a package version published from the same repository matches it (npm @amplifi-liquidity/amplifi-utils-sdk@1.0.6).
Release and deployment
Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to 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 2026-10-07 16:49 UTC; HEY first knew on 2026-10-07.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

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 Amplifi Utils SDK 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 Amplifi Utils SDK’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 8 of the 11 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: 2 meaningful events in the last 30 days, the newest 2026-10-07.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv1.0.6Code changes, week of 2026-10-05 – 2026-10-11 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · 1 commit+1 moreWhat 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.ReadRecordsv1.0.6Code changes, week of 2026-10-05 – 2026-10-11 · 3 commitsCode changes, week of 2026-09-14 – 2026-09-20 · 1 commit+2 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

v1.0.6

GitHub releaseSource verified

Fixes · RPC provider resolution no longer stalls on a throttled or hanging host (#3). Each host is probed with a 5 s deadline, outside ethers' 429 retry loop. Failed hosts cool down for 5 minutes, concurrent callers share one probe per chain, and healthy providers are kept for 5… Show all
  • Fixes
  • RPC provider resolution no longer stalls on a throttled or hanging host (#3). Each host is probed with a 5 s deadline, outside ethers' 429 retry loop. Failed hosts cool down for 5 minutes, concurrent callers share one probe per chain, and healthy providers are kept for 5 minutes.
  • Public fallback RPCs. After the configured hosts and the default, PUBLIC_FALLBACK_RPC_URLS are tried (BSC: dataseed2–4, publicnode, 1rpc).
  • Requires Node ≥ 18. Release process
  • First release built and staged from CI: npm trusted publishing (OIDC) with provenance, approved by a maintainer…

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

View evidence ↗Post this ship on X

Shared change · Release

Amplifi Utils SDK shipped v1.0.6.

2 meaningful development events were recorded in the last 30 days. Builder status: Active.

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

Questions HEY can answer about Amplifi Utils SDK — as of 2026-10-23

Is Amplifi Utils SDK still being built?
DerivedActive: 2 meaningful events in 30 days; latest ship 16 days ago. Evidence
What did Amplifi Utils SDK ship last?
Factv1.0.6 — GitHub release, 16 days ago. Evidence
What does HEY not know about Amplifi Utils SDK?
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, week of 2026-10-05 – 2026-10-11 · 3 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in amplifi-liquidity/amplifi-utils-sdk.

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 3 commits (opens in a new tab)

  2. Code changes, week of 2026-09-14 – 2026-09-20 · 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in amplifi-liquidity/amplifi-utils-sdk.

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · 1 commit (opens in a new tab)

  3. Code changes, week of 2026-08-10 – 2026-08-16 · at least 2 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in amplifi-liquidity/amplifi-utils-sdk.

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-08-10 – 2026-08-16 · at least 2 commits (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 Amplifi Utils SDK? 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 Amplifi Utils SDK: 1 release · 3 weeks of code pushed.

Amplifi Utils SDK on What changed →

The full change record holds 1 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 8 of the 11 research questions that apply.

8 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 3h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 16d 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 4d ago.
  • Published packagesMeasuredRead 46m ago.
  • Package advisoriesMeasuredRead 4d ago.

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