​

Why it matters

Networks don’t run on vibes; they run on client software. Client diversity affects resilience, decentralization and upgrade risk, but implementations are scattered across GitHub orgs and documentation pages.

Structuring client software in Geo makes the operational layer discoverable and supports research into client diversity and network health.

What to publish

Update-first (no duplicates)

  • Search Geo using the client’s canonical GitHub repo or org (and website if available). If a client entity already exists, update it. Only create a new entity if none exists.

Create Project entities for client software and fill the client-software-specific fields you already have:

  • Primary language

  • Software license

  • GitHub (repo)

  • GitHub stars (optional)

  • Actively maintained (checkbox)

  • First release

  • Latest version

  • Latest release date

  • Key maintainers (optional)

Also add general Project fields where useful:

  • Website URL

  • Docs URL

  • X, Discord, Telegram, LinkedIn

  • Launched

Add relations:

  • Client Project → Network (the chain(s) it supports)

  • Client Project → Related projects (e.g., the foundation or company behind it) when publicly stated

Recommended classification (in Topics or Tags):

  • execution client

  • consensus client

  • full node

  • validator client

  • rollup node

  • sequencer node

Scope

  • 20-40 client software projects, covering:

    • Ethereum clients (execution and consensus)

    • Solana, Jito clients where applicable

    • Cosmos SDK chain clients at the framework level

    • Major L2 node stacks where they are distinct projects

  • Focus on widely used and clearly maintained clients.

Potential sources

  • Network documentation listing supported clients

  • Client GitHub repos and release pages

  • Foundation and client team documentation pages

  • Ecosystem “run a node” guides

Quality rules

  • Avoid per-chain duplication: if one client serves many Cosmos chains (Cosmos SDK), model it once and link appropriately.

  • One entity = one identity: avoid duplicates under slightly different names.