yoroi-frontend
yoroi-frontend copied to clipboard
hardcoded saturation value ending in inaccurate saturation warnings
Yoroi seem to use some hard coded value for their saturation check currently but should be using a value that's dynamically changing (total ada in circulation / 500). Where 500 is current value of k / nOpt parameter..
Because Yoroi using hard coded value if anyone tries delegating to a pool with 95% saturation and still therefore have some room than they get over saturation warning when in fact is not .
Issue still happening in latest Yoroi 4.8.2
Any updates on this investigation @vsubhuman ?
Bump.