Skip to content

Releases: livepeer/go-livepeer

v0.5.8

11 May 18:39
716119b
Compare
Choose a tag to compare

Summary

This release includes support for voting in governance polls. All orchestrators should upgrade to this version as soon as possible so they can use livepeer_cli to vote in the LIP-19 poll.

This release also includes a few minor new features and bug fixes - please refer to the "Features" and "Bug Fixes" sections for more details.

Thanks to everyone that submitted bug reports and assisted in testing!

Features

Broadcaster

  • Propagate the last error when the max number of transcode attempts is hit (#1475)
    • If the max number of transcode attempts is consistently hit, there is likely a problem with the segment

Orchestrator

  • Added support for voting in governance polls in livepeer_cli (#1461)
    • Check out the docs for more details on how to vote in polls

Bug Fixes

General

  • Embed mime types for some video formats because the mime types are not always loaded from the host machine (#1465)

Orchestrator

  • Fixed the GPU transcoding test on start up for Windows builds (#1471)
    • A Windows based orchestrator and/or transcoder does not need to be run with the -testTranscoder=false flag anymore

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): d7cc8df1549888562f89150c7a205efc
  • livepeer_cli (Linux): c7bea07ac4036a212add9ca4e1bb8daa
  • livepeer (Darwin): e641b8067b31ca0907a0812a36197308
  • livepeer_cli (Darwin): 2a5089a27a31ab57f5240210df012c30
  • livepeer.exe (Windows): 7d03a677d8c37d0385ad8c4de54d28eb
  • livepeer_cli.exe (Windows): b0d96268c4ace1d76684ec3710de93a8

Generate the md5 hash:

md5sum livepeer
md5sum livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): 15faebb5703dd31d2b6353427190db30560b373410ebda2bf5a8aac376a72356
  • livepeer_cli (Linux): 4d851104435811d1ded329035db55c42bb089875940024378a92302ce21dd9ff
  • livepeer (Darwin): 1dcca18eb3f5e7481f345ffa91ec5a2c023254d9ad6c6139a8fbb1b639a951fd
  • livepeer_cli (Darwin): 94738bdf8c4f716747127fa6ea08265480ad07f9f19e6b3c766c973694715cff
  • livepeer.exe (Windows): 98001a865f0d95e76596dbe033b70e68882e4ac28686ac0057fd470c54480370
  • livepeer_cli.exe (Windows): 0a57d96d65e68ea7675de46e9fb6d8f79bd0801283eb6bebaed1a287bf204b24

Generate the sha256 hash:

shasum -a 256 livepeer
shasum -a 256 livepeer_cli

v0.5.7

23 Apr 19:09
ac28889
Compare
Choose a tag to compare

Summary

This release fixes the broken v0.5.5 Windows binary and also includes a small update to the HTTP ingest response format for broadcasters.

If you do not run on Windows and if you do not run a broadcaster with HTTP ingest enabled, then you can safely ignore this release.

There is a known issue with the GPU transcoding test that the Windows binary runs on start up, but transcoding works after start up. This will be fixed in a future release, but for now a Windows based orchestrator and/or transcoder should be started with the -testTranscoder=false flag.

Features

Broadcaster

  • Return the file name in the Content-Type header of the response returned when using HTTP ingest (#1466)

Bug Fixes

General

  • Fixed the Windows build by adding a missing DLL (#1462)

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): fb89aa46ef360e61af83cbb2c2538e22
  • livepeer_cli (Linux): b9ddad630af6d1354a0d6d00a712e450
  • livepeer (Darwin): ff0b93544f761d15c7aef69e1462b8c9
  • livepeer_cli (Darwin): 9b654e81db5fb6ac02563a5ffb6d1796
  • livepeer.exe (Windows): 05607bc81ef925aa94acdfc5d8e8791a
  • livepeer_cli.exe (Windows): 461634e36c63cd865e8a8e9b82c82915

Generate the md5 hash:

md5sum livepeer
md5sum livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): 7074c26e1c754563201a24ff973a6782472061e2eb9e928b850ebe5e4c499367
  • livepeer_cli (Linux): 1f70c4870fff2a868e467ddeb0e7f71efafcb0df8e2d176882870e38e679b103
  • livepeer (Darwin): c7beaf8192a69c2f97f81365a03f7d9dd53cfebaff7a1dbd104ae745213ca9ff
  • livepeer_cli (Darwin): 5a30bb4e581d6d3992ab34e2e37d6e44fa6c4d58e978e0f8c2d7ddf84b08ec98
  • livepeer.exe (Windows): 446f7bce7eaff80b9ab7fd7ec878aec70dff1b46d0f8c452254b15f450a68292
  • livepeer_cli.exe (Windows): 276e014f80eb1c6526d02ef5dc52f3ad90dacc9ff028203ed6c7322864cb516f

Generate the sha256 hash:

shasum -a 256 livepeer
shasum -a 256 livepeer_cli

v0.5.6

21 Apr 12:42
a55045b
Compare
Choose a tag to compare

Summary

This release includes a critical fix for a bug that could cause orchestrators to advertise prices different from the prices that they expect payments to be based upon. All orchestrators should upgrade to this version as soon as possible to ensure that they can transcode streams reliably and be paid correctly.

This release also includes a breaking change that will require all node operators to start their nodes with a -ethUrl flag and the JSON-RPC URL of an Ethereum node. Please refer to the "Breaking Changes" section for more details and instructions for upgrading to this version smoothly.

Other notable updates in this release include a big boost in GPU transcoding performance, improved filtering of faulty orchestrators during discovery for broadcasters and support for transcoding MP4 inputs/outputs.

Thanks to everyone that submitted bug reports and assisted in testing!

Breaking Changes 🚨🚨

  • As of this release, a node started without the -ethUrl flag will no longer use a default Infura endpoint when connecting to Rinkeby (using the -network rinkeby flag) or mainnet (using the -network mainnet flag). When the node connects to Rinkeby or mainnet, the -ethUrl and the JSON-RPC URL of an Ethereum will be required. Refer to this guide for instructions on connecting to an Ethereum node.
    • The reasons for this breaking change are:
      • At the moment, there are no restrictions on usage for the default Livepeer Inc. sponsored Infura endpoints and as the number of requests increase the higher the subscription costs for maintaining these endpoints. Furthermore, there are request caps for each pricing tier, so high usage from any individual node operator can reduce the number of requests available to other node operators at a given tier. See this blog post and pricing guide for more details on how Infura pricing works
      • While there is a free tier for Infura, the cap for the number of requests for these endpoints is not very high so the per day request cap will be hit pretty quickly if all node operators are sharing the same endpoints. At this point, node operators would need to find alternate methods of connecting to an Ethereum node
    • There will be a one week grace period before the default Infura endpoints in the node will stop working so all node operators should upgrade to this version during this time and connect to an Ethereum node using the guide mentioned above

Features

General

  • Removed the default Infura endpoints for the -ethUrl flag (#1448)

Broadcaster

  • Added a per-stream orchestrator suspension list that is used during discovery to filter out orchestrators that have returned errors which should improve the broadcaster's ability to find reliable orchestrators (#1435)
  • Added support for transcoding MP4 inputs/outputs when using HTTP ingest (#1429)
    • Check out the docs for more details on how to transcode MP4 inputs/outputs
  • Added support for enabling and disabling HTTP ingest (#1446)
    • Check out the docs for more details on how to enable and disable HTTP ingest
  • Added additional logging when an error is encountered while submitting a segment to an orchestrator (i.e. if the broadcaster is missing a deposit or reserve) (#1430)

Orchestrator

  • Enabled filtergraph persistence in between segments during GPU transcoding. This update results in roughly a 30% performance gain when using a GPU to transcode a 1080p input into 720p, 576p, 480p and 360p outputs (#1444)
    • With this update, the transcode job serialization introduced in v0.5.5 is no longer needed (as it was a temporary solution for sub-optimal GPU transcoding performance) so that code has been removed

Bug Fixes

General

  • Fixed an invalid ticket creation round error caused by a broadcaster and orchestrator having different views of the latest Ethereum block. This issue is resolved by having broadcasters set the ticket creation based on the expected ticket creation round advertised by orchestrators (#1428)
  • Fixed a bug that caused livepeer_cli to crash when connecting to a node running in off-chain mode due to incorrect parsing of the chain ID used by the node (#1455)

Orchestrator

  • Fixed an overflow bug that could cause an orchestrator to advertise a price different from the price that it expects payments to be based on (#1450)
    • This resolves the invalid ticket recipientRand error that many orchestrators have been observing in their logs when transcoding streams
  • Fixed a potential race condition bug that could have caused an orchestrator to advertise a price different from the prices that it expects payments to be based on (#1453)
  • Fixed a nil pointer error triggered when an orchestrator receives a segment/payment from a broadcaster before an in-memory cache used for validation is populated with the latest Ethereum block (#1425)

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): ee078a01c762643ba9ab593a36166d44
  • livepeer_cli (Linux): 21f0296f689d3e5af5d986fcf4727b89
  • livepeer (Darwin): e44af1510588766031d938a51fd9a697
  • livepeer_cli (Darwin): 6bf5975781ccba3135877fdf4de30935
  • livepeer.exe (Windows): c316f91cc0cfc2d7f3b80c15f834e853
  • livepeer_cli.exe (Windows): d95bd8dddd328abdf4fc84e1696459d2

Generate the md5 hash:

md5sum livepeer
md5sum livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): 19db1c45ef4e1a6dbdf2cbb88b95faae456d96e838c0eb59425d084d26252eb7
  • livepeer_cli (Linux): c6fb76cd2d82cdb2241b1a7786f59edf810d4dcc07d1087f09963f4e91c2f80c
  • livepeer (Darwin): 3b3c1b8e24b4667086e7958084579e0de8084a09268d5080f1f99e0be6eb2c8b
  • livepeer_cli (Darwin): 25295d815736f1aecd385b7778e0e47432fcf4d707df2394eb087f368934d8bf
  • livepeer.exe (Windows): f6754a292f9a0165f2d1bdb189518f21e5f009d90518e225340d534d04722c3b
  • livepeer_cli.exe (Windows): e300fa37d981393e0bb2d1451381a21df745d6217f741a43e2b00b6c43950015

Generate the sha256 hash:

shasum -a 256 livepeer
shasum -a 256 livepeer_cli

v0.5.5

13 Mar 01:25
ce819a1
Compare
Choose a tag to compare

Summary

This release includes a number of improvements that improve transcoding reliability including the elimination of payment related errors triggered by dynamic price and/or ticket parameter adjustments mid-stream and a more efficient GPU transcoding work assignment algorithm that decreases transcoding time for multi-profile jobs.

Thanks to everyone that submitted bug reports and assisted in testing!

Features

General

  • Introduced expiring payment parameters to the payment protocol (#1383)
    • This allows an orchestrator to continue accepting payments for work even as it dynamically adjusts its price and/or ticket parameters in response to changing gas prices on the ETH blockchain
    • This removes the notion of acceptable vs. unacceptable payment errors (which was a source of confusion)
  • Added orchestrator prices to the CLI (#1394)
  • Added transaction parameters when logging submitted/failed transactions (#1250)
  • Added a /getLogLevel endpoint that can be used to set/get the current log level (affects the logs displayed to the user) used by the node (#1356)
    • See the docs for usage information.
  • Updated metrics logging (enabled if the -monitor flag is used) to only be displayed when the value of the -v flag is >= 6 (#1357)
  • Updated segment related log messages to consistently include the manifestID (#1363)

Broadcaster

  • Updated the latency score calculation in selection to be based on round trip time instead of transcode time (#1404)
    • This change should allow the broadcaster to select orchestrators based not only on how fast they transcode, but also how fast they download and upload segments
  • Updated the discovery process to shuffle the list of orchestrators prior to sending out requests to randomize the request order when using a fixed list of orchestrators (#1400)
  • Added segment upload and download time to logs (#1339)
  • Added the duration of broadcast session refreshes (executed when the broadcaster needs to find more orchestrators to send segments to) to logs (#1402)
  • Added the duration of auth webhook requests to metrics reporting (#1402)
  • Added the user agent, remote URL and body length to logs when using HTTP push (#1406 #1411)

Orchestrator

  • Added transcode job serialization when using a GPU which improves transcode time by anywhere between 20-60% depending on the hardware and configuration used (#1364)
  • Added a cap on the number of transcoding attempts for a segment which allows a broadcaster to skip a segment if the time window for he segment to be transcoded has already passed (#1392)
    • The -maxAttempts flag can be used to set the maximum number of transcoding attempts (the default value is 3)
  • Updated ticket processing to exit early if the rest of the tickets in a multi-ticket payment would be invalid (#1413)

Bug Fixes

Broadcaster

  • Fixed a bug where orchestrator signatures over segment data were not being verified when a broadcaster uses an external object store (#1393)
  • Fixed a bug where an RTMP stream object was not being closed properly at the end of a stream (#1351)
  • Fixed a bug in the transcoding verification policy (experimental) to ensure that results with incorrect audio are not inserted into a playlist (#1384)

Orchestrator

  • Fixed a bug related to a statically linked GMP library that was causing crashes during GPU transcoding on certain processor types (#1391)

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): 7ee126424d559925e0864433abe34cae
  • livepeer_cli (Linux): b108edb62364380e72cbd8e43cdd134b
  • livepeer (Darwin): fec6e8b1aaaf07588e10a27063000fcd
  • livepeer_cli (Darwin): 118520601994acce9628bca8df50edf0
  • livepeer.exe (Windows): be1cc61e6ee44086874168f64ecd9974
  • livepeer_cli.exe (Windows): 294b75cd2fb486d8b548b5284702ced5

Generate the md5 hash:

md5sum livepeer
md5sum livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): ef593400e3eecd449a323a0a498b4254fea32171c36b05a79e15f13e9b97f47f
  • livepeer_cli (Linux): cbc64cb0e5192ae3f48f483570982ebff37a83802042d5ac62daaec7a58f2f51
  • livepeer (Darwin): 341cf6d4c84c45dfe82b519b846ab67eba245637a3e4ee74d52d27fe19afe66d
  • livepeer_cli (Darwin): f5d620342ac6da674bae6f04b5965773ccafbb178cb8cc2b010a8966d6c72aef
  • livepeer.exe (Windows): 351ad49cde877a75418d1d4e4f71e45adff826969861ce3046cffdcdd609ec64
  • livepeer_cli.exe (Windows): 61f4e0caf3190cc6bf74ae5a4fc829a650091fc262edf3141323c82e8165ee3c

Generate the sha256 hash:

shasum -a 256 livepeer
shasum -a 256 livepeer_cli

v0.5.4

05 Feb 23:39
eadd64c
Compare
Choose a tag to compare

Summary

This is the second mainnet compatible release after the Streamflow protocol upgrade. In addition to some small bug fixes and enhancements, this release also includes a few notable new features including broadcaster support for multipart/mixed return when using HTTP ingest and message signing in the CLI wizard which enables 3Box profile linking in the explorer. There is also a Windows build! Thanks to everyone that submitted bug reports and assisted in testing!

The features and bug fixes sections below are now divided into sub-sections with information specific to broadcasters, orchestrators or all users.

Features

General

  • Added support for message signing in the CLI wizard using a /signMessage endpoint on the node's webserver (#1063)
  • Updated the CLI wizard to consistently display units (i.e. LPT/ETH) for token values (#1305)
  • Reduced logging level and language of block watcher logs for recoverable errors (#1320)
  • Re-enabled Windows builds that can also be used with GPUs (#1227)
  • Add support for passing in the HIGHEST_CHAIN_TAG environment variable when building a local Docker image (using make localdocker) in order to build the image with support for a particular network i.e. Rinkeby, mainnet (#1340)

Broadcaster

  • Added support for returning transcoded segments in a multipart/mixed response when using HTTP ingest (#1280)
    • Check out the docs for information on how to use this feature
  • Alert the user that a broadcaster's stream will not be transcoded due to the broadcaster being close to its withdraw round (when the user will be able to withdraw funds) by closing the RTMP stream (#1318 #1212)
  • Added a log statement with payment information when payments are created (#1331)
    • The log statement is only visible when the value of the -v flag is >= 5
  • Added a log statement with error information when an orchestrator found during discovery is excluded from selection (#1335)
    • The log statement is only visible when the value of the -v flag is >= 5

Orchestrator

  • Added an active status check when the orchestrator receives a payment to make sure that the orchestrator only accepts payments when it is active since only active orchestrators can redeem payments on-chain (#1291)
  • Enabled 3Box profile linking via message signing in the CLI wizard (#1063)
    • See this forum post for more information on how to link a 3Box profile to your account

Bug Fixes

Broadcaster

  • Fixed a bug where temporary files created for pixel count verification of transcoded segments were not being closed causing the node to eventually crash with a "too many open files" error (#1312)
  • Changed the orchestrator discovery timeout to 3 seconds from 1 hour which was too long (#1319)
  • Fixed a bug where the broadcaster would crash with a nil pointer error during selection when the broadcaster starts up for the first time in on-chain mode and specifies an orchestrator using the -orchAddr flag (#1330)
  • Fixed a bug where the broadcaster would crash with an index out of range error during selection when an orchestrator that is missing stake (could be specified via -orchAddr) is removed (#1330)

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): 51a75d6e06b4dd57278d9a601f97443e
  • livepeer_cli (Linux): 108a6873ff81b24af67fc76e1064dd36
  • livepeer (Darwin): 1ab18bf441b9c1ba7bc220bfd8611628
  • livepeer_cli (Darwin): 11dc802d81e6e4a7c6478592c0e8a528
  • livepeer.exe (Windows): 31f6156648afd318436b749668d44cfb
  • livepeer_cli.exe (Windows): 54b0a17764e993918f4a5f1d2d56ac5b

Generate the md5 hash:

md5sum livepeer
md5sum livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): a669d75ad1bfb1a992eaac40a1b4f519c592b178feedfc1f48f057d03e152937
  • livepeer_cli (Linux): d8aaa47a2a7855d2c273de2ee0b7fc3793382863e1b638ee5681249b60281253
  • livepeer (Darwin): 75353fb31479dd56f58d89166e2e4381f7909e439c09a495c0129975b56a2dab
  • livepeer_cli (Darwin): 480fdacdfa77edf0a67783c57786eb3bdcbff166c79feaab975272dfc9e635cf
  • livepeer.exe (Windows): 82aa9ffd2d07654f9f397086a0d8a352e0da0f593341deb269c048f9635fd837
  • livepeer_cli.exe (Windows): c047a3c2a0e9ac78be246916ba672874ab210ed8f70d55bea4a13d0411649902

Generate the sha256 hash:

shasum -a 256 livepeer
shasum -a 256 livepeer_cli

v0.5.3

13 Jan 23:57
Compare
Choose a tag to compare

Summary

This is the first mainnet compatible release that supports the Streamflow protocol upgrade.

Existing transcoders (now called orchestrators post-Streamflow upgrade) should check out the upgrade guide for instructions on re-joining the active set.

For more information on the Streamflow protocol upgrade, check out the following resources:

Features

  • Changed the default DB file name from lp.sqlite3 to lpdb.sqlite (#1299)
    • As a result of this update, if you are upgrading from a previous go-livepeer release you do not need to delete your existing DB file prior to upgrading

Full list of changes

Verifying Release

md5 hashes for release binaries:

  • livepeer (Linux): bf4ee3a984023dad2b75b4902b90e3be
  • livepeer_cli (Linux): d3b3549d91bf0591d25d8a83f568d242
  • livepeer (Darwin): f210f44b252e46d6bd623ea0a2784bff
  • livepeer_cli (Darwin): 261519967fc89bbcfe7cbc05095a5111

Generate the md5 hash on Linux:

md5sum livepeer
md5sum livepeer_cli

Generate the md5 hash on OSX:

md5 livepeer
md5 livepeer_cli

sha256 hashes for release binaries:

  • livepeer (Linux): a843648c0153cd7b03b68363e43214d8eee9c2f7f7e320f88bb198cb38e62ce5
  • livepeer_cli (Linux): 0beecc3ed126fca8f877886a6aaf7eab3ea35c382a0ee641a418857034aa2bd7
  • livepeer (Darwin): b03111b64e56e7027b3bec388d1ffe2a79142414080d15cab7c57125a669119f
  • livepeer_cli (Darwin): 6e67a0e6ff04e7aa3e3fd256579ee22aa0ec4df3e305bc83101e1e2c99c7f40a

Generate the sha256 hash on Linux and OSX:

sha256 livepeer
sha256 livepeer_cli

v0.5.2

11 Jan 01:04
Compare
Choose a tag to compare
v0.5.2 Pre-release
Pre-release

Summary

This is the last Rinkeby only go-livepeer release before the Streamflow upgrade on mainnet. The next release will be mainnet compatible.

Existing transcoders should check out the upgrade guide to make sure that they are prepared to run mainnet compatible nodes.

Breaking Changes

If you are upgrading from a previous release, you will need to delete your DB file prior to upgrading. The DB file can be found at <DATA_DIR>/<NETWORK_NAME>/lp.sqlite3. By default the DB file is located at ~/.lpData/rinkeby/lp.sqlite3.

  • The stake column has been added to the orchestrators table in the DB (#1216)

Features

  • Added support for caching the stake of active orchestrators when running as a broadcaster (#1216)
  • Added error logging when a user requests LPT from the Rinkeby faucet more than once in an hour (#1251)
  • Updated the /setOrchestratorConfig endpoint to not update the on-chain reward cut and fee share if the values would be unchanged (#1230)
  • Updated transaction signing to use EIP-155 by default (#1266)
  • Updated the CLI wizard to always print the list of preset video profiles in the same order (#1267)
  • Added support for passing in the password for an ETH account via text file (#1268)
  • Added support for passing in an orchestrator's shared secret (used by transcoders for authentication) via text file (#1275)
  • Enable custom video profiles for broadcasters (#1242)
  • Updated the CLI wizard to properly format LPT/ETH balances (#1285)
  • Added support for stake/latency based orchestrator selection for broadcasters (#1241)
  • Added support for experimental transcoding verification for broadcasters (#1096)
    • If you're interesting in trying out this experimental feature, check out the docs
  • Added support for load balanced transcoding across multiple GPUs enabled by session based transcoding in LPMS (#1124)

Bug Fixes

  • Fixed a bug where the Docker image was not built with the correct Rinkeby compatibility build tag (#1248)
  • Fixed a bug where Linux binary was not built with the correct Rinkeby compatibility build tag (#1260)
  • Fixed a bug where floating point conversion from ETH to wei would lead to rounding errors in the values included in transactions (#1243)
  • Fixed a bug where the node would crash due to a concurrent map write (#1288)

Full list of changes

v0.5.1

03 Dec 16:40
Compare
Choose a tag to compare
v0.5.1 Pre-release
Pre-release

Summary

Breaking Changes

If you are upgrading from a release < 0.5.1, you will need to delete your DB file prior to upgrading. The DB file can be found at <DATA_DIR>/<NETWORK_NAME>/lp.sqlite3. By default the DB file is located at ~/.lpData/rinkeby/lp.sqlite3.

  • The following activationRound and deactivationRound columns have been added to the orchestrators table in the DB. (#1171)

Features

  • Added support for active orchestrator set tracking by watching for events emitted by the BondingManager contract (#1157 #1180 #1173 #1171 #1182)
  • Added support for monitoring on-chain service URI updates by watching for events emitted by the ServiceRegistry contract (#1181)
  • Added support for broadcaster encoding fee estimation. The broadcaster will now estimate the encoding fee for a segment and use the estimate to determine the number of tickets to send as payment. (#1199)
  • Included actual values when logging max faceValue and max EV related errors (#1201)

Bug Fixes

  • Fixed a bug where the price per pixel in the CLI wizard was displayed as X pixels / Y wei instead of X wei / Y pixels. (#1169)
  • Fixed two flaky unit tests in the pm and eth packages that caused CI to fail sometimes. (#1189)
  • Compare the max faceValue for a broadcaster against the faceValue of a single ticket instead of the sum of the faceValues of all tickets in a batch. (#1201)
  • Orchestrators will now check if a broadcaster is close to the end of its unlock period and if so will stop working with the broadcaster. (#1210)

Full list of changes

v0.5.0

29 Oct 00:58
Compare
Choose a tag to compare
v0.5.0 Pre-release
Pre-release

This is the first go-livepeer release that is compatible with the Streamflow public testnet. This release supports the following features:

  • Scaling an orchestrator by running multiple attached transcoders
  • Basic off-chain orchestrator selection with price filtering
  • Working with multiple orchestrators to transcode a stream
  • Paying for transcoding using off-chain probabilistic micropayments
  • Pricing transcoding based on the number of pixels processed

This is just the first of many releases to come in the near future that will not only improve the node's stability and reliability on the public testnet, but also introduce additional important features. Follow along in the issues.

Infura Endpoint Update

26 Mar 23:22
Compare
Choose a tag to compare

Please ignore this release if you are running your own Ethereum node.

Infura is sunsetting its old endpoint versions. This release updates the Infura provider endpoints to v3.