Getting Started

Step 1: Understand the Three Protocols

Prometheus Protocol consists of three interconnected sub-protocols:

• TCDP (Tool Capability Description Protocol) — lets devices declare "what I can do." Read the TCDP Whitepaper.
• DTOP (Distributed Task Orchestration Protocol) — lets tasks find the most suitable devices. Read the DTOP Whitepaper.
• PCSP (Proof-of-Contribution & Settlement Protocol) — ensures contributions are fairly measured and settled. Read the PCSP Whitepaper.

Together they form a complete loop: declare capabilities → match tasks → prove contributions → receive settlement.

Step 2: Understand the Design Intent

Each sub-protocol solves one core problem:

• TCDP solves "trust": how do we know a device really has the capabilities it claims?
• DTOP solves "coordination": how does a complex production task get decomposed, assigned, and composed?
• PCSP solves "fairness": how is each participant's contribution measured and settled?

We recommend starting with Design Philosophy to understand the principles behind the protocol, then diving into the technical details in the whitepapers.

Step 3: Understand the Declaration Format

TCDP declarations are expressed in JSON. Below is a laser cutter declaration example (specification draft phase; format may change):

{
  "tool_id": "TCDP-HK-LC-001",
  "name": "Laser Cutter Alpha",
  "type": "laser_cutter",
  "capabilities": {
    "material": ["steel", "aluminum", "acrylic"],
    "max_thickness_mm": { "steel": 20, "aluminum": 30 },
    "precision_mm": 0.05,
    "work_area_mm": [1500, 1000]
  },
  "location": { "lat": 22.3, "lon": 114.2 },
  "trust": { "certificate_issuer": "PrometheusCA-v0.1",
             "reputation_score": null }
}

See the full declaration example on the Specification & Implementation page. The complete JSON Schema definition is still being designed.

Step 4: Understand the Intended Production Flow

A complete production task will go through these stages:

• The requestor publishes a task (with specs, quality requirements, timeline, budget)
• DTOP decomposes the task into independently executable subtasks
• Subtasks are broadcast globally; verified nodes submit bid proposals
• DTOP composes winning nodes into a production line (dynamic composition; auto-replacement on node failure)
• Nodes execute in dependency order, producing intermediate or final products
• PCSP verifies each stage's contribution for authenticity and spec compliance
• Verified contributions automatically convert to credit points, completing settlement

See the detailed flow diagram on the Flow page.

Step 5: Think About Your Participation

The protocol is still in draft phase, but you can start thinking about future participation:

• If you're a factory owner: what are your equipment capabilities? How would you describe them in TCDP format?
• If you're a freelance operator: what professional skills would you declare? What kinds of bids would you participate in?
• If you're a protocol developer: what do you think of the whitepaper designs? What needs to be added or corrected?

The most effective way to participate right now is to read the specifications and give feedback. Send your thoughts to suke@ezuhe.cn.