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
Because of updates in fuel-core 0.41, the coinsToSpend query now limits how many resources can be ignored when fetching resources. This limit is set by the max_inputs value in the chain configuration.
As a result, we need to update the resource cache logic on the ResourceCache class. Currently, the cache does not track which owner a resource belongs to; it combines UTXO IDs and Message nonces from different owners.
However, since the coinsToSpend query is meant for a single owner, the cache needs to be changed to handle ownership. This way, when calling coinsToSpend, we will be able to exclude resources that belong to one specific user, making it less likely to exceed the max_inputs limit.
The text was updated successfully, but these errors were encountered:
Because of updates in
fuel-core 0.41
, the coinsToSpend query now limits how many resources can be ignored when fetching resources. This limit is set by themax_inputs
value in the chain configuration.As a result, we need to update the resource cache logic on the
ResourceCache
class. Currently, the cache does not track which owner a resource belongs to; it combines UTXO IDs and Message nonces from different owners.However, since the
coinsToSpend
query is meant for a single owner, the cache needs to be changed to handle ownership. This way, when callingcoinsToSpend
, we will be able to exclude resources that belong to one specific user, making it less likely to exceed themax_inputs
limit.The text was updated successfully, but these errors were encountered: