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

Exits become enabled before there are period data available #252

Open
3 of 5 tasks
troggy opened this issue Nov 21, 2019 · 0 comments
Open
3 of 5 tasks

Exits become enabled before there are period data available #252

troggy opened this issue Nov 21, 2019 · 0 comments

Comments

@troggy
Copy link
Member

troggy commented Nov 21, 2019

Bounty

Because of event delay in leap-node, period data becomes available for proof construction later after the period submission. Before that the "slow exit" button is available, but it is not working due to lack of data

Scope

  • enable "Normal" exit button only once period data exists on the remote node (use getPeriodByBlockHeight API endpoint, see leap-core). Avoid excessive API polling here
  • test in local env or on testnet (with local instance of Bridge UI)

Deliverables

  • updated bridge-ui code

Funding Circle

General Circle

Bounty Owner/Gardener

@troggy as Tool Engineer

Gain for the Role

working Bridge UI software to interact with testnet

Roles

bounty gardener: @troggy / 20 DAI
bounty worker: name / share
bounty reviewer: name / share

Gardener checklist

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

No branches or pull requests

1 participant