About Prometheus Protocol

Current Status

Prometheus Protocol is currently in the specification draft phase. There is a complete conceptual framework for three protocols (TCDP/DTOP/PCSP whitepapers), but no runnable reference implementation code, no real nodes connected, and no production tasks completed through the protocol. This website exists to publish the draft specifications, invite feedback, and iterate gradually.

Origin

Prometheus Protocol was inspired by a question: When production tools are smart enough, why do we still need corporations to organize production?

In Greek mythology, Prometheus stole fire from the gods and gave it to humanity. Today, smart manufacturing capabilities should not be locked behind factory walls or controlled by platform monopolies. They should spread freely like fire, reaching everyone willing to participate in production.

Prometheus Protocol is an open specification designed to enable smart tools to collaborate globally without central platforms or trust intermediaries.

Vision

We believe:

There is a long path between vision and reality. We know this, so we're putting the draft specifications out first, letting more people see, question, and improve them.

Founder

Prometheus Protocol is currently initiated and maintained by one person. The whitepaper writing, website setup, and specification iteration all come from the same individual. This is not an ecosystem project with multiple participants yet; it is an early-stage draft still looking for collaborators.

The "Orchestration Committee" and "rotating democratic governance" mentioned in the Design Philosophy page are governance mechanisms designed into the protocol—they are the target architecture for the future, not the current organizational reality. The current decision process is simple: you email suke@ezuhe.cn, and I respond.

As more participants join, governance will gradually transition from individual maintenance to community co-governance. But this transition only makes sense when actual second and third participants appear.

Social Reaction

Any protocol that changes the logic of production collaboration will trigger complex social reactions. We do not avoid these reactions — positive, negative, and observational all deserve serious examination.

Positive Reactions

  • Worker Empowerment: Freelance operators no longer depend on a single platform for tasks. They can bid cross-domain, choose autonomously, and accumulate credit reputation. Prometheus Protocol gives every capable person an equal opportunity to participate in production.
  • Small Manufacturer Inclusion: Small and medium factories are no longer excluded by large platforms' entry barriers. As long as capabilities are genuinely verifiable, any scale factory can participate. The protocol opens the door of equal competition for small but excellent producers.
  • Transparent Value Exchange: Every contribution is recorded, verified, and settled. No hidden operations, no intermediary interception. Producers know exactly how much value they created and how much return they received. Transparency itself is a correction for injustice.

Negative Reactions

  • Established Platform Resistance: Existing platforms will not voluntarily relinquish control over task allocation and value extraction. They may obstruct the protocol's promotion through technical blockade, legal action, or public opinion attacks. Such resistance is foreseeable and requires strategic community response.
  • Trust Building Challenges: The greatest challenge for decentralized systems is not technology but trust. People are accustomed to "platform guarantee" models. Convincing them that the protocol itself can guarantee fairness requires time and numerous successful demonstration cases.
  • Regulatory Uncertainty: Even with non-exchangeable credit points, regulatory agencies may still scrutinize the system. Different countries have different regulatory frameworks defining "credit systems" and "value records" — compliance pathways must be explored one by one.

Neutral Observations

  • Gradual Adoption Curve: The protocol will not overnight replace existing systems. Adoption will be gradual — starting from marginal scenarios and progressively expanding toward core production domains. Each stage's success paves the way for the next.
  • Regional Variation: Different regions have different industrial structures, trust cultures, and technological foundations. The protocol's adoption speed and form will vary by region. This is normal — the protocol's design itself supports regional adaptation.
  • Hybrid Transitional Models: Before full decentralization, hybrid models will emerge — some stages handled by the protocol, others still by existing platforms. Hybrid models are not compromise but pragmatic choices during transition.

We acknowledge the legitimacy of every reaction. Positive reactions motivate us, negative ones remind us to be cautious, neutral observations help us stay pragmatic. Prometheus Protocol's goal is not to win arguments but to let facts speak.

Community

Community Status

Prometheus Protocol's community is currently in its initial stage. There is no forum, no real-time chat channel, and no code repository to submit PRs to yet. The only communication channel right now is email. This isn't ideal, but honesty matters more than pretending. When enough participants exist, we'll build proper community infrastructure step by step.

Contact

The only contact method at this time:

Email: suke@ezuhe.cn

When writing, please mention your background (factory owner / operator / developer / researcher) and the direction you're interested in. I'll respond to each message individually.

What You Can Do Now

The protocol is still in the draft phase. The most valuable ways to participate currently:

  • Review the whitepapers: Point out designs you think are unreasonable, missing scenarios, or potential contradictions.
  • Provide industry perspective: If you work in manufacturing, logistics, or industrial automation, tell me whether the protocol design aligns with real-world needs.
  • Offer technical suggestions: If you have experience in distributed systems, consensus algorithms, or manufacturing interoperability, tell me which designs need a more rigorous technical foundation.
  • Share use cases: Tell me about your factory or workshop's equipment and needs, so I can understand the real scenarios the protocol must accommodate.

Future Community Plans

When participant numbers reach a meaningful baseline, we plan to build:

  • A public discussion forum (issue-driven, not idle chat)
  • A GitHub code repository (with Pull Requests and Issue tracker)
  • Regular specification review meetings (online, publicly recorded)
  • A testnet environment (a simulated network for verifying protocol logic)

These will only be launched when genuinely needed, not built on empty foundations.

Report Issues

If you find issues while reading the specifications (logical contradictions, technical gaps, unclear wording), please:

  • Identify the specific section and describe the problem
  • Suggest an alternative approach you think would work better
  • Send to suke@ezuhe.cn

Development Journal

Development milestones and progress records for Prometheus Protocol.

2026-07-15
Protocol v0.1 Draft Released
The v0.1 drafts of the three core sub-protocols (TCDP, DTOP, PCSP) were officially released. The drafts define the basic specifications for tool capability description, distributed task orchestration, and contribution proof settlement, laying the protocol foundation for a decentralized production network.
2026-07-22
First Beacon Node Deployed (Hong Kong)
The first Prometheus beacon node was successfully deployed and launched in Hong Kong. Serving as the starting point for the global discovery service, this node began accepting TCDP device declaration registrations and providing global device search capabilities. This is the first step in lighting the beacon.
2026-07-29
Reference Implementation Published
Reference implementation code covering the three core modules (tcdp-schema, dtop-engine, pcsp-validator) was officially released. The code is licensed under GNU AGPLv3 and includes a complete verification test suite. Community developers can now begin experimenting and contributing based on the reference implementation.
2026-08-01
Community Feedback Collection Started
Community feedback channels are now open, inviting all participants to share opinions and suggestions on protocol specifications, reference implementations, and usage experiences. Feedback is collected via email and organized into public issues driving continuous protocol improvement.

License

All specification documents and future reference implementation code for Prometheus Protocol are released under the GNU Affero General Public License v3 (AGPLv3). This license ensures:

We chose AGPLv3 because the protocol's goal is open production collaboration. AGPLv3 ensures this openness cannot be eroded by any participant through closed services.