ABOUT / the index

What this site indexes, where the data comes from, how often it refreshes, and how to use it. Built and maintained by Unity Nodes. One person, a SQLite file, a cron tick every minute.

14 source types39k indexed items43k embedded chunks28k sync runs logged88 MCP tools43 REST endpoints

What this is

CCPEDIAis a read-only index of public Canton Network material: CIPs, the developer forum, the cip-vote mailing lists, the official docs (canton.network + daml.com), whitepapers, GitHub releases and issues, YouTube talks, third-party blogs, and the Foundation's curated KB. Each source is re-scraped on its own cadence, normalised into one SQLite database, embedded for vector search, and made queryable through one ranked-results page.

On top of the index sits Cippy, a chat that retrieves from the same database and cites every source link it used. Same data, three surfaces: browser search, chat, and an MCP server for AI agents.

Sources

Every row below is a real table in the live database. Counts and last-fetched times are read at page-render and revalidated every 10 minutes.

SourceCadenceItemsLast fetchedCanonical
CIPs6 h1203h agogithub.com/canton-foundation/cips
CIP status history6 h2183h agoupstream git log of the CIP repo
Forum topics5 min4.2k3m agoforum.canton.network
Forum posts5 min18k3m agoforum.canton.network
Mailing-list threadsdaily1.3k-lists.sync.global
Mailing-list messages5 min3.1k3m agolists.sync.global
Docs pages6 h2.5k3h agodocs.canton.network + docs.digitalasset.com
Whitepapersdaily718h agocanton.network/whitepapers
GitHub items (issues, PRs, dev-fund)5 min5.9k2m agogithub.com/canton-foundation + digital-asset + canton-network
GitHub releases15 min1.9k3m agogithub.com release feeds
GitHub discussions6 h423h agogithub discussions API
Blog posts (aggregated)15 min1.0k1m agocanton.network, blog.digitalasset.com, cantonnews.org, PR Newswire
YouTube videos + transcripts6 h1713h agoyoutube.com channels (curated)
Foundation KB (Build-on-Canton)daily13618h agogithub.com/canton-network-devs/Build-on-Canton-MCP

Why this exists

I kept writing Daml that didn't compile because Google ranked old blog posts above the current docs. Half the answers I found paraphrased canton.network into uselessness; the other half quoted endpoints that had moved or been renamed two SDK versions ago. The official forum has good answers, but they're scattered across threads and the search there ranks by recency, not relevance.

So I built one place that always reads the primary source, keeps the canonical link, and shows the timestamp it was last fetched. If a CIP moved from Draft to Final last Tuesday, the page here knows that and shows the transition (there are 218 such transitions logged so far). If a forum thread has no replies in 30 days, it's flagged. If a docs page 404s upstream, the cached snapshot stays reachable until it comes back.

How it stays current

A cron tick fires every minute on the VPS and dispatches work into buckets so cheap sources stay fresh and expensive ones don't hammer their upstreams:

*     *  *  *  *   sync-tick.sh
  ├─ 5 min   forum, CIP status changes, dev-fund GitHub items, releases
  ├─ 15 min  docs (3 sites), mailing list (6 groups), blogs, github items
  ├─ 6  h    whitepapers, sitemaps, ecosystem registry, ecosystem-news
  └─ daily   YouTube transcripts, GitHub discussions, foundation-kb,
             embeddings rebuild for any source whose content_hash changed

When a source is offline, the previous snapshot is served with a last-fetched note. Nothing is paraphrased and nothing is rewritten by an LLM before being shown to you. The model only touches text inside Cippy answers, and even there it has to cite a real source row from the database.

Three ways to use it

1 / Search

Press / anywhere, or use the topbar. Ranked results across every source in one list.

/  →  query
   → ranked results
     across all sources

Browser route: /search

2 / Ask (Cippy)

Conversational answers with every source row cited. Same DB, retrieved with hybrid FTS5 + vector search.

POST /api/chat
{ "message": "what changed
              in CIP-0056
              last week?" }

Browser route: /ask

3 / MCP server

Point Claude Desktop, Cursor, or any MCP client at the URL below. 88 tools covering every source.

https://ccpedia.xyz/mcp
  search_cips, get_cip,
  search_forum, search_docs,
  search_mailing, 83 more

Reference: /for-ai · /api/v1/reference

What this is NOT

  • Not a replacement for the primary sources. Every page links back to canton.network, daml.com, the forum thread, or the GitHub release that the row came from. If the answer matters, click through and verify against the original.
  • Not a news site.No editorial team, no headlines, no "our take". Aggregator pages (/blog, /feed) re-list third-party posts; their text belongs to the original publishers.
  • Not financial advice and not investment research. CIPs cover technical and governance proposals. Nothing here is a recommendation to buy or sell CC or any other asset.
  • Not affiliated with the Canton Foundation, Digital Asset, or any validator operator. CCPEDIA is operated independently by Unity Nodes.
  • Not a finished product.Things break. Upstreams change shape. When I notice, I fix it; when I don't, please tell me on /contact.

How to reach