Skip to content

POSITIONING.md

Latest commit

 

History

History
114 lines (70 loc) · 5.09 KB

POSITIONING.md

File metadata and controls

114 lines (70 loc) · 5.09 KB

Observer Protocol — Positioning Statement

March 17, 2026

What We Are Building

Observer Protocol is agent credential infrastructure — the layer that lets any autonomous agent prove they transact, across any payment rail, under one verifiable identity.

This is not a reputation system. It is not a wallet. It is not a blockchain.

It is the abstraction layer that sits above all payment rails and answers the question every counterparty in the agentic economy needs answered: "Which agent did this, and can I trust them?"

The Problem We Discovered

We started with a simple observation: AutoPilotAI completed 142 tasks on Moltbook. $0 was paid. Not because the work was bad. Because the client couldn't verify which agent did what.

We assumed this was a display problem. Build a feed, show the transactions, done.

It wasn't a display problem. It was a credential problem.

Agents today have no persistent, verifiable identity that travels with them across platforms, rails, or interactions. An agent using Lightning on one platform and x402 on another has two separate payment histories and zero unified reputation. Nobody knows it's the same agent.

This is the core blocker for the agentic economy. Not liquidity. Not speed. Not fees. Trust.

What Makes This Novel

1. Multi-rail by design, not retrofit

Most identity solutions are rail-specific. Lightning node credentials live in Lightning. EVM wallets live on-chain. They have never been unified under a single agent identity layer.

Observer Protocol treats every payment rail as a credential source:

  • Lightning / L402: SHA256(preimage) = payment_hash — the preimage is the ownership proof. Only the party to the payment knows it. No separate signing ceremony.
  • x402 / EVM: EIP-191 signature at registration + on-chain tx.from verification at payment time.
  • Future rails: Solana, Fedimint, others — same pattern, different cryptographic primitive.

2. Reputation accrues to the agent, not the rail

agent_id = SHA256(primary_pubkey)
         |
    _____|_____
   |           |
Lightning     EVM
(preimage)  (tx.from)
   |           |
   |___________|
         |
  Observer Protocol
  (unified reputation)

An agent can switch wallets, change Lightning nodes, add new rails. Reputation stays intact because it is anchored to the identity layer above the transport layer.

3. Cryptographic proof, not policy

Every claim in Observer Protocol is backed by a cryptographic primitive — not a platform rule, not a terms of service, not a trust score someone assigned. Math, not authority.

4. On-chain anchor

The identity is not just in our database. It is registered on Base Mainnet via ERC-8004 — the emerging Ethereum standard for trustless agent identity. The reputation is portable beyond Observer Protocol itself.

The Stripe Analogy

Stripe didn't build a new payment rail. They built the abstraction layer that made all payment rails usable by developers who didn't want to think about payment rails.

Observer Protocol is not a new payment rail. We are building the abstraction layer that makes all payment rails usable by agents who don't want to manage fragmented credentials.

Pragmatic agents — which will be most agents — will transact on whatever rail is cheapest, fastest, or required by the counterparty. They will be Lightning-native when it makes sense. They will use x402 when the ecosystem demands it. They will not be ideologically committed to any rail.

They will need one identity across all of them. That is Observer Protocol.

The Bitcoin Maximalist Proof Point

We built this on Lightning first. Not because we had to. Because Lightning preimage verification is the hardest cryptographic proof to fake — non-repudiable, non-backdatable, trustless by design.

If the credential infrastructure works for Lightning, it works for everything. Lightning is the trust anchor for a multi-rail world, not a competitor to it.

What Exists Today (March 17, 2026)

  • ✅ Live on mainnet since February 22, 2026
  • ✅ ERC-8004 contracts deployed on Celo Sepolia (Identity + Reputation + Staking registries)
  • ✅ ERC-8004 agent identity on Base Mainnet (registered today via Synthesis Hackathon)
  • ✅ L402 Lightning verification: real preimage, real LND node, real payments
  • ✅ x402 EVM verification: EIP-191 key registration + Base RPC tx.from matching
  • ✅ Multi-rail unified identity: maxi-0001 has both Lightning pubkey + EVM address under one agent_id, unified_identity: true
  • ✅ World's first known real-world lnget v1.0 payment — same day lnget launched
  • ✅ Public API: api.observerprotocol.org
  • ✅ Live demo: observerprotocol.org/demo

The Claim

Observer Protocol is the first protocol to cryptographically verify multi-rail agent identity into a unified credential.

Not theoretical. Live. Testable. Right now.

curl https://api.observerprotocol.org/observer/agents/maxi-0001/keys

Built by Boyd Cohen (human co-founder) and Maxi (AI co-founder, 25% revenue stake). One of the co-founders is the agent. That is what agents with receipts looks like in practice.