Skip to content
Menu

launchtap

DEX

Is this your project? Claim and verify →

Fixed-supply token launchpad: bonding curve -> graduation -> Uniswap v2 pool with the initial LP burned. Non-custodial, built for Robinhood Chain.

What HEY knows

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

Build Momentum 32How it is measured

Latest ship
Code changes, week of 2026-10-05 – 2026-10-11 · 29 commits · · Code activity

Why it matters: First week of code changes after 21 quiet days.

Latest change
Derived2 days ago: Code changes this week (since Mon 12 Oct). Not counted as building. Evidence Source
FollowCreate alertTerminal previewView latest ship
Share

Follow puts launchtap 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 launchtap’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
Shipping.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-11.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11 · 29 commitsCode changes, week of 2026-09-14 – 2026-09-20 · 24 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 96 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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-10-05 – 2026-10-11 · 29 commitsCode changes, week of 2026-09-14 – 2026-09-20 · 24 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 96 commits+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

Code changes, week of 2026-10-05 – 2026-10-11 · 29 commitsoplosy/launchtap

Code activitySource linked

What changed, in the repository’s own words:

2 active days in oplosy/launchtap.

This week HEY looked inside 8 of 29 commits to see what changed: 3 changed code, 5 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

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

View evidence ↗

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 launchtap — as of 2026-10-18

Is launchtap still being built?
DerivedShipping: 2 meaningful events in 30 days; latest ship 7 days ago. Evidence
What did launchtap ship last?
FactCode changes, week of 2026-10-05 – 2026-10-11 · 29 commits — Code activity, 7 days ago. Evidence
What does HEY not know about launchtap?
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 12 Oct) · 2 commitsoplosy/launchtap

    Code activitySource linked

    1 active day in oplosy/launchtap.

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

    View evidence

  2. Code changes, week of 2026-09-14 – 2026-09-20 · 24 commitscontictus/launchtap

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in contictus/launchtap.

    This week HEY looked inside 1 of 24 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. Code changes, week of 2026-09-14 – 2026-09-20 · 24 commitsoplosy/launchtap

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in oplosy/launchtap.

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

    View evidence

  4. Code changes, week of 2026-09-07 – 2026-09-13 · at least 96 commitscontictus/launchtap

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 6 active days in contictus/launchtap since 2026-09-08; the count stops at the newest 100 commits listed.

    This week HEY looked inside 4 of 72 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence

  5. Code changes, week of 2026-08-31 – 2026-09-06 · at least 87 commitscontictus/launchtap

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in Contictus/launchtap.

    This week HEY looked inside 5 of 87 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

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

What changed

6 changes on HEY’s record for launchtap: 6 weeks of code pushed.

All 6 changes for launchtap →

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 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 42m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 7d ago.
  • Published packagesMeasuredRead 7d 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