GNS Protocol

Geospatial Naming System — The Identity Layer the Internet Never Had

Patent Pending #63/948,788 · IETF Internet-Draft draft-ayerbe-trip-protocol-02 (co-authored with Usama Sardar, IETF RATS WG)

$ curl https://gns-browser-production.up.railway.app/v1/verify/@camiloayerbe

{
  "verified": true,
  "handle": "@camiloayerbe",
  "trust_score": 90.68,
  "breadcrumb_count": 933,
  "verification_level": "maximum",
  "chain_valid": true
}

1. The Problem

Digital identity is fundamentally broken.

• Billions of accounts controlled by corporations that can suspend you at any moment
• Passwords and 2FA are constantly breached and phished
• No way to prove you're human without giving up your biometric or personal data
• Bot armies and Sybil attacks plague every platform, from airdrops to social media

Authentication services like Auth0 and Okta can answer "is this the right user?" but they cannot answer the more fundamental question: "is this a real human?"

2. Solution: Proof-of-Trajectory

Prove you're human by how you move through the world.

Instead of scanning your eyeball, GNS builds trust through behavioral proof: your unique pattern of movement over time creates an unforgeable signature that only a real human being can produce.

How It Works

1. Generate Keys: Your phone creates a cryptographic key pair. This IS your identity.
2. Collect Breadcrumbs: As you move, your phone signs location proofs (breadcrumbs) that form a tamper-proof chain.
3. Build Trust: After 100 breadcrumbs, claim your permanent @handle. Your trust score grows with your history.
4. Use Everywhere: Your @handle works for messaging, payments, email, and authentication across the ecosystem.

Identity Dashboard

Breadcrumb Chain

Trajectory Criticality Engine Live Demo

Flocking Energy H v3 — Real-time human vs. bot classification using Parisi k=7 criticality analysis, IMU cross-correlation, and power spectral density.

PSD Analysis

Power Spectral Density detects 1/f criticality — the signature of natural human movement absent in bots.

Gyration Radius

2D trajectory visualization with radius of gyration. Humans show bounded exploration; bots show mechanical patterns.

IMU Cross-Correlation

GPS turn rate vs gyroscope correlation (r > 0.9 = real device). Spoofed GPS shows zero IMU correlation.

Phase Space

Speed vs turn rate attractor map. Human trajectories cluster in characteristic phase-space regions.

Open Live Demo ↗

3. The Platform: Live Today

Not a whitepaper. A working platform built on the GNS Protocol.

4. ULissy Language — The Foundation

GNS Protocol is built on ULissy — a domain-specific programming language designed for machines that move through physical space. 26,000 lines of Rust, full compiler pipeline, 74/74 TRIP protocol tests passing, CI green, live browser playground.

Why a New Language?

Moving machines (phones, vehicles, drones, wearables) need specialized abstractions. ULissy treats identity, location, time, cryptography, and energy as first-class language primitives rather than library imports.

// Collect breadcrumbs to prove humanity
identity me = Keychain.primary

every 10.minutes when battery > 20% {
    let cell = here.h3(10)
    let prevHash = me.trajectory.last?.hash ?? "genesis"
    let hashInput = "\(cell)|\(now.millis)|\(prevHash)"
    
    let crumb = Breadcrumb {
        cell: cell,
        timestamp: now,
        hash: sha256(hashInput),
        signature: me.sign(hashInput)
    }
    
    me.trajectory.append(crumb)
}

250 Lines → 15 Lines

The same algorithm in traditional languages requires 200-300 lines of code with manual coordination between GPS APIs, cryptographic libraries, secure storage, and battery management.

// Initialize keychain
let keychain = Keychain::new()?;
let identity = keychain.get_or_create("primary")?;

// Setup location manager
let config = LocationConfig {
    accuracy: kCLLocationAccuracyHundredMeters,
    distance_filter: 100.0,
    activity_type: .other,
};
let manager = LocationManager::new(config);

// Battery check
let battery = UIDevice.current.batteryLevel;
if battery < 0.2 { return; }

