Opportunity for Zero Authority DAO to be the human coordination layer - zeroauthority-dao/mission GitHub Wiki

An interesting opportunity for Zero Authority is to take the architecture idea behind MCP and apply it to human coordination, rather than AI context.

MCP essentially says: β€œAny application can expose standardized capabilities, and any compatible client can discover and use them.” MCP standardizes tools, resources, and prompts between applications. ([GitHub]1)

Zero Authority could create the equivalent for people, reputation, work, opportunities, and rewards.

The concept: People Context Protocol

I'd frame it as:

PCP β€” People Coordination Protocol

An open protocol for connecting people, organizations, agents, and opportunities.

Or potentially a more brandable:

CAP β€” Contribution Access Protocol

The open protocol for connecting people to work, reputation, and rewards.

The fundamental idea:

MCP connects applications to AI. Zero Authority connects applications to people.

What Zero Authority would standardize

Today, every platform has its own:

  • user profiles
  • reputation
  • jobs
  • bounties
  • applications
  • credentials
  • payments
  • messaging
  • contributor history

A person might have a reputation on GitHub, Discord, X, Zero Authority, Stacks, etc., but those systems don't naturally understand one another.

Zero Authority could define a common protocol.

A person becomes a portable identity.

For example:

person://grimaldo.btc

An application could ask:

GET /person/grimaldo.btc

and receive standardized information:

{
  "identity": "grimaldo.btc",
  "skills": [
    "design",
    "content",
    "community"
  ],
  "reputation": {
    "score": 4215,
    "network": "zero-authority"
  },
  "contributions": 127,
  "credentials": 18,
  "completed_work": 94
}

The important part isn't the API.

It's the standard.

Then add "Opportunities"

This is where it gets really interesting for ZA.

An application could publish:

opportunity://zeroauthority/bounty/123

with standardized fields:

{
  "type": "bounty",
  "title": "Create a Bitcoin explainer",
  "reward": {
    "amount": 500,
    "asset": "STX"
  },
  "skills": [
    "writing",
    "bitcoin",
    "education"
  ],
  "deadline": "2026-10-01",
  "verification": "onchain"
}

Now any application can publish an opportunity into the network.

Not just Zero Authority.

The third primitive: Contribution

This could be the killer piece.

Instead of simply saying:

"Zero Authority has a bounty."

You create a standardized way to represent:

A person did something valuable.

For example:

contribution://12345

{
  "person": "grimaldo.btc",
  "type": "content",
  "organization": "stacks",
  "opportunity": "bounty/123",
  "status": "completed",
  "verified": true,
  "reward": {
    "amount": 500,
    "asset": "STX"
  }
}

That contribution can then become part of the person's portable reputation.

So the protocol has 5 core objects

I'd keep the initial protocol extremely simple:

1. Identity

Who are you?

PERSON

Wallet, BTC name, social accounts, optional credentials.

2. Reputation

What have you actually done?

REPUTATION

Contributions, credentials, verified work, participation.

3. Opportunity

What can you contribute to?

OPPORTUNITY

Gigs, bounties, grants, quests, jobs, tasks.

4. Contribution

What did you actually do?

CONTRIBUTION

Work submitted, event attended, code shipped, content created, governance participation, etc.

5. Reward

What did you receive?

REWARD

BTC, STX, tokens, credentials, reputation, access, etc.

Then applications become "clients"

This is where the MCP analogy becomes powerful.

Imagine:

GitHub

"I want to find contributors with Bitcoin + Rust experience."

GitHub queries the protocol.

Discord

"Show the reputation of this contributor."

Discord queries the protocol.

AIBTC

"Find people who completed Bitcoin development bounties."

AIBTC queries the protocol.

Wallet

"Show opportunities available to this person."

Wallet queries the protocol.

AI agent

"Find me three verified designers who have completed Bitcoin-related work."

Agent queries the protocol.

Zero Authority

"Here are 500 opportunities from across the ecosystem."

ZA consumes and publishes through the same protocol.

This changes what Zero Authority is

Today the story is approximately:

Zero Authority = platform

