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

ActionInitChain using wrong value #2784

Closed
hackaugusto opened this Issue Oct 15, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@hackaugusto
Collaborator

hackaugusto commented Oct 15, 2018

Problem

  • During start up we use the latest block number (as seen by the node's Ethereum node) to initialize the node's state here, this is dispatched and make recoverable by the WAL here
  • Then here Raiden polls all events from the smart contracts, updating the node's view of the blockchain
  • If during the poll the node is crashes, it will be left with a partial update
  • On restart, the node will use the latest block number set in the NodeState, here. Which is up to the latest block number
  • That block is then used here to poll the events from the blockchain

Fix

Instead of using the latest block number, ActionInitChain must use the block height at which the token network registry was deployed.

@palango

This comment has been minimized.

Collaborator

palango commented Oct 15, 2018

Fixed by #2787

@palango palango closed this Oct 15, 2018

@palango palango added this to the Red Eyes Testnet 14 milestone Oct 15, 2018

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