We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, at the moment the saturation point 63.6M (SATURATION_LIMIT = 63600000000000 is hardcoded in https://github.com/Emurgo/adapools-yoroi-frontend/blob/5db1f38a88a4a3916708acb7d7bb863e64063e0b/src/containers/Home.js#L25 and https://github.com/Emurgo/adapools-yoroi-frontend/blob/5db1f38a88a4a3916708acb7d7bb863e64063e0b/src/containers/HomeRevamp.js#L26) looks like definitely low. Are there any plans to raise it to real values?
The text was updated successfully, but these errors were encountered:
Btw, how about the idea of not removing the pool with more than 63.6M ada from the list in case the user delegates to this pool?
Sorry, something went wrong.
No branches or pull requests
Hi, at the moment the saturation point 63.6M (SATURATION_LIMIT = 63600000000000 is hardcoded in https://github.com/Emurgo/adapools-yoroi-frontend/blob/5db1f38a88a4a3916708acb7d7bb863e64063e0b/src/containers/Home.js#L25 and https://github.com/Emurgo/adapools-yoroi-frontend/blob/5db1f38a88a4a3916708acb7d7bb863e64063e0b/src/containers/HomeRevamp.js#L26) looks like definitely low. Are there any plans to raise it to real values?
The text was updated successfully, but these errors were encountered: