-
Notifications
You must be signed in to change notification settings - Fork 2
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
Make Staking Stable #1
Comments
I'm a bit lazy to reconfig my config because I'm using an updated system on my "org" So I'll just max out the priority to get the pricing in the ballpark of our normal budgets |
It's odd seeing a react codebase in amongst the rest of the UIs The provider being used is a fallback provider that often fails to reach quorum and throws an error in one of the wrappers that's stopping rendering, now it's either connectkit or wagmi but I wasn't able to find who the culprit is on first pass I'll work on this tomorrow |
This is the oldest UI. I decided that we should proceed with React because its the most common framework so I figured it would be the most maintainable. Boy, was I wrong! |
/start |
@kdbvier the deadline is at 2024-03-08T06:57:47.456Z |
# No linked pull requests to close |
/start |
Tips:
|
+ Evaluating results. Please wait... |
/query @Keyrxng |
|
The current uad.ubq.fi interface is hosted off of my development branch as a stopgap until we redeploy.
This is essential infrastructure to keep alive for our stakers/farmers.
Staking view does not always render. I presume its RPC related.
Make sure its stable.
This will be a manual payout.
The text was updated successfully, but these errors were encountered: