Hosted transcoding in go-livepeer still assumes a local gateway wallet. The existing remote-signer path is only wired for the Live AI payment flow, while classic transcoding still uses local pm.Sender state, local PM sessions, and local ticket generation in the broadcaster path.
We need to decide between:
- Short-term: run dedicated hardened gateway nodes with a hot wallet as a temporary bridge.
- Medium-term: add a custody-backed AccountManager so gateways keep the existing transcoding flow but signing/tx custody moves off-box.
- Long-term: implement full remote-signer support for transcoding by moving PM session and ticket issuance out of the gateway path.
Hosted transcoding in go-livepeer still assumes a local gateway wallet. The existing remote-signer path is only wired for the Live AI payment flow, while classic transcoding still uses local pm.Sender state, local PM sessions, and local ticket generation in the broadcaster path.
We need to decide between: