---
title: "Coordinated phase-2 ceremony platforms"
description: "Coordinated phase-2 ceremony platforms: Coordinated ceremony platform. Coordinator-run platforms that automate queueing, timeouts, per-contribution…"
type: "option"
url: "https://zkpick.com/ceremony/phase-2-platforms/"
section: "04 Running or reusing a trusted setup"
authors:
  - "MarketComp"
publisher: "MarketComp"
version: "1.3"
updated: "2026-09-12"
license: "CC-BY-4.0"
json: "https://zkpick.com/data/ceremony/phase-2-platforms.json"
---

*By MarketComp. Updated 2026-09-12. Version 1.3. CC BY 4.0.*

# Coordinated phase-2 ceremony platforms — *Coordinated ceremony platform*

> Coordinated phase-2 ceremony platforms: Coordinated ceremony platform. Coordinator-run platforms that automate queueing, timeouts, per-contribution verification and attestation publication across multiple circuits at once, with browser and CLI contribution. Maturity: Production-used, maintenance mode. Maintained by: Ethereum Foundation Privacy & Scaling Explorations (p0tion, DefinitelySetup); maintenance mode. Choose it when: Teams needing an open, browser-accessible phase-2 ceremony with many contributors, who do not want to build queueing and attestation plumbing themselves.

Coordinator-run platforms that automate queueing, timeouts, per-contribution verification and attestation publication across multiple circuits at once, with browser and CLI contribution. **The leading open platform states it is no longer actively developed**, which is the most decision-relevant fact here: adopting it means owning it. Third-party coordination does buy something real — it constrains the project's ability to manipulate the ceremony *software* — but not its control of the circuit, the phase-1 artefact chosen, or the deployed verifying key.

**Strengths**

- Removes most of the coordination work, which is where ceremonies usually fail
- Real production track record across multiple independent projects
- Per-contribution verification and timeouts are enforced by the platform, so a stalled or malformed contribution cannot silently block or weaken the chain
- Attestations published automatically rather than collected by hand

**Tradeoffs**

- The leading open platform is explicitly in maintenance mode — plan for self-hosting and self-maintenance
- Requires billed cloud infrastructure, so the coordinator carries real cost and operational obligations
- Cloud-hosted coordination concentrates liveness and censorship risk in one operator
- Phase 2 only; not a phase-1 solution

**Choose it when:** Teams needing an open, browser-accessible phase-2 ceremony with many contributors, who do not want to build queueing and attestation plumbing themselves.

Maintained by: Ethereum Foundation Privacy & Scaling Explorations (p0tion, DefinitelySetup); maintenance mode · Maturity: Production-used, maintenance mode · License: MIT · Source: https://github.com/privacy-ethereum/p0tion