livepeer / livepeer/livepeer-python-gateway
Remove deprecated BYOC module from the Python SDK (superseded by live runner)
@rickstaa ci sta già lavorando.
Dal 17/6/2026.
- Lingua principale
- Python
- Stelle
- 1
- Fork
- 7
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Context
byoc.py implements the legacy BYOC consumer flow (client-side sign + probabilistic micropayment for submit_byoc_job / submit_training_job) and is exported from the SDK via __init__.py. It was extended in #17 (merged), so it currently lives on main.
This consumer-side BYOC path is superseded by the live runner (#20, branch ja/live-runner), which becomes the supported way to get jobs onto the network. Shipping both leaves two overlapping job/payment paths on the public SDK surface.
Why
BYOC is deprecated and replaced by the live runner. Removing it collapses the SDK to a single job/payment path and drops the misleading public byoc API before v1.
Scope
- Delete
src/livepeer_gateway/byoc.py. - Remove the
byocimports and the matching__all__entries (submit_byoc_job,submit_training_job, and the other byoc exports) fromsrc/livepeer_gateway/__init__.py. - Delete
tests/test_byoc_refresh.pyandtests/test_byoc_training.py. - Keep
remote_signer.py: it is shared and still imported bylive_runner.py. Remove only BYOC-only paths if any remain after an audit. - Verify no remaining
byocimports acrosssrc/andexamples/.
Preconditions (do not start until all are true)
- Live runner (#20) released.
- storyboard migrated off BYOC onto the live runner: https://github.com/livepeer/storyboard
- naap migrated off BYOC onto the live runner: https://github.com/livepeer/naap
Notes
- #17 is already merged, so this is a removal of merged code, not a close-without-merge on the PR.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.