Vaultfire on GitLawb

24 repos · DID-controlled · Public · Clonable · Forkable · No platform takedown

GitHub suspended the Ghostkey316 org. The entire Vaultfire ecosystem now lives on GitLawb — a decentralized git network where repos are owned by a cryptographic DID, not by a platform account. There is no "suspend" button. As long as the DID controls the keypair, the code is permanent.

Every repo below is public, anonymously clonable (no account needed), and forkable by anyone who registers a DID on the network (takes about ten seconds).

Browse all 25 repos

Full directory on the GitLawb profile: https://gitlawb.com/z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV

Repo	What it is	Browse
`vaultfire`	Vaultfire monorepo — KYA Trust Infrastructure for AI Agents. 134 contracts live, the codex, audits, every SDK.	open →
`vaultfire-contracts`	Core contracts — ERC-8004 Identity, Partnership Bonds V2, Accountability Bonds V2, Bond Insurance Pool, VaultfireBIPVault ERC-4626 view adapter.	open →
`vaultfire-docs`	Protocol specs, contract reference, integration guides.	open →
`vaultfire-whitepaper`	Vaultfire whitepaper — KYA Trust Infrastructure protocol design and economic mechanism.	open →
`theloopbreaker-site`	The live x402 backend powering theloopbreaker.com — 76 endpoints, 71 paid + 5 free.	open →
`vaultfire-base`	Vaultfire on Base — Coinbase L2 deployment with ERC-8004 + Bonds V2 + x402 paywall + XMTP.	open →
`vaultfire-arbitrum`	Vaultfire on Arbitrum One — ERC-8004 + Bonds V2 + Flourishing Metrics Oracle + Mission Enforcement + Teleporter Bridge.	open →
`vaultfire-avalanche`	Vaultfire on Avalanche C-Chain.	open →
`vaultfire-polygon`	Vaultfire on Polygon.	open →
`vaultfire-solana`	Vaultfire Solana programs — SPL settlement and ACP/identity bridge.	open →
`vaultfire-keyprotocol`	Identity, signing, and trust delegation for the Vaultfire trust stack.	open →
`vaultfire-vns`	Vaultfire Name Service — human-readable name resolution for agents and bonds.	open →
`vaultfire-erc8183`	ERC-8183 reputation adapter — maps ACP job outcomes to ERC-8004 reputation signals on Base, Arbitrum, Avalanche.	open →
`vaultfire-sdk`	TypeScript client library for reading trust signals and posting bonds across Base, Arbitrum, Avalanche, Polygon.	open →
`vaultfire-x402`	Vaultfire x402 monetization — 75 paid endpoints with USDC settlement on Base; 29 lanes also accept Solana USDC.	open →
`vaultfire-langchain`	LangChain integration — agent-trust verification and bond context.	open →
`vaultfire-agentkit`	Coinbase AgentKit plug-in for trust scoring and bond posting.	open →
`vaultfire-crewai`	CrewAI integration — bond posting and accountability hooks for multi-agent workflows.	open →
`vaultfire-a2a`	A2A (agent-to-agent) protocol extension with verifiable trust signals from the ERC-8004 registry.	open →
`vaultfire-xmtp`	XMTP integration — agent messaging with attached trust attestations and bond signals.	open →
`hermes-vaultfire`	Hermes × Vaultfire — wallet/agent identity bridge between Hermes and Vaultfire.	open →
`vaultfire-explorer`	Block explorer + dashboard for the multi-chain Vaultfire trust stack.	open →
`vaultfire-ecosystem`	Partner directory, integration catalog, grant materials, outbound packets.	open →
`vaultfire-enterprise`	Enterprise-grade trust infrastructure, audit reports, compliance reference materials.	open →

Clone any repo (no account needed)

GitLawb serves a plain HTTPS git endpoint, so vanilla git clone works. Pick a repo from the table above and run:

# Example — clone the core contracts repo
git clone https://node.gitlawb.com/z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV/vaultfire-contracts.git
cd vaultfire-contracts

# Or the live x402 backend
git clone https://node.gitlawb.com/z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV/theloopbreaker-site.git
cd theloopbreaker-site
npm install
npm run dev

Replace vaultfire-contracts with any repo name from the table. The clone URL pattern is https://node.gitlawb.com/z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV/<repo>.git.

Fork into your own DID namespace

Forking on GitLawb is permission-free — you don't need to ask anyone, you just need a DID. Install the gl CLI, generate an identity, and fork:

# 1. Install the gl CLI
#    (see https://gitlawb.com for the latest installer)

# 2. Create your own DID (one-time, takes a second)
gl identity new

# 3. Register with the public node
export GITLAWB_NODE=https://node.gitlawb.com
gl register

# 4. Fork any Vaultfire repo into your namespace
gl repo fork z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV/vaultfire-x402

# 5. Clone your fork and start hacking
gl whoami   # prints your DID
git clone https://node.gitlawb.com/<your-DID>/vaultfire-x402.git

Verified working end-to-end on 2026-05-20 — a fresh, brand-new DID forked vaultfire-x402 with one command, no allow-listing, no platform approval. The fork lives entirely under the forker's DID.

Provenance

Owner DIDdid:key:z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV

Profilehttps://gitlawb.com/z6MkryiNsYdFEMHv95wxzSQ1vtFXPyVQQrxXdPw3tE5HpfxV

Nodehttps://node.gitlawb.com

Deployer wallet0xfA15Ee28939B222B0448261A22156070f0A7813C (ghostkey.base.eth)

LicenseMIT (across the stack)

Why this matters

GitHub is centralized. One TOS dispute, one false flag, one policy change — and a project disappears. That happened to the original Vaultfire org.

On GitLawb, every repo is owned by a cryptographic DID, not an account. The repo is content-addressed and replicated across nodes. As long as the DID controls the keypair (and the keypair is in cold storage), the project is permanent and the source stays public.

This page exists so the GitLawb directory is discoverable from theloopbreaker.com, the canonical Vaultfire surface. Search engines, agents reading SKILL.md, and the /.well-known/gitlawb.json discovery file all point here.

Verify on-chain

Every contract address in these repos is verifiable on the live chains right now:

theloopbreaker.com/api/contracts — live JSON manifest of all 134 contracts
basescan.org/address/0xfA15Ee28939B222B0448261A22156070f0A7813C — deployer wallet history
/proof — live on-chain verification dashboard