Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channel won't close (transaction failed) #1138

rethore opened this issue Nov 20, 2017 · 2 comments

Channel won't close (transaction failed) #1138

rethore opened this issue Nov 20, 2017 · 2 comments


Copy link

rethore commented Nov 20, 2017

Problem Definition

I've tried to reproduce the API calls described in readthedocs. While most of them worked, I couldn't close a channel (and therefore also settle it afterwards).

When I made the following API request [1]

PATCH /api/1/channels/<CHANNEL ID>, with payload {"state":"closed"}

I received:

 "partner_address": "0x0075703bf50aebe6755844c0c9b28cdb8f730933",
 "balance": 1050,
 "reveal_timeout": 10,
 "settle_timeout": 100,
 "state": "opened",
 "channel_address": "0xcf312d3743e09ccb7630c185b80d65747479bb6a",
 "token_address": "0x706ffe280b3ab30719212a8b6f4a1b2ac00f0862"

Which indicates that the channel state is still open.

Furthermore, I checked the transaction initiated in the parity node on etherscan [2]. The transaction status is TxReceipt Status:Failed

[1] API requests:
In [142]: patch(raiden1 + '/api/1/channels/' + BET_chn, json={"state":"closed"})

[2] Failed transaction:

System Description

System: Docker compose [3,4,5], inspired from raiden/docker/Dockerfile
Raiden version: commit version: 6be7cc1
Parity version: stable-release

[3] Docker compose used to start the two Raiden nodes:

[4] Dockerfile for raiden nodes

[5] Raiden settings file:

Copy link

Same as #1090 and #1109 .

This should be fixed by #1141 , if the bug persists please open a new issue.

Copy link

rethore commented Nov 27, 2017

I can confirm that #1141 fixed this bug. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants