Skip to content

Nip 101: UPlanet#2108

Open
papiche wants to merge 31 commits intonostr-protocol:masterfrom
papiche:NIP-101
Open

Nip 101: UPlanet#2108
papiche wants to merge 31 commits intonostr-protocol:masterfrom
papiche:NIP-101

Conversation

@papiche
Copy link

@papiche papiche commented Nov 1, 2025

Add NIP-101: UPlanet - Decentralized Identity & Geographic Coordination

Summary

This NIP introduces a comprehensive protocol for decentralized identity management, geographic coordination, and verifiable credentials on Nostr. It extends the protocol with four integrated systems:

  1. Hierarchical GeoKeys - Nostr keypairs derived from geographic coordinates
  2. Decentralized Identity (DID) - W3C-compliant identities stored as Nostr events
  3. Oracle System - Multi-signature permit management using Web of Trust
  4. ORE System - Environmental obligations attached to geographic cells

Event Kinds

This NIP introduces the following event kinds:

  • 30800: DID Document (W3C-compliant decentralized identifiers)
  • 30500: Permit Definition (license/certification types)
  • 30501: Permit Request (applications with evidence)
  • 30502: Permit Attestation (peer validation signatures)
  • 30503: Permit Credential (issued W3C Verifiable Credentials)
  • 30312: ORE Meeting Space (extends NIP-53 for environmental verification)
  • 30313: ORE Verification Meeting (compliance verification events)

Key Features

1. Self-Sovereign Identity

  • No centralized registries required
  • W3C DID Core and Verifiable Credentials compliant
  • Multi-chain support (Nostr, IPFS, Ğ1, Bitcoin)

2. Peer-Validated Credentials

  • Community-based competence certification
  • Web of Trust bootstrap mechanism
  • Multi-signature attestation requirements
  • Transparent audit trail on Nostr

3. Geographic Coordination

  • Location-based Nostr feeds (UMAP, SECTOR, REGION levels)
  • Deterministic key generation from coordinates
  • Enables localized communication and services

4. Environmental Accountability

  • Decentralized ecological commitment tracking
  • Integration with meeting spaces (NIP-53 compatible)
  • Economic incentives for compliance

Compatibility Notes

  • Kinds 30312-30313: Extends NIP-53 meeting spaces with geographic and ecological metadata
  • Fully compatible with NIP-01, NIP-10, NIP-33, and NIP-42

Implementation

Use Cases

  1. Community-based driver's licenses - Peer-validated competence certification
  2. Professional certifications - Medical, legal, artisan, educator credentials
  3. Local coordination - Geographic Nostr feeds for neighborhoods and cities
  4. Environmental tracking - Transparent ecological commitment with economic incentives

Testing

The protocol has been in production since 2024 on the UPlanet network, with active use by the Ğ1 libre currency community and CopyLaRadio SCIC cooperative.


Related: This NIP complements NIP-53 (Live Activities) and NIP-99 (Classified Listings) while avoiding kind number conflicts.

Authors: papiche (@papiche), CopyLaRadio SCIC
Status: Draft for community review
Discussion: NIP-101 Repository

…ation. Added details for image thumbnails, clarified NOSTR event tags for deduplication, and updated upload process to include file hash checks.
… types: NIP-94 file metadata and NIP-22 video comments, increasing the total synchronized event types from 18 to 20.
…ficial extensions to 8. Updated overview and details for geographic chat functionality, including integration with ORE System.
…ration timestamp for encrypted voice messages, and include new analytics extensions in UPlanet overview.
@fiatjaf fiatjaf changed the title Nip 101 Nip 101: UPlanet Nov 13, 2025
papiche and others added 16 commits November 13, 2025 23:19
…nsion, including SSSS-based authentication, geographic key delegation, and smart contract integration. Update event types and clarify implementation processes, increasing the total synchronized event types from 18 to 21.
… economic health extension, increasing synchronized event types from 20 to 40
…ily for economic health broadcasts and reports
…ocumentation to reflect daily publication frequency for station economic health reports
…ate UPlanet documentation to include new economic features for forest garden acquisition
…o Commons Crowdfunding System and update contribution event details to use kind 7 with multi-currency support
…among stations, emphasizing their uniqueness and read-only sharing across the swarm
…r stations, including steps for peer discovery, P2P tunnel creation, and event synchronization, enhancing the understanding of the N2 constellation network
…ng publication frequency to daily and clarifying report structure and query patterns
…to 45, reflecting the addition of new event types and updating relevant documentation
…efining media and comment types, and enhancing documentation for clarity and accuracy
@papiche
Copy link
Author

papiche commented Feb 1, 2026

Supplement to the PR description — data not covered in the opening post:

The opening post lists 7 event kinds (30800, 30500–30503, 30312, 30313). This PR also introduces or references the following UPlanet-related kinds defined in the included extension documents:

Additional event kinds (extnsions)

Kind(s) Name Document
30850 Economic Health Report 101-economic-health-extension.md
30852 Economic alert (planned) 101-economic-health-extension.md
30904 Crowdfunding campaign 75-crowdfunding-extension.md
31900–31902 Cookie workflow (definition, instance, completion) 101-n2-constellation-sync-extension.md, 101-cookie-workflow-extension.md
31910 N² development memory (AI recommendations, TODOs) 101-n2-constellation-sync-extension.md
30009, 8, 30008 Badge definitions, awards, profile badges (NIP-58) 58-oracle-badges-extension.md — emitted when Oracle credentials (30503) are issued

Constellation synchronization

UPlanet relays synchronize a broader set of event kinds across the constellation (N² protocol, backfill_constellation.sh in the NIP-101 repo):

  • Core: 0, 1, 3, 5, 6, 7
  • Media / files / comments: 21, 22, 1063, 1111, 1222, 1244, 1985, 1986
  • Content & lists: 8, 30008, 30009, 30023, 30024, 30001, 30005, 10001, 30315
  • Channels (NIP-28): 40, 41, 42, 44
  • UPlanet identity & systems: 30800, 30500–30503, 30312, 30313, 30850, 31900–31902, 31910
  • Crowdfunding: 30904
  • Analytics: 10000

So in total ~45 event kinds are documented as synced; some deployments use a smaller “minimal” set (e.g. core + UPlanet identity + Oracle + ORE + economic). This is described in 101.md (Constellation Synchronization table) and in 101-n2-constellation-sync-extension.md.

papiche and others added 3 commits February 2, 2026 01:18
…ntation for SECTOR and REGION levels, enhancing clarity on channel discovery and message structure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant