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

Avoid too many state channel conflicts #524

Closed
jdgemm opened this issue Nov 29, 2021 · 3 comments
Closed

Avoid too many state channel conflicts #524

jdgemm opened this issue Nov 29, 2021 · 3 comments
Assignees

Comments

@jdgemm
Copy link
Contributor

jdgemm commented Nov 29, 2021

Provide a more robust test suite for state channels.

@jdgemm jdgemm added this to the Sprint 66 / 2021.12.08.0 milestone Nov 29, 2021
@michaeldjeffrey
Copy link
Contributor

Can we get a log or something for the case where a packet handler buys an offer, but the internals refuse the offer.

@macpie macpie changed the title Improve state channel test suite Avoid too many state channel conflict storms Jan 18, 2022
@macpie
Copy link
Member

macpie commented Jan 18, 2022

We need to limit the number of close transaction with conflicts that can be submitted (via chain var). As soon as one conflict is in we should reject anymore close transactions.

Furthermore, when reward time comes, if a state channel close includes any conflict the owner should get "punished" and all of its DC used to open SC should be lost. Note that in this case no hotspot would get rewarded to avoid any attempts at gaming the system

@macpie macpie changed the title Avoid too many state channel conflict storms Avoid too many state channel conflicts Jan 19, 2022
@michaeldjeffrey
Copy link
Contributor

blockchain-core PR for tracking helium/blockchain-core#1229

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

No branches or pull requests

3 participants