// Get current location
let location = manager.current_location().await?;
let h3_index = h3::from_geo(
    location.latitude,
    location.longitude,
    10
)?;

// Build chain
let prev = storage.get_last_breadcrumb()?;
let prev_hash = prev.map(|b| b.hash)
    .unwrap_or("genesis".to_string());

// Hash computation
let input = format!("{}|{}|{}",
    h3_index,
    SystemTime::now()
        .duration_since(UNIX_EPOCH)?
        .as_millis(),
    prev_hash
);
let hash = Sha256::digest(input.as_bytes());

// Sign
let signature = identity
    .private_key
    .sign(input.as_bytes())?;

// Create breadcrumb
let crumb = Breadcrumb {
    index: prev.map(|b| b.index + 1).unwrap_or(0),
    timestamp: SystemTime::now(),
    cell: h3_index,
    hash: hex::encode(hash),
    signature: hex::encode(signature),
    // ... more fields
};

// Store
storage.append_breadcrumb(&crumb)?;
// ... 200+ more lines for error handling,
// background tasks, platform abstractions...

identity me = Keychain.primary

every 10.minutes when battery > 20% {
    let cell = here.h3(10)
    let prevHash = me.trajectory.last?.hash 
                  ?? "genesis"
    let hashInput = "\(cell)|\(now.millis)|\(prevHash)"
    
    let crumb = Breadcrumb {
        cell: cell,
        timestamp: now,
        hash: sha256(hashInput),
        signature: me.sign(hashInput)
    }
    
    me.trajectory.append(crumb)
}

// That's it. Compiles to Rust.
// Runs on iOS, Android, Desktop.

ULissy Benefits

// Find verified electricians nearby — ranked by trust
let results = search nearby(2.km)
    where trust > 0.5, facet == "services"
    ranked by trust desc

// Safe unwrapping of identity lookups
let alice = search @alice
if let peer = alice {
    let proof = peer.proof
    print("Trust: \(peer.trust), epochs: \(proof.epoch_count)")
}

ULissy v0.4.2 — What's New

5. Strategic Positioning

Protocol first, platform later.

GNS is positioning as the humanity verification primitive that existing auth providers will integrate, not compete against.

The Positioning Stack

Why Auth0 Would Integrate GNS

1. New Value Proposition: "Is this human?" is a question Auth0 cannot currently answer
2. No Conflict: GNS adds to their offering, doesn't replace it
3. Standard Protocol: OIDC-compatible, easy integration
4. Growing Demand: Bot protection is every platform's problem

6. GNS API v1

Core Endpoints

OAuth 2.0 / OIDC Integration

GNS works as a standard identity provider:

// Add "Login with GNS" to your app
const gnsAuth = new GNSAuth({
  clientId: 'your-client-id',
  redirectUri: 'https://yourapp.com/callback',
  scope: 'openid profile humanity'
});

// User clicks login
gnsAuth.authorize();

// Handle callback
const { handle, trustScore, verified } = await gnsAuth.handleCallback();

if (verified && trustScore > 0.8) {
  // Proceed with high-value action
}

7. Technology Stack

The Complete Stack

Cryptographic Primitives

8. Business Model: Commercial Open Source (COSS)

GNS follows the Commercial Open Source Software (COSS) model — the same playbook used by GitLab, Elastic, HashiCorp, MongoDB, and Confluent to build billion-dollar companies on open-source foundations.

Open-Source Layer (MIT License)

The protocol and developer tools are fully open source, maximizing adoption and community contribution:

Commercial Layer (Proprietary)

Revenue comes from managed services, enterprise features, and premium API tiers that organizations need at scale:

API Pricing Tiers

Why COSS Works for GNS

1. Network effects: Every open-source implementation that collects breadcrumbs adds value to the entire verification network. More nodes = harder to fake trajectories = more valuable verification.
2. Protocol lock-in without vendor lock-in: Companies can run their own TrIP nodes (open source), but most will pay for managed infrastructure — just as most companies use GitHub instead of self-hosting Git.
3. IETF credibility: The TrIP Internet-Draft establishes GNS as an open standard, not a proprietary platform. Enterprise buyers trust IETF-track protocols.
4. Developer-first distribution: Free API tier and open-source tools let developers adopt GNS before procurement gets involved — the bottom-up enterprise sales motion.

