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.

Sign up for GitHub

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

Implement Value Ranges instead of Locking #98

Closed

Tracked by

maurolacy opened this issue Jul 19, 2023 · 0 comments · Fixed by #106

Closed

Tracked by

Implement Value Ranges instead of Locking #98

maurolacy opened this issue Jul 19, 2023 · 0 comments · Fixed by #106

Assignees

Milestone

Collaborator

maurolacy commented Jul 19, 2023 •

edited

Loading

Use the value range abstraction to try and avoid locking if / when possible.

Fall back to locking / erroring when not possible.

This affects / involves the vault and external-staking contracts on the Provider side.

maurolacy added this to the TODO V1 milestone

maurolacy mentioned this issue

Add roadmap / milestones for v1 and v2 #85

Open

maurolacy self-assigned this

maurolacy mentioned this issue

F/value ranges #106

Merged

maurolacy closed this as completed in #106

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