Thank you @Mehrdad and the Review Team for the approval. Confirming the two conditions before countersigning, with a short note on what shifted during the first week of building.
1. Milestones — confirmed (refreshed)
Confirmed, with dates re-based to the actual June 15 start: first deliverable June 24 (in review tomorrow), production + public beta July 1, wrapping July 17. Payout structure unchanged.
| # | Deliverable | Target |
|---|---|---|
| 1 | Auth webhook + runtime stack — /authorize webhook (builder-sdk, API-key verifier) + one-command compose stack (signer + Kafka + collector) |
Jun 24 |
| 2 | Bootstrap + OpenMeter billing adapter — Go sdk-konnect bootstrap → .env.livepeer; collector → OpenMeter with Wei→USD oracle; trial balance allowances via config |
Jun 26 |
| 3 | Administrative / Usage API + balance gate — usage query at platform/app/user level + the deny-at-zero gate | Jun 30 |
| 4 | Production + public beta + documentation — live July 1; draft docs July 1, final docs by July 8 | Jul 8 |
| 5 | Platform partnership + retrospective — partner integrations, forum retrospective with beta metrics | Jul 17 |
Milestone 1 & Milestone 2 are already in review; the project then runs to production (Jul 1) → final docs (Jul 8) → partner integrations + retrospective (Jul 17), giving the beta a couple of weeks for real adoption.
2. Documentation
Self-contained and publish-ready for docs.livepeer.org — drafted from Milestone 1 so it never gates the ship, ready for Adam by ~July 1 and finalized by ~July 8. Covers signer standalone usage, suite integration, an app-integrator decision guide, and the API reference.
3. Public beta operator
Understood this doesn’t need confirming now. The Livepeer Developer Dashboard is the leading candidate — already a consumer of the hosted clearinghouse — and I’ll confirm the named operator before the final milestone.
Scope refinements (first-week learnings)
A few things tightened up against the live KongHQ/OpenMeter API:
- Auth: API-key is the clearinghouse-core path; OIDC/Auth0 is validated in live pymthouse (dual-validation), keeping the example minimal-dependency.
- Single store: hosted OpenMeter (KongHQ Konnect) is the system of record — no database; self-hosted/SQL stays on the future roadmap.
- Bootstrap: moved to the Go
sdk-konnectCLI after the KongHQ acquisition broke the OSS NodeJS SDK’s forward-compatibility. - Security (new):
create_signed_ticketdoesn’t carrymodel_id, so usage can’t be bound to the model served — a misattribution vector. Addingmodel_id+ per-modelRemotePaymentStatesigning across go-livepeer (draft PR #3947) andlivepeer-python-gateway, with peer review. Additive hardening under Milestone 2.
Happy to move forward if it looks good on your side. I’ll review the planned milestone issues with @rickstaa again tomorrow to ensure we have full alignment. Thanks again, weekly updates continue.