But the bigger vision could become:

Zero Authority = coordination protocol

The website becomes just one interface to the protocol.

Similar to how MCP isn't "the Claude website."

It's infrastructure that other applications can implement.

MCP's current model separates servers and clients and lets servers expose standardized tools/resources to clients. ([Model Context Protocol]2)

ZA could do something similar:

                  ZERO AUTHORITY PROTOCOL
                           β”‚
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚                  β”‚                  β”‚
     People           Opportunities       Contributions
        β”‚                  β”‚                  β”‚
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           β”‚
                     Applications
                           β”‚
       β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
       β”‚            β”‚      β”‚      β”‚            β”‚
    Discord      GitHub   Wallet   AI       Zero Authority

The really important part: "Connect"

I would make Connect the primary verb.

Not:

Create a Zero Authority profile.

Instead:

Connect your people layer.

A person connects their:

  • Bitcoin wallet
  • BTC name
  • X
  • GitHub
  • Discord
  • Telegram
  • Stacks activity
  • existing credentials
  • previous contributions

Then ZA creates a portable contribution identity.

The user doesn't necessarily need to "live" on ZA.

They can exist across the ecosystem.

And developers get an SDK

Something like:

npm install @zeroauthority/protocol

Then:

import { ZA } from "@zeroauthority/protocol";

const person = await za.people.get("grimaldo.btc");

const opportunities = await za.opportunities.search({
  skills: ["design", "bitcoin"]
});

Or:

await za.contributions.verify({
  person: "grimaldo.btc",
  opportunity: "bounty:123",
  evidence: "..."
});

Now developers don't need to build:

  • reputation systems
  • contributor profiles
  • bounty infrastructure
  • verification systems
  • reward tracking

from scratch.

The "MCP moment" for ZA

The really ambitious version is:

Any application can become a Zero Authority application by implementing the protocol.

A developer could build:

ZA Server

Expose:

people
opportunities
contributions
reputation
rewards

ZA Client

Consume those objects.

And eventually:

ZA Agent

An AI agent could discover opportunities and coordinate people.

For example:

USER
"Find me a designer for this Bitcoin campaign."

        ↓

ZA PROTOCOL

        ↓

DISCOVER PEOPLE

        ↓

CHECK REPUTATION

        ↓

CHECK AVAILABILITY

        ↓

MATCH

        ↓

SEND OPPORTUNITY

        ↓

CONTRIBUTION

        ↓

VERIFICATION

        ↓

BTC/STX PAYMENT

        ↓

REPUTATION UPDATED

That starts becoming an open coordination layer for the human + agent economy.

And this fits Zero Authority extremely well

Your existing product already has many of the pieces.

ZA currently positions itself around connecting contributors, opportunities, reputation, bounties, grants and governance. ([Zero Authority DAO]3)

And the current AI product already exposes APIs and bots for things like gigs, bounties and reputation. ([Zero Authority DAO]4)

So rather than inventing an entirely new product, I'd make the protocol the underlying layer that unifies what you're already building.

Existing ZA

Bounties
Gigs
Grants
Creators
Reputation
Governance
Bots
AI
Payments

ZA Protocol

IDENTITY
REPUTATION
OPPORTUNITY
CONTRIBUTION
VERIFICATION
REWARD

Applications

ZA
Discord
Telegram
GitHub
Wallets
AI Agents
DAOs
Communities
Other platforms

The strongest positioning

I would avoid calling it simply a "people API."

That's too small.

I'd position it as:

Zero Authority Protocol

The open protocol for human contribution.

Connect people, opportunities, reputation, contributions, and rewards across applications.

Or more aligned with your existing language:

The open coordination protocol for the human and agent economy.

And the simplest comparison:

MCP connects AI to applications. Zero Authority connects people to opportunities.

That is a very understandable narrative and gives ZA a potential path from being a destination application to becoming infrastructure that other applications build on.

The protocol should be open and permissionless, while ZA can monetize hosted infrastructure, discovery, verification, enterprise features, premium APIs, agent services, and transaction/coordination fees. That lets the protocol grow independently of the ZA frontend.