go-livepeer-basicnet icon indicating copy to clipboard operation
go-livepeer-basicnet copied to clipboard

Basic p2p video streaming for Livepeer

Results 12 go-livepeer-basicnet issues
Sort by recently updated
recently updated
newest added

Easier to distinguish and diagnose issues with rather than using the full hex-encoded address.

Currently we use a mix of encodings: JSON to wrap Golang gob-encoded messages. * The gob encoding is not portable. While theoretically documented in https://golang.org/pkg/encoding/gob/ , in practice gob encoding...

Would be good for broadcasters to get some feedback from the transcoder in case a segment couldn't be processed for whatever reason. We can implement a new message type for...

So I'm not sure how we're actually populating our peer tables and whether that actually follows Kademlia routing specifications. Depending on how we do this, routing loops seem like they...

Tracking issue for the proposal outlined in https://github.com/livepeer/go-livepeer-basicnet/issues/21#issuecomment-369310870 * [x] On-chain tracking of new jobs and assignments in transcoder. * [x] Transcoder prepares to receive a direct connection (set up...

## Super Rough Version **Message Types:** 1. Sub 2. Data (video segment) 3. Finish 4. Cancel 5. TranscodeResponse 6. GetMasterPlaylist 7. MasterPlaylistData 8. NodeStatusReq 9. NodeStatusData **Node Roles:** Broadcaster *...

## Rationale Handling failure cases in the current implementation is difficult (eg, transcoder address changes, broadcaster unavailability), and poses challenges for designing large-scale systems. Broadcasters are overly exposed to the...

A lot of our unit tests here are actually integration tests. This might be an incremental effort, but we should stub out the underlining, libp2p layer in the tests to...

For a Livepeer node, this corresponds to the JobID, from which the StreamID can be looked up easily on-chain. Other off-chain applications can use the bigint as a lookup key....