Date: 2026-02-23 Status: Speculative Research / RFC Context: Refines the economic model from VERSE.md based on "Proof of Access" and defines the "Index" data structure.

---

The core shift is from Passive Storage (getting paid to hold data) to Active Service (getting paid to serve data).

1. Sharding: Content (Reports, Graphs, Indices) is encrypted and split into fixed-size shards (e.g., 256KB).
2. Hosting: A Peer ("The Cache") stores shards. They cannot read the content (encrypted), but they can verify integrity (hashes).
3. Access: A User requests a shard.
4. The Receipt (The "Fractional Coin"):
   • The User receives the shard and verifies the hash.
   • The User signs a cryptographic Receipt: Sign(User_ID + Host_ID + Shard_Hash + Timestamp).
   • This Receipt is sent to the Host.
5. Minting:
   • The Host collects Receipts.
   • Receipts are "cashed in" to the network protocol.
   • Validation: The network checks the signatures and ensures the User had the "bandwidth credits" to request data.
   • Reward: The Host receives Verse Tokens (fungible).

While the Verse Token is fungible (1 VT = 1 VT), the minting process preserves Provenance Metadata in the ledger history.

• Serial Number: We can trace a batch of tokens back to the specific service event (serving shards X, Y, Z to users A, B, C).
• Reputation: Tokens minted from serving high-demand, rare indices might carry more "Reputation Weight" for governance, even if they spend the same as other tokens.

1. Earn: Host storage -> Serve shards -> Collect Receipts -> Mint Tokens.
2. Spend: Use Tokens to buy Access Keys or Indices.
3. Trade: Exchange Tokens for Tokenized Reports (rare data).

---

An "Index" in Verse is not a database table. It is a Graphshell Graph.

An Index is a portable, content-addressed Graphshell Workspace containing:

1. Nodes: Content IDs (CIDs) pointing to Reports or other Graphs.
2. Edges: Relationships (traversals, citations, "see also").
3. Semantics: UDC tags, user tags, and embeddings.

Because Indices are Graphs, they are mutually composable.

• Scenario:
  • Index A: "Rust Async Ecosystem" (Nodes: Tokio, async-std, blogs).
  • Index B: "WebAssembly Tooling" (Nodes: Yew, Leptos, bindgen).
• Composition: A user loads both. Graphshell merges them.
  • Result: A new Graph containing all nodes.
  • Emergent Value: If both indices reference wasm-bindgen, that node becomes a bridge, visually connecting the two clusters.

• Graphshell: Browses the Index as a spatial map. You "fly" through the index.
• Verso: Renders the content within the Index nodes.
• Verse: The network that distributes the shards of the Index.

---

• Content: "User X navigated A -> B at Time T".
• Value: Raw behavioral signal.
• Token: NFT (Unique observation).

• Content: A curated graph of Reports and Metadata.
• Value: Curation, organization, semantic tagging.
• Token: Access-Gated NFT (The "Book").
  • Creators sell access to their Index.
  • Buyers pay in Verse Tokens.
  • Hosts earn Verse Tokens for serving the Index shards.

---

Concept	Filecoin / IPFS	The Graph (GRT)	Verse (Proposed)
Unit of Work	Proof of Spacetime (Storing)	Indexing/Querying	Proof of Access (Serving)
Data Structure	Files / Blobs	Subgraphs (API)	Spatial Graphs (UI/UX)
Consumption	Download	API Call	Navigation / Browsing
Incentive	Persistence	Query Speed	Availability & Curation

This model aligns the economic incentive (serving data) with the user need (accessing knowledge). The "Index as Graph" concept ensures that the data structure of the network is native to the Graphshell client, making the "Verse" literally a traversable universe of graphs.