Skip to content

cdn

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

Config and tooling for the SQD CDN (asset hosting, CORS).

What HEY knows

Development

Shipping consistentlyShipping: 4 counted ships in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 51How it is measured

Latest: Code changes this week (since Mon 26 Oct) · 1 commit

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts cdn on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow cdn

No account? Email me cdn’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.

View latest ship
Share
More detail
Not yet known
Unknown1 gap: Official site changes (stale). The last read of its website’s files is out of date.
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: 4 counted ships in the last 30 days, the newest 2026-10-29.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 1 commitCode changes, week of 2026-10-19 – 2026-10-25 · 2 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 7 commits+2 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".
Research coverage: HEY can answer 9 of the 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 44m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 3h ago.
  • API descriptionMeasuredRead 34d ago.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 4d ago.
  • Published packagesMeasuredRead 4d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, 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.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

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

Code activitySource-backed

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

What changed, in the repository’s own words:

1 active day in subsquid/cdn.

HEY could not tell what 1 commit changed this week. This week HEY looked inside 1 commit to see what changed: 1 could not be classified.

Record ship:5c6278b1… · HEY counts it as building; it does not judge the release’s quality.

Code changes, read from the team’s GitHub · not a deployment
What it names
0 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
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-29; HEY first knew on 2026-10-29.
Not known
  • No source HEY holds names what this change does.
  • HEY could not read whether every commit of this week changed code.
  • 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.

Shared change · Official source change

cdn's official site changed.

Links the official site declares changed: 0 added, 1 removed. Removed feed link….

Observed by HEY on 2026-10-08Source: Project’s official site

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.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-19 – 2026-10-25 · 2 commits

    Code activitySource-backed

    1 active day in subsquid/cdn.

    How HEY read this week

    HEY could not tell what 2 commits changed this week. This week HEY looked inside 2 commits to see what changed: 2 could not be classified.

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 7 commits

    Code activitySource-backed

    3 active days in subsquid/cdn.

    How HEY read this week

    HEY could not tell what 4 commits changed this week. This week HEY looked inside 7 commits to see what changed: 3 documentation or maintenance only, 4 could not be classified.

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in subsquid/cdn.

    How HEY read this week

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

  4. October 7, 2026

    AnnouncementSource-backed

  5. Code changes, week of 2026-09-28 – 2026-10-04 · 2 commits

    Code activitySource-backed

    2 active days in subsquid/cdn.

    How HEY read this week

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

  6. Code changes, week of 2026-09-21 – 2026-09-27 · 13 commits

    Code activitySource-backed

    4 active days in subsquid/cdn.

    How HEY read this week

    This week HEY looked inside 3 of 13 commits to see what changed: 1 changed code, 1 documentation or maintenance only, 1 could not be classified. One code change is enough for the week to count, so HEY stopped there.

  7. Code changes, week of 2026-09-14 – 2026-09-20 · at least 8 commits

    Code activitySource-backed

    3 active days in subsquid/cdn.

    How HEY read this week

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

  8. SQD Partners with Google Cloud to Expand Blockchain Analytics

    AnnouncementSource-backed

    Through SQD 360, our enterprise arm, SQD now contributes to the datasets behind Google Cloud's blockchain analytics in BigQuery.

Earlier ships (16)
  1. August 6, 2026

    AnnouncementSource-backed

  2. July 29, 2026

    AnnouncementSource-backed

  3. The New Architecture of DEX Data

    AnnouncementSource-backed

    How four DEX teams rebuilt their data layer: subgraph migrations, indexer vs RPC tradeoffs, and where AI agents fit. A joint report with Algebra.

  4. Subsquid Labs Announces Strategic Repositioning Toward Institutional Clients

    AnnouncementSource-backed

    SQD is repositioning toward enterprise and institutional clients, with Wanja S. Oberhof as new CEO and a board spanning crypto, capital markets, and AI.

  5. May 20, 2026

    AnnouncementSource-backed

  6. May 5, 2026

    AnnouncementSource-backed

  7. Unifying Under SQD.dev: One Home, One Focus

    AnnouncementSource-backed

    We're consolidating everything under one domain · sqd.dev. Tighten focus, simplify how people find and trust us, and put everything we're building in one place. Show all
    • We're consolidating everything under one domain
    • sqd.dev. Tighten focus, simplify how people find and trust us, and put everything we're building in one place.
  8. How SQD Validates Every Block

    AnnouncementSource-backed

    This post looks at how SQD verifies blockchain data at the source, rather than relying blindly on RPC responses. It covers trie-root validation, bloom checks, parent-hash continuity and a preview of Snoopy in beta this week.

  9. DeFi Wasn't Built for This

    AnnouncementSource-backed

    A collaborative research piece with Barter on why DeFi infrastructure built for human traders penalises autonomous agents · and what data, routing, and liquidity actually need to look like when the actor changes. Show all
    • A collaborative research piece with Barter on why DeFi infrastructure built for human traders penalises autonomous agents
    • and what data, routing, and liquidity actually need to look like when the actor changes.
  10. Public Revenue Pool: How SQD's Automated Supply Management Works

    AnnouncementSource-backed

    A look at how SQD Network's Revenue Pool fees are routed: how the FeeRouter splits top-ups three ways, how the automatic SQD conversion works via PancakeSwap, and how slippage protection keeps swaps safe.

  11. First Ever Public Revenue Pool (FAQs)

    AnnouncementSource-backed

    Learn how SQD Revenue Pools work, how this first public pool is structured, and what participants need to know when taking part. This FAQ covers rewards, activation, wallet limits, withdrawals, and key risks.

  12. Portal MCP Server: Connect AI Agents to Onchain Data

    AnnouncementSource-backed

    A lot of onchain work still starts the same way: you’ve got a question, and then you end up doing the boring setup work just to get to the first result. We just made that process faster.

  13. Sustainable Rewards, Powered by Demand

    AnnouncementSource-backed

    Portal Revenue Pools let SQD token holders lock tokens behind Portals serving paying customers and receive USDT-based rewards funded by real data demand.

  14. zkVerify Built Proof-Scale Indexing & Monitoring with SQD

    AnnouncementSource-backed

    zkVerify chose SQD for its native Substrate support, custom schema definitions, and throughput efficiency to build a verification layer for zero-knowledge proofs.

  15. Curvance Cut Indexing Time From Days To Minutes With SQD

    AnnouncementSource-backed

    Curvance switched from The Graph to SQD and cut indexing time from days to minutes for their lending protocol on Monad.

  16. SQD Revenue Pools Explained (FAQs)

    AnnouncementSource-backed

    Everything you need to know about Revenue Pools: how they work, how rewards are calculated, and how to participate.

Other changes on HEY’s record

79 changes on HEY’s record for cdn: 1 new Verified Builder or owner proof · 28 official source changes · 43 other ships · 7 weeks of code pushed.

All 79 changes for cdn →

The full change record holds 40 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Questions HEY can answer about cdn — as of 1 Nov

Show the answers
Is cdn still being built?
DerivedShipping: 4 counted ships in 30 days; latest ship 3 days ago. Evidence
What did cdn ship last?
FactCode changes this week (since Mon 26 Oct) · 1 commit — Code activity, 3 days ago. Evidence
What does HEY not know about cdn?
Unknown1 gap: Official site changes (stale). The last read of its website’s files is out of date.

Sources

39 places HEY reads for cdn
30 more sources (docs)