Releases: raiden-network/raiden
v0.200.0-rc6 - Starcraft
New release with minor bugfixes and UI improvements.
v0.200.0-rc5 - Pannekoken
This is a testnet release. Running this version on mainnet is not recommended.
v0.200.0-rc4 - Hefe
This is a testnet release. Running this version on mainnet is not recommended.
v0.200.0-rc3 - Goat for Azazel
This is a testnet release. Running this version on mainnet is not recommended.
This is a release candidate. It includes some bug fixes and multiple performance improvements and fixes to the transport layer, how events are fetched from the blockchain, and handling of transactions. Tested for over a thousand hours of automatic runs, but on the other hand, we want to revolutionize the payment sector … So the highest security and stability standards apply.
v0.200.0-rc2 - Narcoleptic Neo
Description
This is a testnet release. Running this version on mainnet is not recommended.
This is the second release candidate towards a mainnet-stable Alderaan. A lot of bugs found during testing were fixed especially on the mediation fees component and the the transport layer.
New Features
- #5050 Raiden's argument
--debug-logfile-namehas been renamed to--debug-logfile-pathto better reflect the argument's function. - #5278 Always use private rooms in the matrix transport.
- #5217 Fully support infura as an underlying ethereum rpc node.
- #5053 Make mediation fees non-negative by default. This fixes some counter-intuitive behaviour.
- Update WebUI to version 0.10.1 https://github.com/raiden-network/webui/releases/tag/v0.10.1
Bugs
- #5050 Raiden now works on OSX Catalina. Debug logfile is no longer written in the current directory.
- #5064 Display a user-friendly error message when the PFS info request fails.
- #5055 Fix withdraw messages deserialization when the messages are queued in
queueids_to_queues. - #4835 Fix etherscan sync by passing user-agent in the HTTP request. The request was failing because etherscan is protected by Cloudflare.
v0.200.0-rc1 - Aloof Alpaca
Description
This is a testnet release. Running this version on mainnet is not recommended.
This is the first release candidates towards a mainnet-stable Alderaan. A lot of work has gone into adding new features: mainly mediation fees, integration with path-finding and monitoring services and channel withdraw among many bug fixes.
New Features
- #4905 Added API parameter to the PATCH channel endpoint to update channel's reveal timeout.
- #4976 Geth users no longer need to activate the special txpool RPC api when starting their geth node.
- #4917 Added documentation on using Raiden for atomic swaps.
- #4860 Update per-channel proportional fee calculation
- #4858 Add check for bound in med fee calculation
- #4844 Formalize fee calculation
- #4815 Exclude direct transfers from fees
- #4751 Add Fees to internal Routing
- #4731 Setting fee defaults for Alderaan
- #4654 Define imbalance fees relative to channel balance.
- #4697 lock_timeout can be provided when making a payment.
- #4653 Allow setting per token network flat mediation fee from CLI.
- #4102 Display progress during syncing the blockchain.
- The lowest supported geth version is now 1.8.21.
- Update WebUI to version 0.10.0 https://github.com/raiden-network/webui/releases/tag/v0.10.0
- Added a new api endpoint
/api/v1/versionto query the raiden version via the Rest API.
Bugs
- #4835 Catch undefined med fee inside the state machine
- #4762 Properly check the withdraw expiration on the TokenNetworkProxy. This gives a better error message to the users and prevents a corner case error.
- #4685 Invalidate a withdraw transaction on restart if the channel is closed.
- #4560 Formatting of timestamp fields on the API should follow ISO8601.
- #4561 Limit and offset should now work properly in the payment API event queries.
- #4446 Fix assertion error in 'calculate_imbalance_fees'
v0.100.5a0 - Antifragile Crocodile
Description
This is a testnet release. Running this version on mainnet is not recommended.
v0.100.5a0 is a testnet release mostly fixing bugs since our last release.
From this release and on we are switching to a new scheme for testnet releases of an upcoming mainnet release. The suffix aN will be given where N is a number indicating the testnet release iteration.
New Features
- Update WebUI to version 0.9.2
Bug fixes
v0.100.5-dev0 - GANDALF2000
Description
This is a testnet release. Running this version on mainnet is not recommended.
v0.100.5.dev0 is a testnet release mostly fixing bugs since our last release.
New Features
- #4457 Raiden now checks the version of the ethereum node at startup and if it is not supported quits with an appropriate message.
- Update WebUI to version 0.9.1
Bug fixes
- #4446 Fix problems with the calculation of mediation fees
- #4383 Fix locked transfer not being sent due to global queue handling.
- #4484 Fix json decoding error that could lead to a crash.
- #4373 Fix a deserialization error for imbalance penalty
- #4377 The client now sends proper capacity updates to the PFS.
- #4301 Providing an endpoint argument without a port no longer leads to a crash.
v0.100.4 - thehighfiveghost
Description
v0.100.4 is our latest release which includes a collection of new features including channel withdraw and improved PFS integration as well as bug fixes which improve Raiden's handling of pruned blocks while interacting with the blockchain clients. A detailed list of all features and bug fixes is presented below.
This is a testnet release. Running this version on mainnet is not recommended.
New Features
- #4095 Prevent Raiden from sending IOU to PFS when fee is 0
- #4088 Check PFS info about registry address, prevent use of a PFS that doesn't support the current network.
- #4062 Use PFS requested fee instead of client max fee
- #3894 Drop support for UDP transport
- #3863 Implement permissive source routing
- #3754 Publish mediation fee infos to PFS
- #3303 Use direct channels for payments when possible, without asking PFS
- #1498 Implement on-chain channel withdraw
Bug fixes
v0.100.3 - Rosemary
Description
Raiden v0.100.3 is a mostly bug-fixing release containing a considerable number of bug fixes since the 0.100.2 (Pluto) release. In addition, this release contains improvements on the integration with Raiden services and third party services.
Installation
Instructions on how to install and fire up a Raiden client.
Features
- #4043 Update raiden-contracts to 0.19.0 with Görli Testnet support
- #3697 Make sure a token implements the ERC20 interface when registering a new token network. In this case, totalSupply function existence is implemented
- #3467 Raiden now chooses a PFS from a provided registry. Also added a new argument
--routing-modeto configure the routing mode to either be PFS or BASIC. - #3464 Raiden will warn users about insufficient user deposit funds (If monitoring service or path-finding service are enabled and used).
- #3462 Static Monitoring service reward through user deposits contract. Only usable if Raiden is run in development environment
- #3461 Static PFS payment for provided routes through the user deposits contract. Only usable if Raiden is run in development environment
- #3425 Update raiden-contracts package to version 0.9.0
- #3318 allow secret and/or hash with payment request
- #2436 Add an API endpoint to list pending transfers
Bug Fixes
- #4024 Fix clearing a channel state iff all unlocks are done by channel participants
- #3874 Fix invalidation of a batch-unlock transaction in case a similar transaction was already sent/mined by channel partner
- #3856 Handle pruned blocks during settle/unlock when requesting on-chain state, use latest if block is pruned
- #3832 Fix Raiden startup when a previous run aborted during migrations
- #3687 Fix startup initialization issue which caused Raiden to crash on private chains
- #3567 Resolve an issue in route filtering where the partner's network state is taken into account when choosing a route
- #3566 Handle cases where Raiden tries to query blocks which are old and pruned by the blockchain client (Geth & Parity)
- #3558 Raiden will no longer crash if starting with a fresh DB due to the ethereum node queries timing out.
- #3567 Properly check handling offline partners
- #3475 Properly check async_result in rest api payments