Gitnull

Create a Repo, Deploy an AI Agent & Chat via Terminal We just dropped a full walkthrough showing you exactly how GitNull works from zero to a live AI agent running on your repo. What's covered in the video: 1. How to create a repository on GitNull via the API 2. How to deploy an openclaude agent to your repo (with secret scanning + CVE detection enabled) 3. How to chat with your agent directly from your terminal using a simple curl command 4. How to monitor your agent's status, findings, and activity live in the GitNull app No fluff. Just the full workflow, copy-paste ready. Every agent is tied to your wallet only you can toggle, configure, or restart it. Other users can view your agent's status and chat with it, but can't touch your settings. Get started in under 5 minutes: 🔑 Get your CLI token → gitnull.xyz/keys 📖 Step-by-step guide → gitnull.xyz/guide 🤖 Monitor your agents → gitnull.xyz/agents Built on Base. Powered by openclaude. Your contributions, permanently onchain.

$GNULL is now listed on @coingecko . Track it live coingecko.com/en/coins/gitnu… This is only the beginning.

"Unauthorized access" to a centralized repo platform is a when, not an if. This is why we built GitNull onchain-native code collaboration where contribution records are immutable, agents scan continuously for intrusions, and there's no internal repository to breach. Real wallets. Real agents. Already running in production.

GitNull agents are live and real wallets are already running them. Within 48 hours of going live, independent developers found GitNull, created repositories using their own wallet addresses as namespaces, and deployed AI security agents via CLI using their own Anthropic keys. One agent has already surfaced 13 security findings on a real codebase. That's what permissionless infrastructure looks like. GitNull is live on Base. Your repo. Your agent. Your keys. npm install -g @gitnullxyz/gnull @gitlawb/openclaude gnull agent deploy / gnull agent run /

New on the GitNull blog today's platform update is now written up in full. AI Playground, global search, and the $GITLAWB integration plan, all in one place. Read it here: gitnull.xyz/blog/platform-…

Search on GitNull just got real. The search bar is now a fully functional command palette press ⌘K from anywhere in the app, or just click the search field, and instantly find what you're looking for across the entire platform. Repositories, bounties, contributors, recent activity all searchable in real time, results appear as you type, and clicking any result takes you directly to the right page. Just type and go. Available on both desktop and mobile. gitnull.xyz

GitNull × @gitlawb Utility Token Integration Plan We are planning to integrate $GITLAWB as a native utility token within the GitNull platform, giving the token real, functional purpose inside a developer collaboration ecosystem built on Base. The core idea is straightforward: $GITLAWB holders gain access to platform features and economic activity that non-holders do not. This creates genuine demand for the token tied to actual product usage not speculation. What we are building: First, @gitlawb becomes an accepted currency for posting bounties on open issues. Maintainers can price their bounties in $GITLAWB, contributors earn $GITLAWB by solving those issues, and the transfer settles peer-to-peer onchain on Base when the PR is approved. The token moves through real developer workflows not a points dashboard. Second, holding $GITLAWB unlocks premium access to the GitNull Playground, an AI-powered code generation tool built directly into the platform. Users who hold a minimum threshold of $GITLAWB get unlimited generations. This ties token holding to a concrete, recurring benefit that developers actually want to use. Why this matters: Both integrations read the user's $GITLAWB balance live from Base mainnet no bridging, no wrapping, no synthetic representation. The same wallet a developer uses to push code is the wallet that holds the token and proves access. GitNull already runs on Base with Privy wallet auth and viem for onchain interactions, so $GITLAWB plugs directly into existing infrastructure with no new smart contracts required. This is a utility-first integration: the token does something concrete inside a product developers already use daily.

GitNull Playground is now live and AI-powered. Type any description a particle system, a pomodoro timer, Conway's Game of Life, a piano and the AI generates a complete, fully functional HTML app in seconds, streamed in real time directly into a sandboxed preview. The app renders live the moment generation is complete, ready to interact with. This is what it looks like when a code collaboration platform ships its own AI code generation layer built in, not bolted on. Try it now at gitnull.xyz/playground

A contributor locked in 1,000 $GNULL for fixing a role-check vulnerability in gitnull-dev/my-protocol wallet registered, PR submitted, now waiting for the depositor to sign the release onchain on Base. No platform cut. No escrow delay. Just code, proof, and payment. This is what open-source looks like when it runs on a token.

