What you can do with CKB Pulse
Pulse shows who is building CKB, live, from their public work on GitHub. This page lists everything else it does.
For everyone
Watch the work
Every project is a block (a bar on a phone), the faces are the people at work, and each update lands as it happens. Tap a project or a face to see its last 30 days, its badge and a link to share.
Keep up without coming back
The week in one page, to read or forward. A feed for your reader. And notices on this device when something you follow moves (follow from a project's card) or a new CKB project appears (in the New tab).
Add a missing project
Pulse finds CKB work by itself: projects that use a CKB library, carry a CKB topic, or call a Fiber node. If it missed yours, write the GitHub name in the New tab. It joins at once if it has public CKB work from the last 30 days.
For developers
Read what CKB learned
Lessons from real fixes in CKB projects, each linked to the commit it came from. Search them, start with the basics, or look up a term.
Show your project's pulse
A small picture with a project's last 7 days, for a README or a website. Each project's and person's card on the page has its own, ready to copy. This one is the whole ecosystem:
[](https://pulse.lusocryptolabs.com/)See who builds on your library
For people who maintain a CKB library: how many of the projects Pulse follows depend on it, and how many are active. CCC, Lumos, Spore SDK and ckb-std.
Use the data
What the page shows is open JSON, free to use. Please send a User-Agent that names your app.
https://pulse.lusocryptolabs.com/api/state
projects, highlights and 7 days of historyhttps://pulse.lusocryptolabs.com/api/repo?name=owner/repo
one project over 30 dayshttps://pulse.lusocryptolabs.com/api/impact?lib=ccc
Which projects use a library: CCC, Lumos, Spore SDK or ckb-stdhttps://pulse.lusocryptolabs.com/api/stream
updates as they happen (Server-Sent Events)https://pulse.lusocryptolabs.com/learned.json
every released lesson in one file, under CC BY 4.0https://pulse.lusocryptolabs.com/learned.xml
the newest lessons as an Atom feed
These answers need no key and can be read from any website.
Ask an AI agent
Pulse is also an MCP server, so an AI agent such as Claude can ask it about CKB: who works on Fiber, what a project did this month, what the DAO funds. It only reads what Pulse stores, and there is nothing to install.
In Claude Code:
claude mcp add --transport http ckb-pulse https://pulse.lusocryptolabs.com/mcpIn another MCP client, add an HTTP server at:
https://pulse.lusocryptolabs.com/mcp
Then ask, for example:
Who has worked on Fiber this month, and on which projects?
What it can look up
overviewthe day, week or month: updates, people, projects and the most activefind_projectsprojects by words or by areaprojectone project: activity, people and latest updatespersonwhat one person works onwho_works_onthe most active people in an arearecent_updatesthe latest updates, anywhere, in a project or by a personnew_builderswho joined recently: first commits in the last daystrendsdevelopers and commits per month over two yearssearch_lessonsLessons from real fixes, by wordsget_lessonOne lesson in full, with its sourcelessons_from_projectWhat one project taughtcheck_codeYour code against the lessonslist_areasThe topics of the lessons
Agents that read llms.txt find all of this at https://pulse.lusocryptolabs.com/llms.txt.
Let your agent check the lessons by itself
Paste this into the AGENTS.md or CLAUDE.md of your CKB project. Your agent then reads the lessons before it writes transaction code, and checks its code against them when it is done.
## CKB lessons
This project builds on Nervos CKB. The CKB Pulse MCP server (https://pulse.lusocryptolabs.com/mcp) holds lessons from real fixes in other CKB projects.
- Before writing or changing code that builds, signs or reads CKB transactions, scripts, witnesses, since values, capacity or indexer queries, call search_lessons with the functions involved and read the lessons that match with get_lesson.
- After writing that code, call check_code with it and go through every lesson it returns before you finish.
- Each lesson links to the commit it came from. When a lesson and the current library docs disagree, follow the docs and say so.
Setup in Claude Code: claude mcp add --transport http ckb-pulse https://pulse.lusocryptolabs.com/mcpLessons on every pull request
A GitHub Action for your CKB project: on each pull request it comments with the lessons that apply to the lines that changed, repeated mistakes first. Copy this to .github/workflows/ckb-lessons.yml. Only the changed lines go to Pulse, and they are not stored.
name: CKB lessons
on:
pull_request:
permissions:
contents: read
pull-requests: write
jobs:
lessons:
runs-on: ubuntu-latest
steps:
- uses: LusoCryptoLabs/ckb-pulse-action@v1