Skip to content
CCPEDIAby Unity Nodes

One index for the whole Canton Network.

CIPs, docs, forum, and governance. Always current, always searchable, and open to AI agents through MCP.

New here? Canton terms like CIP, SV Node, and Round explained on /glossary.What is CCPEDIA? →
  • Every answer links back to its primary source
  • Re-synced every 5 minutes to daily, per source
  • Open REST API and MCP server, no key required
Knowledge layer19 sources · syncing
90MCP TOOLS
117.0msAVG LATENCY
SERVER DATA
CIPs
124
Docs
2 723
Whitepapers
7
Blog
1 182
Forum
4 263
Mailing
3 201
YouTube
171
Discussions
51
GitHub Items
7 062
Releases
1 977
SDK Versions
8 110
Radar
518
Dev Fund
527
Ecosystem
549
Foundation
140
DSO
1 351
Sv Calendar Event
699
On
604
Cip Attachment
54
Total indexed records19 of 19 sources · semantic search enabled
33 313across 19 sources
90 MCP tools34 704 RAG chunks5 min - 24 hr sync/api/v1/sources
Apache 2.0

What's inside

Four kinds of material, all indexed from their primary source and kept current.

Why CCPEDIA exists

A SQLite database and a cron job that never stops reading the primary source.

CCPEDIA is a read-only index of public Canton Network material: CIPs, the developer forum, mailing lists, official docs, whitepapers, and GitHub releases, normalized into one database and always linked back to where it came from.

We kept writing Daml that didn't compile because search ranked old blog posts above current docs, and good forum answers were scattered across threads ranked by recency, not relevance. So we built one place that always reads the primary source and shows exactly when it was fetched, 225 CIP status transitions tracked that way so far.

Read the full story →
How it stays current
  • 5 minForum, CIP status, dev-fund GitHub, releases
  • 15 minDocs, mailing lists, blogs, GitHub items
  • 6 hWhitepapers, ecosystem registry & news
  • dailyVideo transcripts, discussions, embeddings rebuild

Three ways in

Same index, same citations, whichever one fits how you work.