You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It probably only makes sense to do this for inlineable RPCs, so that the estimation will actually estimate the underlying query of that RPC. So we should probably just base this off of pdVolatility. This isn't a 100% match, we'd still have some non-inlineable RPCs for which this could be used (without useful results), but volatility is a requirement to make it useful.
The text was updated successfully, but these errors were encountered:
steve-chavez
added
enhancement
a feature, ready for implementation
and removed
idea
Needs of discussion to become an enhancement, not ready for implementation
labels
Jul 10, 2024
It seems like this is not supported, yet.
It probably only makes sense to do this for inlineable RPCs, so that the estimation will actually estimate the underlying query of that RPC. So we should probably just base this off of
pdVolatility
. This isn't a 100% match, we'd still have some non-inlineable RPCs for which this could be used (without useful results), but volatility is a requirement to make it useful.The text was updated successfully, but these errors were encountered: