Skip to content
This repository has been archived by the owner on May 28, 2021. It is now read-only.

Scaffolding for rebalancing service #788

Open
rhlsthrm opened this issue Jan 27, 2020 · 1 comment
Open

Scaffolding for rebalancing service #788

rhlsthrm opened this issue Jan 27, 2020 · 1 comment
Assignees
Labels
Chore Devops or refactoring task Enhancement New feature or request p4: Eventual Enhancements Enhancements that will eventually be needed by users but not immediately

Comments

@rhlsthrm
Copy link
Contributor

Expected Behavior

Current Behavior

Possible Solution

Context

  • Client version used:
  • Node version used:
  • Chain used:
  • Browser Name and version:
  • Operating System and version (desktop or mobile):
  • Link to your project:
@rhlsthrm rhlsthrm added the Needs Triage Needs to be looked at and prioritized. label Jan 27, 2020
@rhlsthrm rhlsthrm added p1 Bugs/Tests/Blockers Bugs that break things but no loss of funds + Test improvements + PRIORITY blockers for customers. and removed Needs Triage Needs to be looked at and prioritized. labels Jan 27, 2020
@hthillman
Copy link
Contributor

This seems like a pretty big bucket.

Does this refer to:

  • setup for shared view
  • new ec2 setup / other devops stuff on the algorithm side
  • new endpoint(s)
  • the algorithm itself

@ArjunBhuptani ArjunBhuptani added Chore Devops or refactoring task Enhancement New feature or request p4: Eventual Enhancements Enhancements that will eventually be needed by users but not immediately and removed p1 Bugs/Tests/Blockers Bugs that break things but no loss of funds + Test improvements + PRIORITY blockers for customers. labels May 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Chore Devops or refactoring task Enhancement New feature or request p4: Eventual Enhancements Enhancements that will eventually be needed by users but not immediately
Projects
None yet
Development

No branches or pull requests

4 participants