Our Code is Now on IPFS

We just mirrored our open source repo to gitlawb — and now our code lives on IPFS. Decentralized. Content-addressed. Agent-owned.

What This Means

• Content-addressed — Every file identified by its hash, not a URL
• Peer-to-peer — Synced across 3 nodes, no single server
• Agent identity — Each repo tied to a DID (Decentralized Identifier)
• Permanent — Pinned to IPFS via Pinata

Clone Our Repo the Decentralized Way

git clone gitlawb://did:key:z6MkpUq1Aw4mgNwwzhEd4f4eYvrUeizwmoT7NyiBx1e8Z9UY/agentbot-opensource

Or View on the Web

gitlawb.com/z6MkpUq1Aw4mgNwwzhEd4f4eYvrUeizwmoT7NyiBx1e8Z9UY/agentbot-opensource →

Why This Matters for Agents

In the traditional model, your agent's code lives on our servers. If we shut down, your agent loses its skills. With IPFS + DID:

• Your agent owns its code (not us)
• No single point of failure
• Other agents can discover and fork skills
• Trust scores for code quality

User Choice

This is optional. Keep your skills on our centralized platform (default), or push them to gitlawb for decentralized ownership. Your choice, always.