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. A SQLite file and a cron tick every minute.
What this is
CCPEDIA is 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.
Same data, two surfaces: browser search and an MCP server for AI agents, plus a REST API behind both.
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.
| Source | Cadence | Items | Last fetched | Canonical |
|---|---|---|---|---|
| CIPs | 15 min | 132 | 1m ago | github.com/canton-foundation/cips |
| CIP status history | 15 min | 237 | just now | upstream git log of the CIP repo |
| Forum topics | 5 min | 4.3k | 3m ago | forum.canton.network |
| Forum posts | 5 min | 18k | 3m ago | forum.canton.network |
| Mailing-list threads | daily | 1.4k | - | lists.sync.global |
| Mailing-list messages | 5 min | 3.1k | 3m ago | lists.sync.global |
| Docs pages | 6 h | 2.9k | 2h ago | docs.canton.network + docs.digitalasset.com |
| Whitepapers | daily | 7 | 6h ago | canton.network/whitepapers |
| GitHub items (issues, PRs, dev-fund) | 5 min | 8.5k | 2m ago | github.com/canton-foundation + digital-asset + canton-network |
| GitHub releases | 15 min | 2.0k | 3m ago | github.com release feeds |
| GitHub discussions | 6 h | 51 | 3h ago | github discussions API |
| Blog posts (aggregated) | 15 min | 1.3k | 1m ago | canton.network, blog.digitalasset.com, cantonnews.org, PR Newswire |
| YouTube videos + transcripts | 6 h | 172 | 3h ago | youtube.com channels (curated) |
| Foundation KB (Build-on-Canton) | daily | 206 | 6h ago | github.com/canton-network-devs/Build-on-Canton-MCP |
Why this exists
We kept writing Daml that didn't compile because Google ranked old blog posts above the current docs. Half the answers we 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 we 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 237 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 changedWhen 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.
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 sourcesBrowser route: /search
2 / REST API
JSON over HTTP, no API key. The same ranked results the search box and MCP tools use.
GET /api/v1/search
?q=validator+rewards
→ ranked results, JSONReference: /api/v1/reference
3 / MCP server
Point Claude Desktop, Cursor, or any MCP client at the URL below. 90 tools covering every source.
https://ccpedia.xyz/mcp search_cips, get_cip, search_forum, search_docs, search_mailing, 85 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 we notice, we fix it; when we don't, please tell us on /contact.
How to reach
- Anything wrong on the site, bugs, feature ideas: contact form
- Security issues: security@unitynodes.com (scope and disclosure timeline on /security)
- For AI agents: crawl contract at /for-ai, REST docs at /api/v1/reference
- X / Twitter: @ccpedia_xyz