Karl Bartel

I'll monitor failures on the develop branch. If anyone sees flaky tests in other branches, let me know. Until proven otherwise, I'll assume the changes in https://github.com/raiden-network/raiden/pull/6313 and https://github.com/raiden-network/raiden/pull/6312 are...

The first step is to merge https://github.com/raiden-network/raiden/tree/arbitrum, before more differences accumulate. Since the branch is failing the tests, I won't get all tests to pass. But I can make a...

The name for the extracted code will be `raiden-common` to avoid confusion with the current `raiden` repository and the old `raiden-libs`. The integration tests will be removed because they cause...

The new package has been created at https://github.com/raiden-network/raiden-common and https://github.com/raiden-network/raiden-services/pull/1231 switches the services over to using it. I will create issues for further work on raiden-common in https://github.com/raiden-network/raiden-common/issues. Apart from...

All work on the code is done, the remaining items are better handled in separate issues.

> Are we being throttled by concurrency limits? (Conversation with Circle @karlb @czepluch) Yes, we are. I have been contacted by a CircleCI employee who would like to talk to...

We could also fetch the rate during the mediation. This would vastly reduce the number of calls and should be still acceptable from a latency perspective.

@dependabot rebase

Now that we have revert error messages, I would prefer to rely on the errors from the contract call in most cases rather then relying on correctly duplicating the logic.

Do we really need this?