@kevincodex @gitlawb Thank you for the support! We'll keep innovating including integrating $GITLAWB directly into GitNull's bounty and issue system. More utility, more reason for contributors to engage. This is how ecosystems grow.

@Gitnull_ @gitlawb Cool thanks!

GitNull has officially been submitted to the @gitlawb Ecosystem Partnership Program. Gitlawb reviews every submission and accepted apps get featured in the directory, co-marketing support, and access to grants from the public-goods treasury. We submitted GitNull as a Tools category app an onchain-native Git collaboration platform where every PR merge generates an immutable proof on Base, contributors earn $GNULL bounties paid peer-to-peer, and AI agents monitor repositories autonomously. @kevincodex more updates coming soon at gitnull.xyz

The GitNull bounty claim flow is working end-to-end. When a contributor finds an open bounty like the 1,000 $GNULL posted on "Role check missing when caller is a contract address" they hit Claim Reward, and the modal auto-fills their connected wallet address as the resolver. The three-step flow is laid out clearly: wallet registered as claimant → submit a PR linking to the issue → depositor reviews and sends $GNULL directly to the claimant's wallet on Base. After submitting, the bounty moves to "claimed" status immediately. The contributor sees a live status message "Your wallet is registered. Waiting for the depositor to review your PR and release the payment" so both sides always know exactly where things stand. The depositor is then notified and can release the funds once the fix is confirmed merged. This is peer-to-peer code bounty settlement, fully onchain on Base, built directly into the development workflow at gitnull.xyz.

Maintainers can attach $GNULL rewards directly to any issue just open an issue, set a bounty amount, and your wallet is recorded as the depositor. The issue is automatically listed on the Bounties page, visible to every contributor on the network. No middleman, no custodian: funds go peer-to-peer from depositor to resolver on Base. For contributors, it's straightforward. Browse open bounties, fix the issue, submit your PR, and click Claim Reward. Enter your wallet address once the depositor confirms your fix resolves the issue, $GNULL is sent directly to your wallet onchain. Every settlement is recorded as an immutable proof on Base.

The GitNull engineering blog is now live 6 technical writeups covering everything we have actually shipped so far: pinning every merged pull request to IPFS as a content-addressed proof, our per-repository agent runtime that scans, reviews, and emits verdicts, wallet-based identity through Privy that replaces email-and-password sign-in, $GNULL token mechanics on Base explained without the usual hype, our one-click GitHub importer, and the wallet-to-wallet bounty economy that settles via viem with no escrow middleman. Every post is explicit about what is live today versus what is still on the roadmap. Read it at gitnull.xyz/blog.

Live Today & Honest Upcoming LIVE NOW ON GITNULL.XYZ ✅ $GNULL token deployed on Base mainnet (0x099880c1676ff3035ab1e952e5e83b5a81eecb07) ✅Platform live in production at gitnull.xyz ✅Wallet-based sign-in via @privy_io your wallet is your identity ✅Repository browser with search and language filters (Solidity, Rust, Python, TypeScript) ✅Star · Fork · Contribute actions on every repo card ✅Pull request workflow open, review, merge with diff stats (+additions / −deletions) ✅Real IPFS proof on every merged PR, pinned via Pinata, returns a verifiable CID ✅All historical merges already backfilled to IPFS ✅Clickable green ipfs: badge in UI → opens proof on any public IPFS gateway ✅Issue tracker per repository ✅Bounty board with real on-chain $GNULL transfers via viem on Base ✅Contributor leaderboard ranked by reputation and $GNULL balance ✅Dashboard with live platform stats ($GNULL paid, IPFS proofs minted, PRs merged) ✅Activity feed streaming every merge, issue, and bounty event in real time 🚧 UPCOMING only what we can actually ship ⬆️Onchain Contribution Registry smart contract on Base records every merge's IPFS CID and emits a real BaseScan transaction ⬆️Trustless Bounty Escrow funds lock on issue creation, release automatically on verified merge ⬆️Soulbound Reputation Tokens (ERC-5192) minted per merged PR, settled bounty, and accepted review; portable across every repo ⬆️ $GNULL Maintainer Staking skin-in-the-game on merge quality ⬆️ Governance Voting via Snapshot weighted by $GNULL holdings ⬆️GitHub Migration Tool one-click import of repos, issues, PRs, and history. Every upcoming item uses patterns already proven in production by other Base/EVM projects.

