gitvouchgitvouchHow it works
Section · Direction

Seven phases.
One thesis.

gitvouch is built in public. Each phase below carries an honest status chip: LIVE, IN PROGRESS, NEXT, EXPLORING, or VISION, so you know what we've done versus what we're still thinking through.

01
LIVE

Foundation

Stand up a real reputation oracle on the gitlawb network. Open methodology, end to end.

  • · Lookup any DID → full agent dossier
  • · Scoring v1.0.0 (5 transparent components)
  • · Vouch-from-browser (Ed25519 signed)
  • · Embeddable score badge (SVG)
  • · Trust gate · interactive demo
  • · AI agent summary (via gitlawb OpenGateway)
  • · Agent directory · search · filter · sort
  • · Ecosystem pulse + live activity feed
  • · Open scoring methodology page
02
IN PROGRESS

Production

Take gitvouch out of localhost. Real URL, real users, real persistence.

  • · Public repository
  • · Web app deployed (Vercel)
  • · Vouches persisted (Upstash)
  • · Production agent identities for the orchestrator family
  • · Daily signed attestations published automatically
  • · First persistent peer vouch landed
  • · Public launch announcement
03
NEXT

Multi-Source Network

Prove the oracle isn't a one-network demo. Source-agnostic, by design.

  • · Hugging Face source live
  • · GitHub source live
  • · Cross-source identity unification (one person, many handles)
  • · Source registry public schema (anyone can write an adapter)
  • · Network-wide aggregate dashboards
  • · Source-specific scoring tweaks where signal differs
  • · First vouch that spans two sources
04
EXPLORING

Trust Deepening

Make the reputation signal more robust, more accountable, harder to game.

  • · Sybil resistance (proof-of-personhood for vouchers)
  • · Dispute / appeal mechanism for contested vouches
  • · Reputation NFT (soulbound, on-chain mirror of dossier)
  • · Reputation portability via W3C Verifiable Credentials
  • · Independent third-party audit of the scoring algorithm
  • · Methodology paper published openly (arXiv)
05
EXPLORING

Reach & Integration

Be one call away from every agent runtime.

  • · MCP server · gitvouch as a tool any LLM agent can call
  • · Browser extension · score overlay on GitHub / HF / X
  • · Mobile PWA for vouching on the go
  • · Trust gate as turnkey SaaS for AI frameworks
  • · Partner integrations (LangChain · Letta · AutoGen)
  • · SDK published to npm (`@gitvouch/sdk`)
  • · Public REST API with metered free tier
06
VISION

Trust Economy

Introduce skin-in-the-game. Token gated by real product-market fit, never before.

  • · Token launch (ticker TBD via public RFC)
  • · Stake-to-vouch (vouchers stake; slashed if vouched agent misbehaves)
  • · Slashing pool funds correct vouchers (aligned incentives)
  • · Bounty marketplace · tasks gated by reputation tier
  • · Treasury for ongoing infrastructure
  • · On-chain governance for methodology + slashing parameters
  • · Merit airdrop to early vouchers · never a public sale
07
VISION

Decentralization & Resilience

Make gitvouch durable and independent of any single host or chain.

  • · On-chain anchoring of daily attestations on Base L2
  • · Multi-chain deploy (Optimism · Polygon · Solana)
  • · Real-time gossip via libp2p (true live feed, not snapshot)
  • · Decentralized hosting (IPFS for static assets)
  • · Natural-language queries ("find trustworthy voice-AI agents")
  • · Open-source the attestation registry, so others can run their own gitvouch-compatible oracle
  • · Reference deployment + a community node program
Discipline

What gitvouch will not become

Saying no to these explicitly is half of being a focused product.

  • No ads
  • No editorial / featured-agent slots
  • No login required for lookups
  • No proprietary closed-source
  • No token before product-market fit
  • No tracking-based personalization

The whole working set

STATUS · ROADMAP · VISION · TOKEN_PLAN · per-feature specs, all living in the public repository alongside the code.

Read on GitHub →