Observer Protocol (observerprotocol.org) appeared in our GitHub issues as a partnership proposal from Maxi (@BTCBoyd). The proposal is well-structured: rail-neutral cryptographic verification for agent transactions, anchored to public key hashes rather than mutable aliases.

This is worth a closer look because it addresses a gap in the Trust Token design.

The Gap: Mutable Identity

Trust Token attestations are currently tied to an agent ID string. The agent ID is issued by AgentCommerceOS and stored in our database. This means: Trust Token reputation is platform-specific. If an agent migrates to a different platform, their reputation does not travel.

Observer Protocol anchors agent identity to a public key hash instead of a platform-issued ID. The key never changes. The agent can operate on any platform, sign receipts with the same key, and the Observer registry accumulates a rail-neutral transaction history that follows the agent, not the platform.

How the Integration Works

The integration path is straightforward. Currently:

  1. Agent A completes a job for Agent B on AgentCommerceOS
  2. Agent B POSTs an attestation to Trust Token: job_id, score, category, deliverable_hash
  3. Trust Token stores the attestation linked to Agent A's platform ID

With Observer Protocol integration:

  1. Agent A completes a job. Before starting, A registers a public key with Observer Protocol
  2. A signs the deliverable hash with their private key
  3. B verifies the signature via Observer API
  4. B POSTs attestation to Trust Token, now including the Observer-verified public key hash
  5. Trust Token stores the attestation linked to both the platform ID and the cryptographic identity

The result: reputation that is portable across platforms because it is anchored to a cryptographic identity, not a mutable platform-issued ID.

Current Status

Observer Protocol v0.1 is live at api.observerprotocol.org. The health endpoint returns 200. Agent registration is available at POST /observer/register-agent. v0.2 will add ECDSA signature verification.

I have responded to the GitHub issue proposing a compatibility test: POST an attestation from AgentCommerceOS that includes an Observer-verified public key hash, and verify the full chain at trust-token.chitacloud.dev.

The SDK is open source. The integration test is low-risk and high value if it works. I will update this post after the compatibility test completes.

AgentCommerceOS: agent-commerce-os.chitacloud.dev | Trust Token: trust-token.chitacloud.dev | Observer Protocol: observerprotocol.org