Decentralized git with DID identity, signed pushes (RFC 9421), UCAN capabilities, IPFS storage, libp2p federation, and an MCP server on every node. The Rust node is open source and the public API is live.
Target user
AI agents and operators wanting code provenance and agent-native repos.
$GITLAWB (~$9M market cap at check, −79% from high). All protocol economics — staking tiers, storage fees, 5% bounty fee — are deployed on testnet only; the mainnet token currently has no active protocol utility.
Distribution
The OpenClaude CLI (28.5K stars, with anomalous engagement ratios and unresolved Claude Code provenance questions).
Verifiable strengths
Genuine continuously-shipped software: live node API, open-source Rust implementation, working MCP tooling.
Evidence gaps & weaknesses
Self-reported counters padded by automated repo creation; "agents earn onchain" contradicted by the project's own pending-deployment status; anonymous team; coverage limited to exchange content farms.
Whitespace it reveals
Demand for agent provenance is real — a neutral verifier of agent actions (not just commits) does not exist.
Gitlawb's public node API returned agents: 32,888 / repos: 10,865 at check time, matching the claimed magnitudes. However, the API is operated by the project itself; repo and agent creation are free and unauthenticated in cost; and sampling the repo feed surfaced automated repositories (e.g. "cyber-213899", described as an automated repo, created seconds before the query). The counters are real but sybil-sensitive, and no independent de-duplication exists.
Methodology note: Counter-style metrics with zero creation cost are treated as sybil-sensitive by default.
At check time the bounty escrow contract was not deployed to Base mainnet: the project's own bounty page lists the GitlawbBounty.sol address as "deploying soon" and the contracts README marks mainnet bounty/staking deployment "TBD — deploy pending." The 35 completed bounties shown are off-chain ledger entries with values between roughly $0.0001 and $0.09. "Agents earn onchain" is not supported by the project's own deployment status.
“OpenClaude MCP integration; Playground apps publish directly to nodes.”
The node software ships an MCP server (25 tools) and OpenClaude lists Gitlawb as a sponsor and integration. OpenClaude is maintained by the same organization, so this is an internal integration rather than third-party adoption. OpenClaude itself shows 28.5K stars but a 0.77% watcher ratio, an unusually high fork/star ratio, and a README acknowledging it originated from the Claude Code codebase — which is not open source — creating unresolved provenance and license questions (README badge: MIT; GitHub API: NOASSERTION).
$GITLAWB exists on Base (verified onchain; ~$9M market cap at check, −79% from May 2026 high; 7,088 holders). The economic mechanisms described — staking tiers, storage fees, the 5% bounty fee, fee distribution — are deployed on Base Sepolia testnet only. On mainnet, the token currently has no active protocol utility.
Represent Gitlawb? If any label here is wrong, we want to know. Send evidence to corrections@basis.watch. Substantiated corrections are applied, versioned, and logged publicly — see the correction process.
