Specification & Implementation

Current Project Status

Prometheus Protocol is currently in the specification draft phase (v0.1 Draft). The content below describes the planned reference architecture; no runnable code exists yet. The three whitepapers define the conceptual framework and design intent of the protocol. The reference implementation aims to make these concepts verifiable, testable, and iterable. We chose to write specifications before code because a protocol's foundation is consensus, and consensus requires text first.

If you have thoughts on the protocol design, reach out at suke@ezuhe.cn.

Planned Repository Structure

The reference implementation will include the following modules (currently a design plan, not yet created):

prometheus-protocol/
├── tcdp-schema/          # TCDP semantic schema definitions & validator
│   ├── schemas/          # JSON Schema definition files
│   ├── validator.py      # Declaration validation engine
│   └── registry.py       # Device registry service
│   └── tests/
├── dtop-engine/          # DTOP task orchestration engine
│   ├── decomposer.py     # Task decomposer
│   ├── bidder.py         # Bid coordination
│   ├── composer.py       # Dynamic composition
│   ├── scheduler.py      # Decentralized scheduler
│   └── tests/
├── pcsp-validator/       # PCSP contribution proof validator
│   ├── proofgen.py       # Contribution proof generator
│   ├── verifier.py       # Multi-party verification engine
│   ├── settler.py        # Auto-settlement engine
│   ├── arbitrator.py     # Dispute arbitration module
│   └── tests/
├── beacon-node/          # Beacon node (lighthouse service)
│   ├── server.py         # HTTP/DHT server
│   ├── discovery.py      # Global discovery protocol
│   ├── monitor.py        # Node health monitor
│   └── tests/
├── docs/                 # Protocol docs & whitepapers
├── examples/             # Example configs & declarations
├── LICENSE               # GNU AGPLv3
└── README.md

Core Modules

tcdp-schema

TCDP's semantic schema definitions and validation tools. Will include complete JSON Schema definitions, a declaration validation engine, and a device registry service. Any device can use this module to publish TCDP-compliant declarations and register with the global discovery service. The TCDP whitepaper already defines the declaration fields and semantic schema design framework.

dtop-engine

DTOP's core task orchestration engine. Will implement the complete pipeline from task decomposition, bid coordination, to dynamic composition. Supports dependency-aware subtask decomposition, automatic bidding based on TCDP capability matching, and automatic re-orchestration upon node failure. The DTOP whitepaper already defines the decomposition strategy and bidding mechanism design framework.

pcsp-validator

PCSP's contribution proof verification and auto-settlement engine. Will implement physical work proof generation, multi-party independent verification, deposit locking and release, and dispute arbitration. All settlement operations will be entirely driven by protocol rules with no human intervention. The PCSP whitepaper already defines the proof types and verification process design framework.

TCDP Declaration Example

Below is a TCDP-compliant laser cutter declaration example, showing the planned declaration format:

{
  "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, "acrylic": 40 },
    "precision_mm": 0.05,
    "work_area_mm": [1500, 1000],
    "power_watts": 4000
  },
  "location": { "lat": 22.3, "lon": 114.2, "region": "HK" },
  "interfaces": {
    "api_endpoint": "https://tcdp.example.com/v0.1/tools/TCDP-HK-LC-001",
    "protocol_version": "0.1",
    "transport": "HTTPS+JSON"
  },
  "trust": {
    "certificate_issuer": "PrometheusCA-v0.1",
    "serial": "CERT-2026-001",
    "reputation_score": null,
    "fulfillment_history": []
  },
  "status": "offline",
  "updated": "2026-08-01T00:00:00Z"
}

Note: reputation_score and fulfillment_history are empty because this node has not yet participated in any production task. This is the initial state of a new node.

Development Roadmap

The reference implementation development will follow this priority order:

Phase 1: TCDP-schema module. Starting with declaration format and validation logic, this is the foundation of the entire protocol. If capability declarations cannot be trusted, subsequent orchestration and settlement cannot function.
Phase 2: Beacon-node service. Providing the most basic device discovery and registration functionality so nodes can find each other.
Phase 3: DTOP-engine module. With trusted nodes in place, implementing task decomposition and bidding.
Phase 4: PCSP-validator module. With orchestrable tasks, implementing contribution proofs and settlement.

Each phase will have independent verification test suites ensuring modules can run and verify independently.