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

Raiden DB doesn't takes into account contracts address, and gets messed up on new deploys #2356

Closed
andrevmatos opened this Issue Sep 5, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@andrevmatos
Collaborator

andrevmatos commented Sep 5, 2018

Problem Definition

After latest contracts deployment and merge of changes on master, nodes which didn't removedb get lost because it can't find onchain the channels it had registered, nor detect/react on new ones, as it doesn't know about the new contracts.

It's caused by the db name having only the chain_id and version on it. It should also include the token_network_registry address, to reset on new deployments.

System Description

Current master 7fff72a

@LefterisJP

This comment has been minimized.

Collaborator

LefterisJP commented Sep 5, 2018

Yep we noticed. @hackaugusto is fixing it right now

@andrevmatos

This comment has been minimized.

Collaborator

andrevmatos commented Sep 5, 2018

Fixed by #2359

@andrevmatos andrevmatos closed this Sep 5, 2018

@LefterisJP LefterisJP added this to the Red Eyes Testnet 8 milestone Sep 6, 2018

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