Releases: raiden-network/raiden-services
Releases · raiden-network/raiden-services
v0.6.0
- PFS: Fix DB schema to not override channels (#693)
- PFS: Fix deletion of channels (#695)
- PFS: Add UDC info to
/info
endpoint (#689) - PFS: Forbid concurrent database usage (#681)
- PFS: Provide specific error message for common errors (#674)
- PFS: Wait for first matrix sync before starting PFS API (#659)
- PFS: Rework path validity checking (#666)
- PFS: Improve handling of
PFSFeeUpdate
messages (#661) - MS/PFS: Add profiling options to services (#653)
- MS/PFS: Don't replace gevent's error handler (#652)
v0.5.0
- Properly handle 'ValueError: x_list must be in strictly ascending order!' (#636)
- Don't force presence update when receiving capacity update (#647)
- Allow passing Matrix servers as CLI arguments (#633)
- Properly validate integer fields in API (#620)
- Properly validate
DateTime
s in messages and API (#619) - Fix unhandled exception when receiving unexpected IOU (#624)
- Increase precision in fee calculation (#611)
- Add JSON logging mode (#599)
- Wait for Matrix to start properly (#595)
- Show contracts version in info endpoint (#590)
- Add capped mediation fees (#574)
- Use production Matrix servers on mainnet (#575)
v0.4.1
v0.4.0
v0.3.0
- Wait for confirmation of transactions in monitoring service (#503)
- Take unconfirmed state into account if necessary, e.g. user deposit check (#502)
- Remove handling of ChannelNewDeposit event (#496)
- Bugfix: Fix possible crash when receiving unexpected message types (#499)
- Bugfix: Fix crash related to handling of settled channels (#512)
- Bugfix: Ignore MonitorRequests after channel closing (#510)
v0.2.0
- Update to raiden 0.100.5.dev0
- Add CLI options for PFS info settings (#479)
- Provide script to register services in ServiceRegistry (#447)
- Allow error reporting to Sentry (#406)
- Bugfix: Request collector crashes on unsigned RequestMonitoring Messages (#420)
- Bugfix: Request collector stores arbitrary Monitoring Requests (#419)
- Bugfix: Monitoring Service database vulnerable to timing based Monitoring Request injection (#418)