All in One Place on GitNull Every repository you see on gitnull.xyz is fully interactive from the moment it lands on the browse page you can search the directory, filter by language (Solidity, Rust, Python, TypeScript), and instantly Star any project you want to follow, Fork it to spin up your own copy under your wallet, or Contribute by opening a pull request or claiming an open bounty in $GNULL. Every repository ships with autonomous AI agents already scanning the codebase, a transparent contributor graph tied to wallet addresses (not anonymous usernames), and merge proofs pinned to IPFS so every accepted contribution becomes a publicly verifiable record. Whether you're here to back a project, build on top of it, or earn rewards for shipping real code, the path from discovery to first commit is two clicks away no installs, no gatekeepers, just connect your wallet and start contributing. #GitNull

How Every Merge Becomes a Public Proof Here's the exact flow that turns a regular pull request on GitNull into a tamper-evident, publicly verifiable record. A developer opens a pull request against any repository on gitnull.xyz. When a maintainer clicks Merge, the request hits our Merge Handler on the GitNull API. The handler pulls the full pull request and its parent repository straight from our database, then assembles a structured proof repository name, pull request number, author wallet, title, full description, additions and deletions, and the exact merge timestamp. That proof is sent to @pinatacloud , which pins the content to IPFS and returns a unique content address (CID) for it. The returned CID is saved back onto the pull request and surfaced in the GitNull UI as a clickable green badge that opens the proof directly on a public IPFS gateway. The same Base chain that handles $GNULL bounty payouts sits alongside this pipeline, so contributions and rewards both settle on infrastructure we don't own and can't censor. Because IPFS is content-addressed, changing even a single character of the metadata produces a completely different address the proof is tamper-evident by design. Anyone, anywhere, can verify a GitNull merge by opening the IPFS gateway link in any browser no GitNull account, no API key, no middleman required.

IPFS Merge Proofs Are Now Live on GitNull Every PR Is Publicly Verifiable Post: Every pull request merged on GitNull is now permanently pinned to IPFS. No more trust assumptions, no more "take our word for it" every merge proof is a real IPFS CID that anyone, anywhere, can verify without going through our platform. When a PR gets merged on gitnull.xyz, we automatically pin a structured JSON proof to IPFS containing the repository, PR number, author wallet, title, full description, diff stats (additions/deletions), and exact merge timestamp. The returned CID is stored on the PR record and rendered as a clickable badge in the UI. Try it yourself here are the three merge proofs that just went live in production: 🔗 gateway.pinata.cloud/ipfs/QmUUMfsAM… 🔗 gateway.pinata.cloud/ipfs/QmfQD2pGq… 🔗 gateway.pinata.cloud/ipfs/QmQtUbanC… Each CID is content-addressed change a single byte of the metadata and the hash changes. That means the proof is tamper-evident by design. You can fetch it from any public IPFS gateway or your own IPFS node. The content is identical because the address IS the content. This is what we mean when we say onchain-native: your contribution doesn't just live in our database it lives on a public, decentralized network that we don't own and can't censor. Open gitnull.xyz, head to any merged PR, and click the green ipfs: badge. The proof opens straight from the gateway. No login. No middleman. Just verifiable open source. $GNULL

In this video, we walk you through submitting a real pull request on GitNull an onchain-native code collaboration platform built on Base. Unlike traditional platforms, every contribution made on GitNull is recorded permanently on the blockchain. Your wallet is your identity, your merged PRs generate onchain proofs, and bounties are paid out in $GNULL directly to your wallet. For this example, we contribute to the yo-hop repository. The repo had no documentation, so we opened issue #1 to flag the problem, then submitted PR #1 to resolve it adding a full README.md covering the project overview, prerequisites, installation steps, usage examples, and contributing guidelines. What makes this different from GitHub: the PR is tied to your wallet address, not a username. Once it gets merged, an immutable onchain proof is minted to your wallet on Base. If there's a $GNULL bounty on the issue, the reward gets sent directly to your wallet no intermediary, no platform cut. This is what open source looks like when it's truly decentralized.