9. Investment Thesis

$400K pre-seed via YC Post-Money SAFE at $4M valuation cap.

What Has Been Built (Solo Founder, Zero External Capital)

• Complete protocol implementation — mobile, desktop, web, backend, blockchain
• IETF Internet-Draft published — revision -02, co-authored with IETF RATS WG member (draft-ayerbe-trip-protocol-02)
• Provisional patent filed (#63/948,788) — US jurisdiction
• Domain-specific programming language with working compiler
• 933+ breadcrumbs proving the system works in production
• Live API serving real verification requests
• 10B token supply deployed on Stellar mainnet
• COSS business model with six commercial revenue streams defined (including Orbital TrIP — live today)

Why $4M Valuation Cap

Use of Funds ($400K)

US Market Entry Strategy

1. Delaware C-Corp: Standard US fundraising structure. SAFE converts on the next priced round. Italian entity (ULISSY s.r.l.) becomes IP-holding subsidiary or is restructured as needed.
2. Target verticals: Space insurance (Orbital TrIP — revenue-ready today with live data), US platforms facing bot/fraud problems — ad-tech (ad fraud is a $84B/year problem), fintech (KYC costs $60-$500 per customer), social platforms (Sybil attacks), and AI companies needing proof-of-humanity for training data.
3. Regulatory alignment: US Executive Order 14110 on AI safety calls for identity verification standards. NIST is developing AI identity frameworks. GNS's IETF-track protocol positions it as a standards-compliant solution for federal and enterprise buyers.
4. Distribution: Developer-first (free API tier → bottom-up adoption) combined with direct enterprise outreach through IETF/NIST credibility.

Milestones to Seed Round ($2-3M at $15-20M)

Why Now

1. AI makes identity urgent: Deepfakes, AI-generated content, and bot armies are making "is this human?" the defining question of the next decade. Every US platform needs an answer — from social media to financial services.
2. Regulatory tailwind: US Executive Order 14110 on AI safety, NIST AI frameworks, and state-level privacy laws (California CCPA, Texas Data Privacy Act) are creating demand for new identity infrastructure that doesn't rely on centralized biometric databases.
3. Biometric backlash: WorldCoin's iris scanning has faced bans in multiple countries and growing US skepticism. The market wants a non-biometric, privacy-preserving alternative.
4. IETF timing: The TrIP Internet-Draft creates a 6-month window to establish GNS as the trajectory-based identity standard before competitors can draft competing specifications.
5. Cost advantage: GNS verification costs $0.01 vs $0.07+/MAU for Auth0 and $60-500 per KYC check. In the US ad-tech market alone, this price differential at scale represents massive value capture.

10. GNS Token

Native utility token on Stellar blockchain.

• Total Supply: 10 billion GNS
• Initial Distribution: 200 GNS + 2 XLM to each new @handle claim
• Use Cases: Premium features, protocol fees, governance

Stellar Wallet

Send & Receive

11. Organization Namespaces

B2B revenue through corporate identity management.

12. Market Opportunity

Total Addressable Market

• Space Insurance: $630M premium market (179% loss ratio), 45,000+ trackable objects, ~30-50 broker firms globally — Orbital TrIP is live today
• US Ad Fraud: $84 billion/year globally, $35+ billion in the US alone — bot verification is the core problem
• Identity Verification: $12 billion → $30 billion by 2030 (US is 40% of global market)
• Enterprise IAM: $18 billion/year (Okta, Auth0, etc. — primarily US customer base)
• Decentralized Identity: $2 billion → $100+ billion by 2030
• US KYC/AML Compliance: $8 billion/year — banks spend $60-$500 per customer on verification

Competitive Landscape

12.5. Orbital TrIP — Lead Commercial Vertical

Space object identity via Proof-of-Trajectory. The first vertical that generates revenue without consumer adoption.

Three-Tier Attestation Architecture

Critically, Orbital TrIP does NOT require onboard hardware. Like DNS, the registry assigns identity based on external observation:

Four-Layer Revenue Architecture

Orbital TrIP captures value across four distinct layers, each targeting a different buyer with a different willingness to pay. The public registry (ICANN model) remains free — all revenue flows through Globe Crumbs Inc.

Layer 1: Analytical API Subscriptions (Data-as-a-Service)

Layer 2: Parametric Trigger Fees (Success-Based)

Parametric insurance pays out automatically when a pre-defined threshold is met. TrIP provides the independent verification that triggers the payout — eliminating manual claims adjustment.

Layer 3: Compliance Audit Reports

Satellite operators pay for certified TrIP compliance reports to demonstrate responsible behavior and negotiate lower insurance premiums. Regulators increasingly require debris mitigation evidence.

Layer 4: White-Label Underwriting Integration

Deep integration into the internal pricing engines of major reinsurers (Munich Re, Swiss Re, AXA XL). Licensed platform deployment with real-time webhooks that alert their risk systems the moment a satellite's Trust Score drops.

Stakeholder Summary

Revenue Projections (Four-Layer Model)

Live Demo

The Orbital TrIP public registry is live now at orbital-trip-production.up.railway.app — tracking 70+ satellites with live CelesTrak data, Ed25519 breadcrumb chains, trust scoring, and 5 narrative "story satellites" including Russia's GEO stalker (Luch/Olymp-K2) and the ISS ASAT shelter event.

13. Traction and Status

Built and Deployed

• Mobile app (Flutter) — iOS and Android
• Desktop app (Tauri) — Mac, Windows, Linux
• Web identity explorer (Panthera Browser)
• Backend infrastructure on Railway
• GNS API v1 — Proof-of-Humanity, OAuth 2.0, Webhooks, Payments
• Stellar blockchain integration (mainnet)
• GNS token issued (10 billion supply on Stellar)
• End-to-end encrypted messaging
• Email bridge (SMTP gateway)
• Organization namespace registration
• ULissy v0.4.2 compiler — 26,000 lines of Rust, 5 crates, 64 token types, 18 statement types
• 74/74 TRIP protocol tests passing with GitHub Actions CI (build + test + lint)
• EBNF grammar specification: 93 production rules (docs/GRAMMAR.md)
• Browser playground: live tokenizer + AST + Rust preview (gns-foundation.github.io/ulissy/playground)
• VS Code extension with syntax highlighting and diagnostics
• TrIP Search primitives — 4 query targets, typed filters, compile-time privacy enforcement
• IETF Internet-Draft published: draft-ayerbe-trip-protocol-02 (revision -02, co-authored with Usama Sardar, IETF RATS WG)
• TrIP Search Whitepaper v0.2 — spatial-identity discovery specification
• Orbital TrIP public registry — 70+ satellites tracked live, Ed25519 breadcrumb chains, trust scoring, 5 story satellites
• Orbital TrIP White Paper v0.2 — ICANN model for space object identity, insurance API architecture
• Flocking Energy v3 — live trajectory criticality engine (anti-spoofing demo)

Live Production Data

Founder Identity: @camiloayerbe

• 933 breadcrumbs collected
• 90.68% trust score
• "maximum" verification level
• Chain valid: All cryptographic proofs verified

IP Protection & Licensing

• Provisional Patent #63/948,788 filed for Proof-of-Trajectory innovation
• IETF Internet-Draft — draft-ayerbe-trip-protocol-02 (revision -02, co-authored with Usama Sardar from IETF RATS Working Group)
• TrIP Search Whitepaper v0.2 — Spatial-identity discovery specification (13 sections)
• ULissy Language Whitepaper v0.4.2 — open-source (MIT License)
• EBNF Grammar Specification — 93 production rules, formally specified
• GNS Commercial Services — proprietary (COSS model, advised by Heather Meeker)

14. IETF Standardization Roadmap

TrIP is on track for formal IETF standardization. Co-authored with Usama Sardar from the IETF Remote Attestation Procedures (RATS) Working Group, providing internal advocacy within the IETF ecosystem.

15. Glossary