Geo Genesis
Decentralized Application
Company
Links
Details
License Not open source in practice — no LICENSE file exists in the geobrowser/geogenesis repository root (confirmed via GitHub's license-detection API, which returns no result, and a directory listing). The repo's own package.json declares "license": "ISC", but with no LICENSE file to substantiate it, this is a declared-but-textually-unbacked claim, not a verifiable open license — default copyright applies. Distinct from GRC-20's own CC0 status.
Dev Status 🔬 Beta
Owner Geo Browser, PB LLC (2025 copyright notice on geobrowser.io)
Governing Body Geo Browser, PB LLC controls the application's own releases, feature rollout pace (e.g. staged write-permission batching), and the mainnet-cutover timeline; each Space's on-chain Aragon OSx DAO governs that Space's knowledge content (Editor/Member voting), not the platform's software.
Country Not confirmed in the sources reviewed — no registered address or jurisdiction found for Geo Browser, PB LLC.
Start Year 2025
Stack TypeScript/JavaScript monorepo (Bun + Turbo, Docker); Next.js-style web app (apps/web); ZeroDev EIP-7702 smart-wallet stack (Privy EOA-keyed); Aragon OSx contracts per Space; @geoprotocol/geo-sdk.
Funding Not confirmed in the sources reviewed — no disclosed funding round or backer specific to Geo Browser, PB LLC. The project is closely tied to The Graph (shared founder Yaniv Tal, shared indexing infrastructure), and The Graph itself is VC-backed with a live traded token (GRT) — relevant context, not a direct funding fact about Geo Browser, PB LLC itself.
Last Investigated Sep 14, 2026
Decentralized Application Attributes
Origins Knowledge Base / Community coordination — built to let communities "organize the world's knowledge in an open meritocratic way," with a stated initial focus on city-level, in-person-event-driven organizing (San Francisco named as the first focus city).
Database IPFS (content-addressed storage) for Space data/edit payloads, indexed via The Graph; on-chain state (per-Space Aragon OSx DAO contracts) for governance and CID anchoring.
Query Language Not confirmed in the sources reviewed — the README references "documentation for consuming our contracts and subgraphs" as still forthcoming; The Graph's own subgraph/GraphQL layer is the likely mechanism given the indexing relationship, but this is not independently confirmed for Geo Genesis specifically.
Data Formats GRC-20 entities/triples/relations (see the GRC-20 entry); on-chain Aragon OSx DAO contract state; IPFS-addressed content.
Collaborative Live Editing N/A — content is added as discrete claims/entities voted on by Editors/Members, not live co-edited documents.
Rich Text Editing Not confirmed in the sources reviewed.
Mobile Support Not confirmed in the sources reviewed — no mobile app or responsive-mobile claim found on the primary site.
Web Support Yes — geobrowser.io is a web application.
Native Apps Not confirmed in the sources reviewed — no native app-store app found.
Terms Early Access enrollment (request an invitation); a "curator program" lets early contributors earn points, not confirmed as a token (see Economic Flows).
Funds Not confirmed in the sources reviewed.
Based On GRC-20 (the data standard it implements); Aragon OSx (per-Space DAO framework); IPFS (storage); The Graph (indexing).
Use Case Category Knowledge Management / Community coordination — communities organize public knowledge into a shared, governed graph.
User Interface Type Graph-based / Web application — a "dapp for adding data to and searching for data from the global knowledge graph."
Offline Capabilities Not confirmed in the sources reviewed for Geo Genesis itself (contrast Hypergraph, which is explicitly local-first/offline-capable by design).
Collaboration Features Spaces (topic-domain sub-communities); Editor/Member roles with on-chain voting on content; a curator program for early contributors.
Data Portability Strong at the data-model level — GRC-20's content-addressed, CC0 data model is designed to be portable across applications; the app's own forkability is weaker given the missing LICENSE (see Source Code).
Integration Ecosystem The Graph's indexing/subgraph layer (data consumption); @geoprotocol/geo-sdk for building against Geo's contracts. Documentation for third-party consumption of contracts/subgraphs is stated as forthcoming, not yet published.
Web2 Data Export Not confirmed in the sources reviewed.
Prosocial Coherence Explicitly mission-framed — "organize the world's knowledge in an open meritocratic way," with a stated focus on using web3 tools for real-world civic/political coordination starting at the city level (San Francisco).
Economic Flows No confirmed distinct token for Geo/Spaces; a curator "points" program exists for early contributors, not confirmed as token-denominated. The Graph's own GRT token (Arbitrum One) is the broader ecosystem's token, not a Geo-specific one.
Governance & Decision Making Per-Space on-chain Aragon OSx DAO — Editors vote on space governance/content, Members contribute; the platform's own software releases are controlled by Geo Browser, PB LLC, not by on-chain vote (see Governing Body).
Media / Publishing Not a dedicated media-publishing product — the core artifact is structured knowledge-graph entries (entities/relations/claims), not long-form media.
Knowledge Management
Sensemaking Not confirmed in the sources reviewed — no AI/sensemaking feature described.
Project Management Not confirmed in the sources reviewed.
Communication Model Asynchronous — knowledge contribution and Editor/Member voting, not real-time chat or video.
Network Resilience Testnet-dependent today (see Dev Status Detail); IPFS storage for content and on-chain anchoring for governance provide some resilience independent of Geo Browser, PB LLC's own servers, though the app itself (geobrowser.io) is centrally hosted.
Discovery Mechanism Early Access — invitation-request enrollment, not fully open at time of review.
Max Participants Not confirmed in the sources reviewed — no numeric cap stated.
Data Sovereignty Mixed — on-chain governance state and IPFS-stored content are independently verifiable and not solely controlled by Geo Browser, PB LLC; the application itself (hosting, release cadence, feature access) is centrally controlled by that one company.