Docs
Search…
0.0.1
Welcome
Introduction
The Next Computing Paradigm
What is an AR Metaverse?
What is a public good?
Who owns the Geo Web?
Getting Started
Quick Start Requirements
Use Cases
Core Concepts
Digital Land
Partial Common Ownership
Digital Land Registry
Cadastre
Land Transactions
Spatial Browsing
Network Funds
Developers
Architecture Overview
Cadastre Interface
Smart Contracts
Geo Web Subgraph
Identity
Content Layer
IPFS
Ceramic
Persistence & Storage
Spatial Browsers
Community & Governance
Open Org
SourceCred
Geo Web DAO
Powered By GitBook
Content Layer
The Geo Web is envisioned as a peer-to-peer network. The current implementation uses IPFS and Ceramic to link, publish, and retrieve content.
The core protocols of the internet and web were designed to enable peer-to-peer (p2p) communication, but client-server architectures still dominate today. Many of the biggest issues of Web 2.0 (winner-take-all economics, the attention economy, and censorship) can be traced back to the dynamics created by this architecture. For the Geo Web to fulfill its promise as a permissionless, egalitarian network, its full stack must be and remain decentralized.
While the security and data availability guarantees offered by Ethereum smart contracts are necessary for the Geo Web’s digital land market operations, the Geo Web’s content layer calls for a different set of tools. The Geo Web needs dynamic, efficient, but still decentralized content linking, transmission, and storage. The user experience offered must match or exceed the convenience and cost effectiveness offered by Web 2.0 architectures.
We're still in the early days of Web 3.0, but we we're well on our way to delivering on this goal with a content layer consisting of IPFS, Ceramic, and Filecoin.
Developers - Previous
Identity
Next
IPFS
Last modified 4mo ago
Copy link