Summary
Commito is a workspace for people who build and maintain open-source software. It gathers what happens in the repositories you follow, commits, pull requests, contributors and open issues, into one view read live from GitHub. On top of that it offers one small on-chain primitive: a contribution record that points at a real commit or pull request, signed by the person who did the work, which another person can co-sign as reviewer.
The code never moves. Only references and hashes go to Robinhood Chain, where they stay public and checkable without asking Commito for anything.
The problem
- Work is scattered. A contributor active in five projects has five notification streams, five issue trackers and no single picture of what is moving.
- Reviews disappear. Reviewing is real work, yet it leaves little trace outside the repository where it happened, and nothing a reviewer can point to later.
- Claims are hard to check. "I contributed to X" on a profile is easy to write. Checking it means digging through history by hand.
- Newcomers cannot find a start. Good first issues exist, but they are spread across repositories nobody follows yet.
The idea
Keep GitHub as the home of the code and the conversation, and add two thin layers: a reading layer that merges what you follow, and a recording layer that lets people sign what they did and what they checked. Each record is small enough to verify in a browser in seconds, and a review is meaningful only because it comes from a different wallet that put its own signature next to the work.
The system
1. Repository Hub
A list of public repositories kept in your browser. For each one the site reads stars, forks, open issues, languages, topics, license and the last push from the public GitHub REST API. Answers are cached on the server for minutes; when the anonymous quota is used up, your browser reads GitHub with its own quota. Without any configuration this needs no account and no key.
2. Workspaces and contributors
The Commit Explorer, the Pull Request Workspace and Open-Source Tasks merge the same questions across the first eight repositories of your hub. Pull requests show their state and, on request, their review trail: who approved, who asked for changes. The Contributor Dashboard merges GitHub's contributor lists by login.
3. Contribution records
CommitoRecordBook is a contract with no owner, no admin, no fee and no upgrade path. record(repo, ref, kind, role, noteHash) stores the lower-case repository path, the full commit SHA or pull request number, a role and the hash of an optional note, and computes the hashes itself. A wallet can record each exact reference once. review(id) lets any other wallet co-sign a record, once. Everything is readable with paginated view calls, and block numbers come from Robinhood Chain's own L2 counter.
4. Verify
The verify page reads a record, recomputes keccak-256 of the repository path and the reference in your browser, compares them with the chain, and checks on GitHub that the commit or pull request exists.
Pulse
Repository cards show a Pulse from 0 to 99, a reading aid computed only from public numbers: up to 50 points for recency (50 × 0.5^(days since last push ÷ 30)) and up to 49 for reach (49 × log10(1 + stars + forks) ÷ 5.5, capped). Archived repositories score 0. Pulse says how alive and visible a project is; it says nothing about code quality, and it never decides what you see first unless you sort by it.
Trust & abuse
- A record proves that a wallet made a claim at a moment, not that the wallet belongs to the GitHub author. Link your wallet from your GitHub profile if you want others to make that connection.
- Anyone can create wallets, so a review is only as strong as the reviewer behind it. Every review shows its address; judge reviewers, not counts.
- The book refuses self-reviews and counts each reviewer once per record. There is no admin who could delete, edit or hide a record, so nothing can be quietly changed later; it also means mistakes stay public.
- Notes never go on chain, only their hash. Do not record anything you would not want to be public forever.
Token
$COMMITO is the community token of Commito on Robinhood Chain. Today no feature depends on it. Its possible uses, credits for the planned Developer API, a premium workspace and consented verification services, are plans, and they will be described here before anything goes live. The token carries no promise of value, income or reward. Token page.
Roadmap
| Step | Delivers | State |
|---|---|---|
| 0 · Hub | Repository Hub, Commit Explorer, Pull Request Workspace, Contributor Dashboard, Open-Source Tasks, all on public GitHub data | Live |
| 1 · Records | CommitoRecordBook on Robinhood Chain: record, second-wallet review, verify page (practice mode until deployment) | Built, deployment pending |
| 2 · Connect | Connect repositories you own or may read, with your permission; team views | Planned |
| 3 · Developer API | Contribution data per repository, wallet and reviewer; webhooks; export | Planned |
| 4 · Agent tools | Tools for coding assistants to search a hub and prepare records; signing stays with the person | Planned |
| 5 · $COMMITO uses | API credits, premium workspace, consented wallet-to-account verification | Planned |
Risks
- Records and reviews are public and permanent on Robinhood Chain. They cannot be edited or removed by anyone, including the Commito team.
- The record book is small and fully tested, but it has not been through an independent security review yet. It holds no funds.
- GitHub data can be delayed by caching, limited by rate limits, or change after you read it. Always open the original on GitHub.
- $COMMITO is a community memecoin. It has no promised value, returns, revenue share or reward, and its price can go to zero. Never put in money you need.
- Planned features may change or never ship.