blockchain-core
blockchain-core copied to clipboard
helium
State Channel Re-close test
Ensure that submitting a non-dispute state channel close will not make it through when a state channel has already been legitimately closed.
Also update the types of txns a state_channel_client will consider disputable to only those from the original state channel owner. To prevent filing disputes against other disputers.
What happens if the client has a newer version of the state channel that is legitimate?
What happens if the client has a newer version of the state channel that is legitimate?
That's the ultimate issue because at that point it means that server side will start "lying"
What happens if the client has a newer version of the state channel that is legitimate?
That's the ultimate issue because at that point it means that server side will start "lying"
No, that's not true, the router may just be offline.
Imagine this scenario:
Router A is offline, but before it went offline it paid B with a nonce of 20 and also paid C with a nonce of 21.
The state channel expiry time has arrived, A is offline so it cannot close. B sends the latest copy of the state channel with nonce 20. Then C sends its close with a nonce of 21 which should supercede the nonce 20 close, but not conflict with it.