Skip to content
Menu

David Glitc

No narrative yet

Is this your project? Claim and verify →

Polymarket 5m terminal bot + ML traces

What HEY knows

Building
Quiet for 45 daysQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-04. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-08-31 – 2026-09-06 · · 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
Derived15 days ago: 0 meaningful ships this month, 4 the month before. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts David Glitc 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 David Glitc’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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-04.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06Code changes, week of 2026-08-24 – 2026-08-30Code changes, week of 2026-08-10 – 2026-08-16 · at least 6 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06Code changes, week of 2026-08-24 – 2026-08-30Code changes, week of 2026-08-10 – 2026-08-16 · at least 6 commits+5 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-08-31 – 2026-09-06david-glitc/zinger-core

Code activitySource linked

17 active days in David-glitc/zinger-core.

HEY has not looked inside this week’s commits yet.

Record ship:7c3c69a1… · 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: 2 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about David Glitc — as of 2026-10-19

Is David Glitc still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-04. Evidence
What did David Glitc ship last?
FactCode changes, week of 2026-08-31 – 2026-09-06 — Code activity, on 2026-09-04. Evidence
What does HEY not know about David Glitc?
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-08-31 – 2026-09-06david-glitc/zinger

    Code activitySource linked

    7 active days in David-glitc/Zinger.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 (opens in a new tab)

  2. Code changes, week of 2026-08-24 – 2026-08-30david-glitc/zinger

    Code activitySource linked

    6 active days in David-glitc/Zinger.

    View evidence: Code changes, week of 2026-08-24 – 2026-08-30 (opens in a new tab)

  3. Code changes, week of 2026-08-24 – 2026-08-30david-glitc/zinger-core

    Code activitySource linked

    12 active days in David-glitc/zinger-core.

    HEY has not looked inside this week’s commits yet.

    View evidence: Code changes, week of 2026-08-24 – 2026-08-30 (opens in a new tab)

  4. Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commitdavid-glitc/sherhood

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in david-glitc/sherhood.

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

    View evidence: Code changes, week of 2026-08-24 – 2026-08-30 · at least 1 commit (opens in a new tab)

  5. Code changes, week of 2026-08-10 – 2026-08-16 · at least 6 commitsdavid-glitc/zinger-core

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in David-glitc/zinger-core.

    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.

    View evidence: Code changes, week of 2026-08-10 – 2026-08-16 · at least 6 commits (opens in a new tab)

  6. v1.1.0david-glitc/zinger-core

    GitHub releaseSource verified

    v1.1.0 New: SQLite persistence layer (with JSON fallback) · src/polymarket/sqliteStore.ts: all state now persists into a single data/zinger.db (WAL) via Node 22's built-in node:sqlite — no native compilation. Keyed by the JSON store's relative path, with one-time auto-migration… Show all
    • v1.1.0 New: SQLite persistence layer (with JSON fallback)
    • src/polymarket/sqliteStore.ts: all state now persists into a single data/zinger.db (WAL) via Node 22's built-in node:sqlite — no native compilation. Keyed by the JSON store's relative path, with one-time auto-migration of legacy JSON files.
    • ml/sqlite_store.py + wiring in train_lstm.py, pipeline.py, export_onnx.py: Python scripts share the same docs table as the Node app, keeping both sides in sync.
    • Fallback: node:sqlite is loaded via createRequire, so the package still runs on Node 20/21…
    View evidence: v1.1.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 David Glitc? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

8 changes on HEY’s record for David Glitc: 1 release · 1 build pace change · 6 weeks of code pushed.

All 8 changes for David Glitc →

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 6h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo 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 19h ago.
  • Published packagesMeasuredRead 19h 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