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

Jump to bottom

removed expired lock must validate the expiration #2720

Closed
hackaugusto opened this issue Oct 8, 2018 · 0 comments · Fixed by #2721
Closed

removed expired lock must validate the expiration #2720

hackaugusto opened this issue Oct 8, 2018 · 0 comments · Fixed by #2721
Assignees
@hackaugusto
Labels
Severity / Critical
Milestone
Red Eyes Testnet 13

Comments

@hackaugusto
Copy link
Contributor

is_valid_expired_lock currently is not validating if the lock is expired.
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 8, 2018
@hackaugusto
bugfix: lock expiration must be considered
7ea10e8 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
@hackaugusto hackaugusto mentioned this issue Oct 8, 2018
Merged
@LefterisJP LefterisJP added this to the Red Eyes Testnet 13 milestone Oct 8, 2018
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 9, 2018
@hackaugusto
bugfix: lock expiration must be considered
e9bf1c4 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 9, 2018
@hackaugusto
bugfix: lock expiration must be considered
eb2d5f7 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 9, 2018
@hackaugusto
bugfix: lock expiration must be considered
d895c2b 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 9, 2018
@hackaugusto
bugfix: lock expiration must be considered
06272dd 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 9, 2018
@hackaugusto
bugfix: lock expiration must be considered
6d445b5 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 10, 2018
@hackaugusto
bugfix: lock expiration must be considered
82481be 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 10, 2018
@hackaugusto
bugfix: lock expiration must be considered
ea4d85b 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 10, 2018
@hackaugusto
bugfix: lock expiration must be considered
1cb12ce 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 10, 2018
@hackaugusto
bugfix: lock expiration must be considered
588892b 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 10, 2018
@hackaugusto
bugfix: lock expiration must be considered
42528cd 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 11, 2018
@hackaugusto
bugfix: lock expiration must be considered
29c1861 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 11, 2018
@hackaugusto
bugfix: lock expiration must be considered
07525fd 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 11, 2018
@hackaugusto
bugfix: lock expiration must be considered
c5cc42e 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Oct 11, 2018
@hackaugusto
bugfix: lock expiration must be considered
23a6f82 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
LefterisJP pushed a commit that referenced this issue Oct 12, 2018
@hackaugusto @LefterisJP
bugfix: lock expiration must be considered
5337f4d 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix #2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
7b169d2 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
de2f838 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
1eaabad 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
11b065a 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
d4d17c4 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
7ce2a88 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
dd323ad 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
5d9dde1 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
5522515 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
2da4220 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
9f3fa37 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
9b3db7a 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
a257527 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
91a5219 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
37b4706 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
fe830f3 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
c054800 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
a950022 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
cc8b3c1 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
0b389b3 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
3d6f417 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
71d95f0 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
6fba6b9 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
47d6f71 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
975dc8e 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
a001398 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
2e83fc4 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
f3123df 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
899ef73 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 18, 2019
@hackaugusto
bugfix: lock expiration must be considered
9d242a3 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
0c1c4e1 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
89c277c 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
30d5885 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
009f246 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
3616a82 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
hackaugusto added a commit to hackaugusto/raiden that referenced this issue Jan 25, 2019
@hackaugusto
bugfix: lock expiration must be considered
be736c6 
A lock expired message must be ignored if the current block number is
smaller than the lock's expiration. Additionally, the receiver must wait
until the block in which the lock expired is confirmed, this is necesary
to handle the corner case where:

- The secret registration ocurred near the lock expiration
- A reorg happened
- The user's node was following the blocks which didn't have he secret
  registered in time

fix raiden-network#2720
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hackaugusto hackaugusto

Labels
Severity / Critical
Projects
None yet
Milestone
Red Eyes Testnet 13
Development

Successfully merging a pull request may close this issue.

bugfix: lock expiration must be considered hackaugusto/raiden
2 participants
@hackaugusto @LefterisJP