Skip to content
Menu

ReptilianHQ

Dev Tools

Is this your project? Claim and verify →

Public TypeScript SDK, contract interfaces, ABIs, and deployment metadata for the Launch On Block protocol.

What HEY knows

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

Build Momentum 18How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · at least 6 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
Derived9 days ago: 0 meaningful ships this month, 4 the month before. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts ReptilianHQ 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 ReptilianHQ’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's longer window: 4 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-08, 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 · at least 6 commitsSDK 0.10.0Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commits+2 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.
Source3 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 6 commitsSDK 0.10.0Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commits+3 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 · at least 6 commits

Code activitySource linked

What changed, in the repository’s own words:

7 active days in ReptilianHQ/launch-on-block-sdk.

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

Record ship:84e501e6… · 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

ReptilianHQ shipped SDK 0.10.0.

Builder status: Active.

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

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

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

Build timeline

  1. SDK 0.10.0

    GitHub releaseSource verified

    Adds generated Envio indexing materializations, verified consumer documentation, and pinned mainnet fork release checks. · Public indexing catalog, network manifests, event ABIs and tested Envio starter with persisted restart evidence. · Generated curve/router… Show all
    • Adds generated Envio indexing materializations, verified consumer documentation, and pinned mainnet fork release checks.
    • Public indexing catalog, network manifests, event ABIs and tested Envio starter with persisted restart evidence.
    • Generated curve/router quote-versus-execution tests plus launch creation, graduation and collected-fee verification on a pinned local mainnet fork.
    • Source-bound release evidence, guarded against edits during execution; packed exports and consumer examples verified.
    • First-party chain-indexer tarball checks passed before publication. Fork scope and…
    View evidence

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

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in ReptilianHQ/launch-on-block-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

  3. v0.9.0

    GitHub releaseSource verified

    Publish ./provenance/mainnet.json and ./provenance/testnet.json deployment provenance documents, generated at build time from the reviewed public deployment manifest. · Add verify*Transaction calldata verification for every remaining build*Transaction function (sell, graduate… Show all
    • Publish ./provenance/mainnet.json and ./provenance/testnet.json deployment provenance documents, generated at build time from the reviewed public deployment manifest.
    • Add verify*Transaction calldata verification for every remaining build*Transaction function (sell, graduate, claim/claimAll, approve, router buy/sell, swapExactIn, fee collection), matching the existing verifyCreateLaunchTransaction/verifyCurveBuyTransaction pattern.
    • Add Hegel property-based invariant suites for transactions, receipts, and economics, closing this package's SDK standard conformance gap…
    View evidence

  4. v0.8.0

    GitHub releaseSource verified

    Adds offline LaunchToken CREATE2 prediction and bounded vanity-salt mining, including deterministic B10C address discovery for LaunchOnBlock launch flows.

    View evidence

  5. Code changes, week of 2026-07-27 – 2026-08-02 · at least 8 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in ReptilianHQ/launch-on-block-sdk.

    This week HEY looked inside 1 of 8 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  6. Launch On Block SDK 0.7.1

    GitHub releaseSource verified

    Highlights · Aligns public documentation, support policy, and release metadata with the supported npm release line. · Makes the Envio and Graph indexing examples reproducible with committed, validated lockfiles. · Refreshes verified tooling dependencies and consolidates… Show all
    • Highlights
    • Aligns public documentation, support policy, and release metadata with the supported npm release line.
    • Makes the Envio and Graph indexing examples reproducible with committed, validated lockfiles.
    • Refreshes verified tooling dependencies and consolidates automated dependency updates. There are no runtime SDK API changes in this release. The package is published by the protected GitHub Actions trusted-publishing workflow with npm provenance.
    View evidence

  7. Launch On Block SDK 0.7.0

    GitHub releaseSource verified

    Highlights · Publishes only the reviewed deployment integration boundary in declarations and runtime artifacts. · Removes writes_enabled, release authorities, deployer identity, limits, and private chain evidence. · Adds self-contained source maps and automated execution of the… Show all
    • Highlights
    • Publishes only the reviewed deployment integration boundary in declarations and runtime artifacts.
    • Removes writes_enabled, release authorities, deployer identity, limits, and private chain evidence.
    • Adds self-contained source maps and automated execution of the packed deployment module.
    • Completes public security, contribution, dependency, and repository-governance guardrails. Compatibility This is an intentionally breaking pre-1.0 release. Consumers reading removed deployment-manifest fields must migrate before upgrading. Contract ABIs, transaction builders…
    View evidence

  8. Launch On Block SDK 0.6.0

    GitHub releaseSource verified

    Registry status: @reptilianhq/launch-on-block-sdk@0.6.0 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Highlights · Relicenses the public SDK under Apache-2.0 for proprietary and open-source… Show all
    • Registry status: @reptilianhq/launch-on-block-sdk@0.6.0 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Highlights
    • Relicenses the public SDK under Apache-2.0 for proprietary and open-source integrations.
    • Publishes the canonical Apache license and exact author attribution in every package.
    • Records the contributor audit while preserving GPL-3.0-only terms for releases through 0.5.0. The npm package was originally published by the protected GitHub Actions trusted-publishing workflow with…
    View evidence

  9. Launch On Block SDK 0.5.0

    GitHub releaseSource verified

    Registry status: @reptilianhq/launch-on-block-sdk@0.5.0 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Highlights · Defines a clean public ABI boundary while keeping upgrade and escrow internals… Show all
    • Registry status: @reptilianhq/launch-on-block-sdk@0.5.0 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Highlights
    • Defines a clean public ABI boundary while keeping upgrade and escrow internals private.
    • Adds verified read-only launch escrow reconciliation with explicitly unpriced accounting values.
    • Publishes typed event metadata, neutral indexing assets, and validated Envio and Graph examples. The npm package was originally published by the protected GitHub Actions trusted-publishing workflow…
    View evidence

  10. Launch On Block SDK 0.4.3

    GitHub releaseSource verified

    Registry status: @reptilianhq/launch-on-block-sdk@0.4.3 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Changes · Isolate npm registry verification in a retryable post-publish job. · Tolerate registry… Show all
    • Registry status: @reptilianhq/launch-on-block-sdk@0.4.3 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Changes
    • Isolate npm registry verification in a retryable post-publish job.
    • Tolerate registry propagation delay without falsely failing a successful publish.
    • No SDK API changes from 0.4.2.
    View evidence

  11. Launch On Block SDK 0.4.2

    GitHub releaseSource verified

    Registry status: @reptilianhq/launch-on-block-sdk@0.4.2 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Changes · Verify tokenless npm trusted publishing through the protected GitHub Actions release… Show all
    • Registry status: @reptilianhq/launch-on-block-sdk@0.4.2 was withdrawn from npm on 2026-07-27. This source tag remains for provenance and license history. Use the npm latest release. Changes
    • Verify tokenless npm trusted publishing through the protected GitHub Actions release workflow.
    • Publish npm provenance bound to this repository, workflow, and release commit. This release contains no SDK API changes from 0.4.1.
    View evidence

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

What changed

13 changes on HEY’s record for ReptilianHQ: 9 releases · 1 build pace change · 3 weeks of code pushed.

All 13 changes for ReptilianHQ →

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 11m 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 5h ago.
  • Published packagesMeasuredRead 49m ago.
  • Package advisoriesMeasuredRead 9h 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